Dehidden

My entry into Web3 didn't come from ideology. It came from building on IPFS and then falling into NFTs as a technical primitive: metadata, content-addressed assets, and ownership represented in code.

Dehidden was the first place where Web3 stopped being "interesting tech" and became "production systems with deadlines".

High-Profile Clients

Over ~1 year, we shipped NFT/Web3 projects for brands and events:

• Coinbase
• Flipkart
• Mercedes
• NFT-NYC
• Polygon ecosystem events
• The Product House

What People Don't See

NFT launches look simple from the outside. A contract, a mint button, maybe some art. What you don't see is the chaos: traffic spikes that break everything, bot farms trying to drain allocations, last-minute scope changes from clients who "just need one more thing," and the reality that go-live doesn't care if you're ready.

I remember a Coinbase activation where the mint flow broke 30 minutes before launch. The issue was in how we were validating allowlist proofs. We patched it live, coordinated with their team, and shipped. No one outside knew anything went wrong.

That's the job. Not the code itself, but the ability to stay calm, debug fast, and make decisions when there's no time to ask for permission.

The Skills I Didn't Know I Was Learning

My role expanded naturally into something between engineering and product:

• Designing mint flows: Not just "deploy contract" but the full user journey, allowlist mechanics, reveal timing, and how it all fails gracefully
• Client management: Translating "we want it to feel premium" into actual technical requirements
• Security reviews: Catching reentrancy patterns, access control gaps, and economic attacks before mainnet
• Crisis response: When things break at 2 AM before a launch, you fix them. No escalation path, no "that's not my job"

Dehidden taught me something I still rely on: the ability to ship under pressure and stay composed when everything is on fire. Clean architecture is a luxury. Making it work is the requirement.