Early on, I was focused on velocity, shipping features, crossing off tasks, and getting products to users as fast as possible. It worked, until it didn't. Production issues, performance bottlenecks, and unexpected bugs revealed something crucial: using tools is very different from truly understanding how they work.

That realization pulled me deeper, past the surface of web development and into the infrastructure that powers trustless systems. I grew fascinated by how smart contracts execute deterministically on-chain, how consensus mechanisms coordinate distributed nodes without central authority, and how protocol design decisions ripple into real economic consequences for users. Blockchain wasn't just another tool, it was a fundamentally different mental model for building systems.

Today I work across the full stack, from crafting frontend interfaces to writing and auditing smart contracts in Solidity. I care deeply about security, understanding attack vectors, invariant violations, and how a single misplaced assumption can drain a protocol. I've explored DeFi primitives, studied audit reports, and built on-chain systems with a security-first mindset.

If there's one principle that defines how I approach engineering, on-chain or off, it's this: I don't stop at "it works."I want to know how it works, why it works, and where it might break. The stakes are higher on-chain, there are no rollbacks, no hotfixes, no support tickets. Just immutable code and the consequences of its design.