Three years. Each commitment forced the next.
A chronology of the work, told quarter by quarter.
This chapter exists because I think readers should be able to see the order in which the pieces clicked. The structure of the protocol looks, in hindsight, like a single coherent design. It was not built that way. Each commitment forced the next one. The order of the forcing matters.
If you want the decisions rather than the chronology, start with Chapter 2 · What Money Has to Do. If you want the load-bearing claim in one chapter, go to Chapter 4 · The GCSR.
- 2023 · Q3 The quantum worry
A conversation in late September 2023 with a former colleague at one of the agencies. She was looking at harvest-now-decrypt-later for adversary analysis and described, in operational terms, what an actor in possession of a working CRQC would actually do with it. The thing she said — paraphrased: the prize is not Bitcoin. The actors who could field a CRQC first are optimizing for sovereign-scale advantage. I went home that night and started writing.
- 2023 · Q4 The MEV postmortems
Six weeks reading MEV postmortems from Ethereum, Solana, Polygon, and the rollup ecosystem. Cumulative MEV extraction across the major chains was in the billions per year. None of it was legal misconduct. All of it was a structural property of designs that gave the leader visibility into transaction content before commitment. The fix is well-known and unpopular: threshold-encrypted mempools. Marked as the second non-negotiable.
- 2024 · Q1 The Terra forensic
A line-by-line walk of the seven-day UST/LUNA depeg event. Every step of the spiral was correct given the protocol's rules. Nobody made an operational mistake. The mechanism was the failure: a one-step move from peg-defense to dilution, with the dilution unbounded. This forced the SZK collateral cap (§4.2) and the immutable waterfall (Chapter 5).
- 2024 · Q2 Sovereign L1, not a rollup
Two weeks of considering shipping as a rollup on an existing settlement layer. The argument against was that none of the three commitments — post-quantum resilience, threshold-encrypted ordering, bounded-dilution stability with an immutable waterfall — survives a rollup architecture cleanly. The decision to be a chain is justified only when the chain's specific commitments cannot survive being an application. StableZK passes that test.
- 2024 · Q3 onwards Build
Consensus implementation in Rust. The threshold-encrypted mempool. The shielded-transaction circuit. The view-key model. The bridge primitives. The audit cycle. Two cohorts of testnet validators. The rolling migration of the proof system from production-ready Phase 1 toward Phase 3. Publication of the bounded-dilution proof for review.
- 2026 · Apr Public release
This cookbook. The whitepaper. The recipe index. The reason it is public: the barrier to digital money that works is not capital — it is the specific structural commitments that produce a credible monetary system.
Open work items live in § 3.5 Cross-Chain Primitives, § 6.5 Re-attestation Under Primitive Change, and the FAQ. None of them invalidate the structural claim. All of them are work I owe.