Domain Obsession
I don't ship features — I internalize the problem space. Crypto lending, payment rails, wallet security — I go deep until I understand the threat model, the incentive structure, the edge cases that kill companies. Then I build.
I build financial infrastructure at the founding layer — lending protocols, payment rails, acquisition-grade systems. Not because it's a job. Because I can't stop until something works exactly the way it should.
I don't just write code. I develop a deep obsession with the domain until I understand it better than almost anyone in the room.
I treat depth as a prerequisite, not a flex. At MetaKeep I owned the stack end to end — not wiring a demo but shipping the work that held up under real diligence. The integration I built became the primary technical validator for a NASDAQ acquisition — the kind of proof that turns a deal from maybe to closed.
At Revalon I co-founded the protocol layer from zero: underwriting and pricing wired to guarded on-chain execution, plus a two-sided marketplace built for adversarial markets, not slide decks. We ran the full testnet lifecycle with zero bad debt— because production discipline is the only honest dress rehearsal.
This is what separates me — not the stack, not the titles. It's the refusal to stop at “good enough”when I know what “right” looks like. I've worked alongside world-class engineers who built WhatsApp Pay, Diem blockchain at Meta, and Twitter's social graph. That environment sharpened something in me: the standard is always higher than what you think.
I don't ship features — I internalize the problem space. Crypto lending, payment rails, wallet security — I go deep until I understand the threat model, the incentive structure, the edge cases that kill companies. Then I build.
From zero to a crypto onramp used in a NASDAQ acquisition. From zero to a lending protocol with disciplined on-chain execution and automated risk workflows. Most engineers prototype. I ship.
I see the whole board — protocol layer, application layer, DevOps, security architecture. When I build lending infrastructure I think about liquidation economics, custody boundaries, reconciliation, and observable decision trails simultaneously.
The work I do has real financial consequence — bad debt, flash-loan exploits, acquisition validators. I operate with the same focus under pressure as I do at 2am with no deadline. That's not a work habit. It's character.
I've never handed a problem back with "that's not my area." Wallet Isolation, open-source gas optimization, fiat-to-token rails — I find the gap, understand it, and close it. Not because someone asked, but because leaving it open bothers me.
One year: intern contributing to quantum-resistant L1 smart contracts. Two years: CTO of a production-grade DeFi protocol. The velocity isn't luck — it's what happens when someone is genuinely, deeply in love with the craft.
Protocol Engineering · DeFi Infrastructure
Rezolve AI · NASDAQ: RZLV
Quantum-Resistant Blockchain Infrastructure
“Being in a room with people who've shipped systems at civilisational scale doesn't just teach you — it permanently recalibrates what you think is possible.”
Meet Jain · On working with world-class engineersWorked alongside builders of