I lead digital asset products where custody, risk, and execution matter.
Wallets • Custody • Transaction Systems • Governance
Ownership
What I Own
End-to-end responsibility for the parts of the system that move money and create risk.
How assets move
Who can sign and when
What happens when things fail
How systems stay compliant under scale
Decision-making
How I Think
I design for the real world: incidents, constraints, and compliance — not demos.
Failure modes before happy paths
Operational reality over diagrams
Governance as a design constraint, not an afterthought
Track record
Selected Outcomes
Representative results from building and operating real-money infrastructure.
Multi-layer custody systems (hot / warm / cold / vault)
Asset infrastructure supporting 150+ tokens
Transaction pipelines designed for 24/7 operations
Real-time monitoring & incident ownership
Outcomes are measured in survivability: degraded modes, recovery paths, and operational clarity when things break.
Field notes
Notes from building real-money systems
Short ideas I keep returning to when designing custody, wallets, and irreversible flows.
Custody is a product problem, not a security problem
Why most wallet architectures fail under scale
Governance is part of the UX - institutions just don't call it that
Designing transaction systems you can't roll back
Framework
Observation → Tension → Decision → Trade-off
Speed vs custody safety isn't a technical trade-off. It's a product decision with operational consequences.
Read more
Longer write-ups on custody primitives, failure modes, and governance-aware UX.
Want to talk product, custody systems, or digital asset infrastructure?
Let's connect on wallet architecture, risk-aware transaction flows, and resilient on-chain operations for real-world use cases.
Let's Connect