I didn’t come into Web3 through a traditional engineering path — I spent 6.5+ years as a Senior Analyst, which shaped how I think about systems, risk, and edge cases.
When I moved into smart contracts, I leaned heavily into security and real-world behavior, not just writing code that compiles.
What differentiates me is that I operate in both modes: I build systems, and I try to break them.
On the building side, I’ve developed a real-time DAO treasury monitoring system that tracks wallets, detects abnormal outflows, and triggers alerts. That forced me to think about how protocols behave under real conditions — latency, event streams, failure cases.
On the security side, I’ve worked through audit contests (Code4rena, CodeHawks), focusing on exploit-driven analysis — writing PoCs, not just reporting issues. I’m particularly interested in edge cases: validation gaps, accounting inconsistencies, and scenarios where systems behave correctly in isolation but fail under composition.
So I don’t approach contracts as static code — I approach them as systems that can be stressed, manipulated, and broken.
That’s the perspective I bring: someone who can ship, but also understands how things fail in production.