Money Without a Master Key
A StableZK cookbook. Three years of design. One reference implementation.
The cookbook in 50 words: A sovereign Layer 1 stablecoin platform built on four structural commitments: post-quantum durability, threshold-encrypted (MEV-resistant) ordering, the Graduated Collateralized Stability Regime with a 43.75% bounded worst-case deficit and a 15% SZK collateral cap, and an immutable resolution waterfall. 0 master keys. No token sale.
My career has had the same shape three times. The pattern goes: I see a hard problem. I build my way into understanding it. An institution hires me to fix the version of it the institution is wrestling with. I write down what I learned afterward.
It happened in genomics in the early 2000s. It happened in fintech across the next decade. It happened in supervisory regulation when I went to the FDIC in 2021 as the inaugural Chief Innovation Officer. I built the agency's first innovation division, sat at the chairman's table while the U.S. banking system absorbed crypto, AI, and quantum simultaneously, and resigned in early 2022 with a Bloomberg op-ed that said, plainly, that my employer was not equipped for the technology era it was now responsible for regulating. I stand by every word.
What I took from that role was a discipline. Go back to first principles. Demand evidence that's been challenged in public. Be honest about what your data can and can't tell you. It is not the FDIC's slogan. It was the operating manual I built for myself inside the agency, and it is the operating manual that produced this cookbook.
In Q3 of 2023 I pointed that discipline at digital money and didn't like what I found. The stablecoins that scaled were custodial. The stablecoins that didn't depend on custodians were either capital-inefficient or kept failing in public. The privacy tools positioned themselves as adversaries to regulators rather than as partners, with the result that nobody got privacy and nobody got compliance. The cryptography under most of the stack had a shelf life that nobody wanted to talk about. And the central banks I had worked with — at the Fed, at the ECB, at the Bundesbank, at the IMF, at the G7 and G20 — had no instrument they could credibly back without becoming the issuer of a CBDC, which most of them did not want to be.
This cookbook is what I built afterwards.
It is the public version of three years of design. It is not a marketing document. There is no token allocation being raised against this page. There is no presale, no whitelist, no roadmap-to-IPO narrative inserted in chapter twelve. There is a working L1 — StableZK — a reference implementation, an audit posture, and a set of constraints I think compose into something the prior generation of digital money could not.
I expect the cookbook to be wrong about specific things. The cryptographic migration timetable in Chapter 3 will probably get faster on some legs and slower on others. The phased launch parameters in Chapter 4 will probably be re-tuned twice in the first year. The regulatory architecture in Chapter 6 will require local counsel in every jurisdiction it ships into. I am not pretending the math is the world. The math is a constraint on how badly the world can behave.
What I am claiming is the structure. The decision to treat post-quantum resilience as a property of the whole stack. The five-layer escalation regime. The immutable resolution waterfall. The view-key compliance architecture. The bounded-dilution proof. These are the load-bearing pieces. The rest is calibration.
I am not selling anything on this page. The barrier to digital money that works is not capital. It is the specific structural commitments that produce a credible monetary system. That is what this cookbook is.
Pick a recipe. Act on it this week.
At a glance
The numbers above are immutable parameters of the StableZK protocol. See § 4.4 The Bounded-Dilution Proof for how the worst case is bounded.
Table of contents
-
A year-by-year chronicle of how the design happened.
-
A monetary system has to do four things.
-
What's load-bearing, what's swappable, what's production-ready as of April 2026, and what isn't.
-
The Graduated Collateralized Stability Regime.
-
What happens at Layer 5.
-
View keys, ZK compliance attestations, the warrant model, jurisdictional notes.
How to read this
Every recipe follows the same structure: Problem (the design decision you're facing), Solution (what to actually do, with parameters and grades), Discussion (the reasoning, the edge cases, what the math relies on), and See Also (cross-references to other recipes that touch the same decision).
Inline callouts flag tips (things that compound), warnings (where the conventional advice gets it wrong), and notes (caveats worth naming out loud). Anything in monospace is a specific value — a parameter, a primitive, a threshold, a grade — that I want you to read precisely.
This cookbook is not legal opinion. The regulatory architecture in Chapter 6 is design, intended to inform implementation in collaboration with counsel in each relevant jurisdiction.
Pick a recipe. Read just that recipe. Act on it.