I think, I lift, I build.

Most of my work never faces a user. It faces an auditor, a regulator, or a failure mode. The goal is to be taken for granted: the cardboard box, the light switch, the click of a seat belt.

I don't ship interfaces before correctness.
I don't add abstraction without necessity.
I don't wrap other people's infrastructure.
I don't reinvent what works.
I don't build crypto products, consumer apps, or speculative bypass layers.

I build core banking infrastructure. Ledgers. Control planes. Compliance encoded into structure. Systems that fail in contained, inspectable ways. The metric is whether it holds decades later.

Design starts with failure. What breaks. What can't. What the blast radius looks like. Then constraints, then interfaces, then code. Small units, clear contracts, no hidden behavior. One responsibility per component. Text over binaries. Pipes over platforms. Explicit over clever. Boring and correct. UNIX minimalism.

I spent three years as CEO of BitEscrow, building non-custodial Bitcoin escrow. The technology worked. The market wanted it for stablecoin collateral, not Bitcoin settlement. I shut it down rather than force a misfit.

Then I started building a neobank. I live-streamed the entire build from wireframe to last commit. Deep into core banking, I found the real constraint: the infrastructure didn't exist. So I stopped building the product and started building the foundation.

Pediment is that foundation.

Durability is the real metric. Leverage beats headcount. Infrastructure is destiny. Banks aren't broken; their tooling is. The best outcome is invisibility: systems that outlast their builders and the conversations about them.

When money becomes code and code becomes law, may my work keep banks governable - not godlike.

Last edited Jan 16, 2026