Web3 Talent

My story starts far from crypto: a decade in .NET/Azure, building backend systems where reliability wasn't optional — payment flows, distributed services, the kind of architecture where one unguarded state transition costs real money. That's the exact same failure mode smart contracts have, just with fewer safety nets and a lot more at stake.

So instead of jumping straight into "write a dApp," I built my Solidity foundation the way I'd approach any unfamiliar critical system: implement it, then attack it. I've shipped working (testnet) contracts — ERC-20/ICO mechanics, staking with reward accrual, a minimal AMM — and then spent a dedicated week auditing deliberately vulnerable ones against real-world patterns: reentrancy, integer overflow, oracle manipulation, flash loan exploits, frontrunning.

What makes me great isn't years in Solidity — it's years of thinking like someone accountable for what happens when code meets money at scale, now pointed directly at finding what other developers miss.