AfterFiat· Complete Edition

AfterFiat

Front Matter

Complete Edition · v4.1

Abstract

Gold works when the network does not; Bitcoin works when the state does not. Neither is priced for the state this thesis is about: administrative repression under intact infrastructure, where the courts sit, payments clear, the lights stay on, and guarantees are honoured selectively at a price set by someone else. That band is narrow by construction, and the narrowness is the specification rather than an apology for it. Under sustained administrative and financial repression, a bearer asset may earn monetary premium if holding it preserves private settlement, portable proof, and access to verified compute after ordinary legal, custodial, and platform substitutes weaken. That premium is conditional: the full service path must remain stress-deliverable through independently substitutable physical routes; demand must not bypass the asset; a persistent, self-custodied, loss-bearing holder constituency must absorb residual financial risk; and the duration-bearing credit required to build the infrastructure must remain explicitly separate from the monetary object. Privacy, Proofs, and Compute may share that asset, but whether they should is an empirical architectural question rather than a premise.

The protocol and its price are different machines. The protocol machine supplies the triad and routes its demand through fees, burns, collateral, and scheduled issuance. The market machine wraps the resulting asset into custody claims, funds, derivatives, leverage, and allocation rules. Either machine can move without the other. Price is something to explain, not evidence to cite.

Fees, burns, and collateral establish a competitively priced cash-flow claim and a balance-sheet lockup—both of which a discounted-cash-flow valuation reproduces and neither of which is a monetary premium. The monetary claim rests on three mechanisms that lie outside such a valuation. Pledgeability without due diligence: cheap universal verification can make a position information-insensitive by symmetric knowledge — checking is free and public, so looking confers no edge on anyone — rather than by the symmetric ignorance every prior money-like asset has relied on. Denomination: the coordination function a service protocol can reach because the goods are produced by the system that issues the unit. And a state-contingent holder-side service flow: the bearer’s ability to transact, prove, hold, and exit when the substitutes for proofs, courts, and custodians have stopped working. Against its strongest alternative — holding Bitcoin and converting on the day — that service reduces to a balance that stays spendable when acquiring one is no longer feasible, and an access experiment tests whether it does. Each mechanism is standard in its own literature. This thesis argues all three, sizes none of them, and publishes an instrument and a red line for each.

The competitor to an open verifiable stack is accordingly not fiat but a competent closed sovereign stack—state-integrated energy, industry, compute, payments, and identity—which may win on cost, uptime, and build speed while inverting who ends up sovereign. Two such stacks are now under construction rather than one. The marginal buyer of cheap verification is increasingly a machine delegating to another machine across trust perimeters, and the thesis measures whether a human still stands behind what that buyer holds. Duration-neutrality of the monetary object is a repression-resistance requirement, not a theory of capital formation: reserve collateral and the construction interval of plants are different functions, and proofs must not become the bond. The thesis publishes eighteen red lines: named, measurable conditions any one of which would retire or downgrade it. Chapter 8: The Triad and the Monetary Candidate states the argument as a chain of nine links and names the links it rates weakest.

Extended Abstract

Post-Bretton Woods money is increasingly backed by compliance and regulatory enforcement rather than reserves or convertibility. Debt stocks that cannot be honored in real terms make financial repression and balance-sheet capture arithmetically attractive. The dependency now runs in both directions: fiscal capacity itself comes to rest on the market value of the asset complexes the state regulates, and the marginal demand for the reserve asset is increasingly commissioned by benchmark rules and delivered by leverage. Synthetic media and platform moderation undermine the assumption that “seeing is believing.” AI concentrates cognition and compute behind hyperscaler chokepoints. Hardware, networks, identity, and custody systems are progressively integrated into state and platform surveillance infrastructure. In that environment, stores of value that depend on soft guarantees—custodians, editorial gatekeepers, platform labels, regulated wrappers, or vendor invoices—are brittle.

This thesis tests a narrower claim: Privacy, Proofs, and Compute can support an agency-preserving bearer asset that may earn monetary premium under repression, but only where the full stack delivers usable service under stress and a durable native holder base warehouses the asset’s risk. Fees, burns, collateral, disciplined issuance, and public telemetry establish value accrual: a competitively priced cash-flow claim and a balance-sheet lockup, both of which a discounted-cash-flow valuation reproduces and neither of which is a monetary premium. The monetary claim rests on the three mechanisms the Abstract names—pledgeability without due diligence, denomination, and a state-contingent holder-side service flow—each argued, none sized, and each given an instrument and a red line. The holder-side flow meets its strongest alternative first: hold Bitcoin and convert on the day. Against it, holding the base asset buys one thing, a balance that stays spendable where acquiring one is unavailable, too slow, or incompatible with the transaction’s privacy and control terms while native settlement and the service path still work. It buys no capacity, price, or priority; those are sold through Work Credits, prepaid claims on service reserved with named providers. An access experiment tests whether the advantage exists against the best Bitcoin-funded strategy, provider-side conversion included, and whether it supports anything beyond operating inventory (Chapter 13: Why Hold the Base Asset?). The thesis makes the mechanisms’ physical, market, and holder conditions measurable so the question can be settled rather than asserted. Its threat model assumes intentional repression, not benevolence, including the softer administrative repression of custody defaults, compliance rules, and platform terms of service. Against that adversary it sets a seven-layer architecture. Layer 0 grounds it in verifiable machines, energy, and physical capacity (Facility Capacity Receipts); the layers above run through communications, software distribution, identity, truth & work, value & settlement, and a telemetry/governance layer that measures drift rather than denying it.

At the economic core, the thesis formalizes verification asymmetry and defines VerifyPrice (the time-and-cost vector for independently checking a claim) as the hinge that turns proofs and verified FLOPs into commodities rather than platform IOUs. It proposes a Create/Compute → Prove → Settle → Verify loop, a modular stack of twelve primitives, and four reference applications: private treasury & payroll, media provenance, verified inference, and proof/compute procurement. An operator/investor telemetry program, with extensions such as VerifyReach, VerifySettle, and the Wrapper Dominance Ratio, makes neutrality, repression-resilience, and co-option risk falsifiable.

Even when these conditions hold at the protocol layer, observed asset prices can be dominated by external financial wrappers, price-insensitive allocations, mechanical rebalancing, and dealer hedging. This thesis therefore distinguishes native value capture from market price capture and introduces VerifyFlow, a public market-realization telemetry program measuring wrapper exposure, creations and redemptions, holder flow elasticity, leverage, concentration, dealer dependence, and the divergence between financial exposure and protocol-native use. Price is not treated as proof of monetary adoption. Recurring native fees, burns, collateral, settlement, and verified-work demand under healthy SLOs are what make value accrue to a triad asset at all, and are necessary before any monetary question can be asked of it. Wrapper-led appreciation without those conditions is financialization rather than monetary validation.

The buyer the thesis models is increasingly not a person. The marginal purchaser of cheap verification is a machine delegating to another machine, several hops from its principal, at a speed that leaves no room for due diligence, reputation, or courts. Whether that demand ever reaches an open stack depends on whether delegation crosses trust perimeters or stays inside one operator’s fleet; whether its holdings count as anyone’s depends on whether a human can still revoke, cap, and re-key the agent (Chapter 7: The Delegation Economy: Who Buys Verification). This gives the first link of the chain a mechanism and the holder link a caveat. It supplies no precedent.

Beneath both loops sits a physical dependency the thesis makes explicit rather than assuming away. Gross capacity is not deliverable service: the relevant quantity is the surviving flow through energy or fuel →\rightarrow firm electricity →\rightarrow transformer and switchgear →\rightarrow cooling and water →\rightarrow hardware →\rightarrow network →\rightarrow workload →\rightarrow proof →\rightarrow verification →\rightarrow settlement →\rightarrow usable service. The thesis therefore reports Delivered Verified Capacity beside Sovereign Optionality: the first measures scenario-specific surviving service flow and its binding constraints, while the second measures pathway diversity. Service claims are bounded by stress-adjusted deliverable capacity, not nameplate hardware or a benign-state average. Because verification affordability is denominated in real resources on reference hardware, it is exogenous to token price but not exogenous to the conditions under which power and unprivileged hardware can be obtained. The hinge is externally triggerable.

The Topological Scarcity Lemma follows: a nominal stock of resources, capital, or capacity does not secure a monetary service; the relevant quantity is the stress-deliverable flow through the narrowest non-substitutable edge connecting input to holder utility. The associated Pressure–Capacity Corridor writes the potential monetary service as Πmonetary(R)∝Δ(R)×Afull\mbox−stack(R)×H(R)\Pi_{\mathrm{monetary}}(R)\propto \Delta(R)\times A_{\mathrm{full\mbox{-}stack}}(R)\times H(R), where differential demand may rise with regime pressure, full-stack availability may fall, and H(R)H(R) is the holder’s practical ability to self-custody, transact, prove, and exit. The likely shape is an inverted U: little differential value under benign institutions, the strongest case while substitutes weaken but the open stack still works, and declining service when extreme pressure disables the stack or the holder.

The competitor to an open verifiable stack is accordingly not fiat but a competent closed sovereign stack—state-integrated energy, industry, compute, payments, and identity—which may win on cost, uptime, and build speed while inverting who ends up sovereign. Architecture is likewise not pre-selected: the thesis compares one native monetary asset, a neutral reserve plus service-specific credits, and shared settlement plus modular domain collateral. Capability was never the claim; the properties are. In total the thesis publishes eighteen red lines: named, measurable conditions any one of which would retire or downgrade it.

Gold, silver, Bitcoin, and physical hard assets remain load-bearing bridge assets while this stack is under construction; the triad becomes a candidate destination only when VerifyPrice, VerifyReach, VerifySettle, Layer 0 capacity telemetry, and value-capture metrics prove resilience under adversarial conditions. This is not a call to abandon hard assets prematurely, nor a claim that new money is inevitable. Bitcoin’s work function is conceded to be monetarily superior to proof-of-useful-work, and for a reason that does not go away: nobody outside the system buys a hash, so nobody can subsidize, mandate, or withdraw demand for it, and a useful-work function necessarily introduces a buyer who can be. The claim made here is not that a better money is available, but that portable attestation and verified compute are separate goods with separate demand, and that whether they carry monetary premium or merely price as services is open. The result is not a single chain or guaranteed new money, but a research and engineering agenda: a “Bell Labs” for proof-of-useful-work and lawful privacy, testing whether Privacy, Proofs, and Compute can earn a store-of-value premium under measurable conditions. The conditions are that verification remains cheap, privacy settlement remains usable, useful-work markets avoid capture, physical infrastructure remains legible, and protocol design converts recurring triad demand into scarce, non-bypassable, agency-preserving asset value.

Executive Memo: Why AfterFiat Exists

The fiat problem is no longer only inflation. It is the merger of debt arithmetic, compliance-backed money, platform-mediated truth, AI enclosure, and physical compute constraints.

Sovereigns with debt loads that cannot be honored in real terms will prefer repression to default. Platforms facing synthetic media and regulatory pressure will prefer managed truth to open verification. AI hyperscalers will prefer renting cognition to distributing it. Custodians and wrappers will prefer price exposure without native usage. Citizens below the participation line will be offered management rather than agency.

This thesis is the counter-architecture: private settlement instead of surveilled accounts, portable proofs instead of platform labels, verified compute instead of vendor promises, and public telemetry instead of trust. Capturing indispensable demand, and not being bypassed by fiat, stablecoins, cloud contracts, custodial wrappers, or administrative convenience, is what makes value accrue to the asset. It does not by itself make the asset money: a fee stream and a collateral lockup are quantities a discounted-cash-flow valuation reproduces. The monetary claim rests on three mechanisms a discounted-cash-flow valuation does not reach: whether a counterparty will accept the asset without investigating it, whether anyone will reckon in it rather than merely settle in it, and what the bearer can still do when the substitutes for proofs, courts, and custodians have stopped working. This thesis argues all three and sizes none of them.

The thesis is conditional, and two concessions belong at the front rather than in an objections chapter. Bitcoin’s work function is monetarily superior to proof-of-useful-work, because a puzzle nobody outside the system buys has no demand curve anyone can move. And gross native demand is not a monetary anchor: just-in-time fee purchases, burns, operator inventory, collateral requirements, and wrapper exposure do not establish a persistent, self-custodied, loss-bearing constituency willing to add through stress. Gold, Bitcoin, and hard assets are the bridge. Privacy, Proofs, and Compute supply different goods; whether one native asset, a neutral reserve plus service credits, or shared settlement with modular collateral best serves them remains an empirical question.

The buyer is a delegation.

The marginal buyer of cheap verification is increasingly a machine acting for a principal several hops away: an agent delegating to another agent, at a speed that leaves no room for due diligence, reputation, or courts. Whether that demand ever reaches an open stack depends on whether delegation crosses trust perimeters or stays inside one operator’s fleet, and that is set by the same verification cost the rest of the argument hinges on (Chapter 7: The Delegation Economy: Who Buys Verification). The structure of this buyer is measured, not assumed: who operates it decides how coercible it is, and whether a human can still revoke it decides whether its holdings count as anyone’s. It supplies no precedent and repairs no concession.

The protocol and its price are different machines.

The protocol machine supplies Privacy, Proofs, and Compute and routes their demand through fees, burns, collateral, and constrained issuance. The market machine wraps the resulting asset into custody claims, funds, derivatives, leverage, and allocation rules.

The first machine determines whether the asset has monetary substance. The second determines how that substance—or the story about it—is represented in price.

Either machine can move without the other. A protocol can improve while its price falls during wrapper redemptions. Its price can rise while native use stagnates because an ETF, treasury company, or leveraged product directs large exposure demand toward a thin market.

The protocol machine: native useThe market machine: price
downup
improvingprice falls, native use rises
flatmarked price rises, native use flat

Schematic

Two machines: native use against price. Price up with native use flat is the marked cell.

AfterFiat therefore requires two forms of falsifiability: stack telemetry for monetary function, and flow telemetry for market realization.

A further unbundling belongs at the front rather than only in an objections chapter. Duration-neutrality of the monetary object is a repression-resistance requirement. It is not a theory of capital formation. Reserve collateral and long-lived project finance are different functions; Treasuries currently fuse them; proofs can audit the second and must not become it (Chapter 3: The World Forces New Monetary Primitives, Chapter 34: Objections & Responses).

Both machines are bolted to a grid.

Cheap verification is the hinge of the entire argument, and it is priced in electricity and reference hardware. That makes it exogenous to token price but not to policy: a state that finds it awkward to ban verification can simply decline to energize it, and curtailment, rate discrimination, and interconnection queues survive judicial review comfortably. The exposures differ—verification is threatened by hardware obtainability, proving by bulk power—and conflating them produces overclaims in both directions. The thesis measures the substrate as sovereign optionality, prices its fragility into issuance, and retires itself if verification affordability becomes a sovereign policy variable rather than a market outcome.

The real competitor is competence, not fiat.

A state-integrated closed stack—sovereign energy, industry, compute, payments, and identity—is the same trust-minimization instinct applied to matter, and it may deliver better cost and uptime than anything open. The thesis does not contest that. It argues that non-custodial settlement, default privacy, portable identity, checkable receipts, and practical exit are what make an asset a store of value under repression, and that a closed stack withholds precisely those, because withholding them is what makes it closed. Identical dashboards, opposite answers on whether a user can leave. The greater risk is not losing to that stack but quietly becoming it, which is why agency and exit are on the scoreboard and why the thesis names eighteen red lines rather than promising success.

Why instrument rather than forecast.

Every prior restructuring of how civilization handles information arrived as an externality of something cheaper, and nobody ordered its consequences. The printing press was adopted to copy books. Nobody adopted it to create the silent private reader [Ong 1982], standardized parts [Eisenstein 1979], or the nation-state; those arrived over centuries, as byproducts of a new habit at scale. The lesson generalizes, with the caveat that it is mechanism rather than measurement: a new medium is adopted for the function it makes cheaper, and it restructures whoever habituates to it, on a schedule nobody plans.

The stack tested here is being adopted to check work more cheaply. What cheap checking may do to the sensory basis of trust—to who can verify whom, and therefore to who must be trusted at all—is similarly unpredictable, and this thesis does not pretend otherwise. It responds by instrumenting the transition instead of forecasting it: red lines, public boards, and SLOs exogenous to token price, so that the consequences, good or bad, announce themselves in telemetry rather than in narrative (Appendix J: What Changed Across Releases records what each revision added). The frame is borrowed from the media-transition literature [McLuhan 1964]; the falsification conditions are not.

Thesis in Plain Language

The core claim: Under sustained administrative and financial repression, a bearer asset may earn monetary premium if holding it preserves private settlement, portable proof, and access to verified compute after ordinary substitutes weaken. The full service path must remain stress-deliverable; demand must not bypass the asset; a persistent, self-custodied, loss-bearing holder constituency must absorb residual financial risk; and project credit must remain separate. Privacy, Proofs, and Compute may share the asset, but the thesis does not assume they should.

The accrual mechanism: Service value can accrue to the base asset through four channels:

  1. fees paid in the native asset for proof generation, privacy settlement, and verified compute;

  2. burns that permanently remove supply when capacity is consumed;

  3. required collateral for provers, routers, and liquidity providers; and

  4. issuance on a schedule fixed ex ante, not fiat decree.

The value-capture bridge: Utility demand alone does not create store-of-value premium. In the reference design, five channels route service value to the asset:

  1. the asset is the required fee medium for core triad services;

  2. a meaningful share of fees is burned or permanently retired;

  3. operators must stake the asset as collateral;

  4. gross issuance follows a schedule fixed ex ante; and

  5. users cannot obtain equivalent service quality through bypass channels that avoid the asset.

These are the reference design’s channels, each necessary to its route and none necessary to value capture in general. If one fails in this design, the system may be useful infrastructure while the base asset fails even as a service-value claim. If all five hold, the result is a cash-flow claim and a collateral lockup, not yet money.

The monetary bridge adds what the accrual bridge cannot supply. Two are preconditions: stress-deliverable service, and a holder constituency that retains self-custodied balances, bears losses, and accumulates through relevant pressure rather than buying fees just in time or holding wrappers. Three are the mechanisms by which a premium could actually arise, each standard in its own literature and each unsized here (Chapter 13: Why Hold the Base Asset?, Chapter 13: Why Hold the Base Asset?):

  1. pledgeability without due diligence — cheap public verification removes the private information about unit quality that a lender would otherwise price, so a position can be accepted no questions asked; the prediction is lower cross-lender haircut dispersion than on opaque comparables, among lenders who underwrite independently, not lower haircut levels;

  2. denomination — a service economy whose goods are priced, produced, and settled inside one accounting perimeter has a coordination path to being reckoned in, which a bare bearer asset lacks; measured as free-choice denomination share, never the mandated complement;

  3. a state-contingent holder-side service flow — the bearer’s ability to transact, prove, hold, and exit when the substitutes for proofs, courts, and custodians have stopped working, which accrues by holding rather than by distribution; against Bitcoin converted on the day it reduces to a balance that stays spendable when acquiring one is no longer feasible, tested by an access experiment (Chapter 13: Why Hold the Base Asset?) and measured as the convenience yield’s increment in the pressure corridor.

The falsifiable test: It runs one way. If VerifyPrice rises, VerifyReach falls, VerifySettle breaks, DVC collapses, the capturable wedge closes, the native holder base proves procyclical, the collateral–capacity spiral breaches its bound, any of the three monetary mechanisms reads null on its instrument, or the access experiment finds that Bitcoin converted on the day does as well as a held balance, monetary candidacy fails or is weakened, as its red line specifies (Chapter 30: Risk Analysis & Failure Modes). Healthy readings merely keep the candidate alive; no accumulation of green dashboards proves monetary premium.

What price does not tell you: None of the tests above is a price test. An asset’s price can rise because ETFs, treasury companies, leveraged products, passive mandates, or dealer hedging direct large exposure demand at a thin market, while native fees, burns, settlement, and proof purchases stay flat—and it can fall while all of those improve. That is why the thesis adds a fourth measurement family, VerifyFlow (Chapter 26: Extended Telemetry), to separate protocol-native demand from wrapper-led exposure. Price is something to explain, not evidence to cite.

Who is buying: Increasingly, software agents acting for people several steps away. An agent cannot investigate what it accepts at the speed it works, so it accepts most readily what anyone can check, which is why its demand is demand for verification. The thesis measures whether that demand crosses between operators, and whether a human can still revoke the agent that holds the asset.

The thesis examines the triad from three complementary angles, plus one plane around them:

  • Angle 1 — Monetary: whether a bearer base asset can earn a next-generation store-of-value premium by preserving agency through Privacy, Proofs, and Compute; the service claims themselves remain non-monetary.

  • Angle 2 — Stack: the seven-layer cypherpunk stack that actually supplies these capacities.

  • Angle 3 — Telemetry & Governance: VerifyPrice/Reach/Settle + ops as the thing that keeps “repression-resilient neutrality” falsifiable.

  • The Market Realization Plane: the external financial machinery—wrappers, custody, leverage, dealers, allocation rules—that determines how, when, and with what volatility any of the above shows up in price (Chapter 13: Why Hold the Base Asset?).

The Conditional Chain at a Glance

The thesis establishes its claim through a conditional chain rather than an assertion, and a chain defended across the whole thesis is easy to lose. This page states it once; Chapter 8: The Triad and the Monetary Candidate walks it in full, says where each link is argued, and closes with Chapter 8: The Triad and the Monetary Candidate, which rates the argument link by link.

Utility demand →\rightarrow standardized work →\rightarrow receipts →\rightarrow stress-deliverable service →\rightarrow markets →\rightarrow fee flows →\rightarrow a scarce asset (only under non-bypassable accrual) →\rightarrow a persistent, self-custodied, loss-bearing, regime-responsive holder constituency →\rightarrow a possible store-of-value premium.

Every arrow is a conditional. None is asserted as inevitable, and the chain is only as strong as its weakest link. Each link therefore comes with the condition that would sever it:

LinkSevered if
1Utility demand exists and persists, through every cycle and especially under repression; machine delegation across trust perimeters is one named mechanism (Chapter 7: The Delegation Economy: Who Buys Verification)the demand turns out to be cyclical discretionary spend rather than structural necessity, or delegation stays inside fleets that need no portable receipt
2Demand standardizes into canonical work—workload registries, hardware profiles, SLA tiersworkloads stay bespoke, so no fungible unit forms and there is nothing to price
3Work produces cheap-to-check receipts, with r(W)=v(W)/p(W)≪1r(W) = v(W)/p(W) \ll 1verification cost creeps toward production cost, and “anyone can verify” collapses into “trust the prover” (Red Line 1, the hinge)
4Receipts represent stress-deliverable service, measured by scenario max-flow across the full stack, with binding constraints reportednameplate capacity survives on paper while substitution latency or common-cause failure collapses usable service
5Receipts enable markets: proof factories, neutral routers, SLA escrow, capacity procurementrouters, provers, or matching engines capture the market and rent replaces work (Red Line 3 territory)
6Markets produce recurring fee flows, visible as fee coverage against the security budgetfee coverage collapses and workload demand proves speculative rather than budgeted
7Fee flows accrue to a scarce asset—only under the five non-bypassable conditions of the Value Capture Lemmausers obtain equivalent triad capacity through hyperscalers, stablecoins, or custodial APIs without touching the asset (Red Line 6)
8A persistent, self-custodied, loss-bearing, regime-responsive holder constituency anchors the assetnative demand is just-in-time, immediately sold, wrapper-led, leveraged, or procyclical, or the cohort is one operating policy at many addresses
9A scarce, captured, anchored asset may earn a store-of-value premium, if it stays liquid, neutral, verifiable, legally holdable, and agency-preservingany store-of-value requirement fails, a held balance does no better than Bitcoin converted on the day, or the telemetry showing it is captured (Red Line 4)

Where it is weakest. Six links are rated Medium or Medium (conditional). Standardized work and proof/compute market formation are engineering-maturity risks. Stress-deliverable service is Medium because common-cause and substitution data are immature; non-bypassability, because the economics requires a magnitude rather than a binary; the holder anchor, because native transactions do not prove risk absorption; and the premium itself is conditional on the whole chain. The store-of-value premium derives from link 9 through three mechanisms, not from fee accrual: pledgeability without due diligence, denomination, and the state-contingent holder-side flow (Chapter 13: Why Hold the Base Asset?, Chapter 13: Why Hold the Base Asset?); Red Lines 16–18 read on them. The full ratings are in Chapter 8: The Triad and the Monetary Candidate.

What the chain does not claim. Completing all nine links would establish only that the base asset is a defensible monetary candidate. It would not establish when, or with what volatility, price reflects that (Chapter 13: Why Hold the Base Asset?). Nor is the chain suspended in mathematics: the service links consume bulk power and hardware, and the holder link requires balance sheets capable of bearing loss. Both can fail while gross capacity or gross native demand still looks abundant.

Reader’s Map

This thesis is structured as a ladder of seven interlocking layers. Each layer has one or more “home” sections, and most layers also surface in the Create/Compute → Prove → Settle → Verify loop and in the telemetry program.

Use the following table as your compass:

Layer

Role in the Stack

Primary Sections

Key Metrics / Concepts

Falsification Test

Layer 0 — Verifiable Machines & Energy

Physical base reality: open silicon, sampled supply chains, and the power plants that keep provers and routers alive. For pure proof correctness, sound cryptography should tolerate untrusted provers. Layer 0 becomes essential when claims include physical capture, energy use, machine identity, witness confidentiality, or useful-work fairness.

Chapter 17: Layer 0: Verifiable Machines & Energy Layer 0 (open hardware, profiles, lot sampling, FERs); Chapter 31: Implementation Sketches for Builders (L0 implementation sketches); Appendix D: Energy & Plant Architecture (Energy & Plant); Appendix E: Hardware Profiles (Hardware Profiles)

Hardware profiles (HIDs); lot-sampling coverage; Facility Energy Receipts (FERs); Facility Capacity Receipts (FCRs); sovereign optionality 𝒪s\mathcal{O}_s; Physical VerifyPrice (infra audit); disruption-adjusted VerifyPrice; PUE/ERE/WUE; kWh/receipt; profile incidents

RL10 (physical opacity) or RL13 (𝒪snet\mathcal{O}_s^{\text{net}} below threshold / rationing jurisdictions); hinge VerifyPrice becomes sovereign-policy-driven

Layer 1 — Reachability: Communications & Transport

Keeps packets flowing under DPI, filtering, and shutdowns. Without Layer 1, the loop cannot run and “public verification” becomes theoretical.

Chapter 18: Layer 1: Reachability Layer 1 (threats, design rules, mechanisms, VerifyReach); Chapter 31: Implementation Sketches for Builders (comms sketch); Appendix F: Communications Resilience Mechanisms (Comms Resilience)

VerifyReach(N,R): p50/p95 time-to-first-connection; succ1_1/succ2_2 reachability; failure causes; share encrypted/obfuscated traffic; peer-set diversity (geo/ASN); swap success under network stress

>>20% of sampled ASNs in uncensored regions unreachable for >>7 days

Layer 2 — Distribution & Execution: Software Supply & Runtime

Ensures honest clients and updates can be shipped even when app stores, CDNs, and DNS are weaponized. Protects the code that speaks the protocol and runs PaL/PRK.

Chapter 19: Layer 2: Distribution & Execution Layer 2 (threats, design rules, multi-home architecture, update pipeline, key mgmt, fallback playbooks); Chapter 31: Implementation Sketches for Builders (distribution tooling); Appendix B: Practical KPIs & Telemetry Templates (update KPIs)

Update health: p50/p95 metadata & artifact fetch times; success/rollback/signature-failure rates; mirror/CDN top-N share; geographic/ASN diversity; key-rotation & incident history

Single key compromise can push malicious updates

Layer 3 — Identity & Claims: Humans & Machines Without Doxxing

Lets humans and machines prove capabilities and rights (age, residency, uniqueness, model ownership, device profile) without turning identity into a global dossier. Reputation is receipts, not biographies.

Chapter 20: Layer 3: Identity & Claims Layer 3 (identity kernel, human & machine identity, reputation, guardrails, how identity uses the loop); Chapter 27: Legal, Policy, and Jurisdictional Posture (lawful-privacy requirements); Appendix C: The SDK (Proofs-as-a-Library) (PaL/PRK SDK)

Identity-predicate VerifyPrice (p50/p95 verify times for age/residency/set-membership proofs); unlinkability tests; reputation from PIDL receipts (SLA fulfillment vs slashes); hardware-anchored machine attestations

Identity requires centralized issuer

Layer 4 — Truth & Work: Proof Systems and PoUW

Converts expensive work into cheap-to-check receipts. This is where verification asymmetry lives and where VerifyPrice is defined.

Conceptual: Chapter 11: Compute Through the "AI Money" Lens Compute Through the “AI Money” Lens, Chapter 12: Work Credits: Reserved Service Claims Work Credits; Structural: Chapter 21: From Infrastructure to Economics Infrastructure to Economics; Chapter 22: Layer 4: Truth & Work Layer 4 (canonical workloads, PoUW, proof factories, PaL); Chapter 24: The Modular Stack (primitive catalog); Appendix A: Formal Model of Verification Asymmetry & VerifyPrice (formal VerifyPrice)

VerifyPrice(W) per workload: p50/p95 verify times/costs; failure rates; r(W)=v(W)/p(W)r(W) = v(W)/p(W); prover concentration; SLA attainment (Bronze/Silver/Gold); MatMul-PoUW economics; Work-Credit issuance

VerifyPrice p95 exceeds SLO for ≥\geq3 months

Layer 5 — Value & Settlement: Privacy Rails & Non-Custodial Flow

Moves value non-custodially and privately, with auditability via receipts. This is where the service markets described by the legacy “Private Money,” “AI Money,” and “Proof/Attestation Money” lenses settle; their Work Credits and capacity instruments remain typed service claims. The separate base asset is the only conditional monetary candidate.

Analytical lenses: Chapter 9: Privacy as Private Money Privacy as Private Money, Chapter 11: Compute Through the "AI Money" Lens AI Money, Chapter 10: Proofs as Attestation Money Proof/Attestation Money; service claims: Chapter 12: Work Credits: Reserved Service Claims (Work Credits); the monetary argument: Chapter 13: Why Hold the Base Asset? (Why Hold the Base Asset?); Stack: Chapter 23: Layer 5: Value & Settlement Layer 5 (settlement as workload, PRK, bridge-safety, corridors); Chapter 24: The Modular Stack (treasury/payroll, media, inference, procurement flows); Chapter 31: Implementation Sketches for Builders (privacy toolkit); Appendix F: Communications Resilience Mechanisms (swaps, routing)

VerifySettle(C): swap success ≥\geq target; refund_safe(C) — a bounded-time no-loss exit for every party, zero protocol-attributable losses (Chapter 23: Layer 5: Value & Settlement); p50/p95 time-to-finality; per-asset anonymity metrics; corridor LP/route concentration; non-custodial vs custodial flow share

RL2: any protocol-attributable refund failure on an admissible route, or overall refund_safe << 99.5% with failures unclassified (repeated, no delist)

Layer 6 — Governance & Telemetry

The immune system and constitution: keeps drift and capture visible and forces responses. Turns “trustlessness” into dashboards and runbooks.

Metrics: Chapter 22: Layer 4: Truth & Work (VerifyPrice observatory); Chapter 26: Extended Telemetry Extended Telemetry; Governance: Chapter 25: Layer 6: Governance & Telemetry Layer 6 (SLOs as constitution, control surfaces, Bell-Labs vs on-chain vs norms); Legal: Chapter 27: Legal, Policy, and Jurisdictional Posture; Ops: Chapter 28: Operator & Investor Checklist (checklist & red flags); Dynamics: Chapter 29: Adoption Curve & Ecosystem Dynamics and Chapter 30: Risk Analysis & Failure Modes; Appendix A: Formal Model of Verification Asymmetry & VerifyPrice and Appendix B: Practical KPIs & Telemetry Templates

VerifyPrice dashboards per workload; VerifyReach & VerifySettle boards; VerifyFlow (market realization); twelve public boards or maps (Chapter 26: Extended Telemetry), including native-buyer, common-cause, and sponsor-dependency telemetry; decentralization metrics; FeeCoverage (retained fees); Wrapper Dominance; agency preservation

Receipt datasets unverifiable or controlled by single party; wrapper-led price without native use (interpret via VerifyFlow, not as sole red line)

Readers who want the version history—what each release from v1.2 onward added, and why—will find it in Appendix J: What Changed Across Releases. It is not needed to read the argument. Readers who want to know what would actually be built, by whom, on what budget and against which acceptance tests, should go to the investment addendum, Chapter 32: Kardashev Labs: Build and Measure, which maps the Phase I deliverables onto the instruments this map lists.

Key Definitions

The core constructs that recur throughout this thesis are defined precisely here, before they are used. These are not metaphors; they are operationally specified primitives.

Definition: VerifyPrice(W) — Specification Stub

For a canonical workload WW, VerifyPrice is the public KPI vector:

VerifyPrice(W)≡(p50,t(W),  p95,t(W),  p50,c(W),  p95,c(W),  fail(W))\text{VerifyPrice}(W) \equiv \bigl(p_{50,t}(W),\; p_{95,t}(W),\; p_{50,c}(W),\; p_{95,c}(W),\; \mathrm{fail}(W)\bigr)

Where:

  • p50,t(W)p_{50,t}(W), p95,t(W)p_{95,t}(W): median and 95th-percentile verification time (seconds)

  • p50,c(W)p_{50,c}(W), p95,c(W)p_{95,c}(W): median and 95th-percentile verification cost (see cost vector below)

  • fail(W)\mathrm{fail}(W): verification failure rate (fraction of attempts that fail or timeout)

This is the canonical five-field tuple; the cost fields derive from per-run receipts via the published price model of Chapter 22: Layer 4: Truth & Work (per-run cost, then percentiles — never recomputed from percentile inputs), and the physical-component tuples published alongside are views of this vector, not competing definitions (Appendix A: Formal Model of Verification Asymmetry & VerifyPrice).

Verifier Hardware Class (Reference Machine)

TierCPURAMStorageNetworkUse Case
Laptop (baseline)4-core x86-64, 2.5GHz16 GBSSD100 MbpsDefault reference
MobileARM, 2GHz4 GBFlash20 MbpsLightweight verification
Datacenter16-core, 3GHz64 GBNVMe1 GbpsHigh-throughput nodes

All published VerifyPrice metrics specify which tier they target. The baseline is Laptop; mobile and datacenter metrics are supplementary.

Cost Vector (input view)

The five-field tuple above is what is published and what every SLO reads on. Beneath it sits the input view: per run, the verifier records a cost vector, not a scalar,

c(W)=(tcpu,  mpeak,  bnet,  ejoules,  cest)c(W) = \bigl(t_{\mathrm{cpu}},\; m_{\mathrm{peak}},\; b_{\mathrm{net}},\; e_{\mathrm{joules}},\; c_{\mathrm{est}}\bigr)

from which the canonical tuple is priced: tcput_{\mathrm{cpu}} and ejoulese_{\mathrm{joules}} enter the per-run price model of Chapter 22: Layer 4: Truth & Work to yield cestc_{\mathrm{est}}, whose percentiles are p50,cp_{50,c} and p95,cp_{95,c}; wall-clock time percentiles are p50,tp_{50,t} and p95,tp_{95,t}. mpeakm_{\mathrm{peak}} and bnetb_{\mathrm{net}} are published, not priced: they appear in the receipt and in the physical-component views, bound the reference machine a verifier must be, and enter no cost percentile. The vector is a view of the canonical tuple’s inputs, not a second definition of VerifyPrice (Appendix A: Formal Model of Verification Asymmetry & VerifyPrice).

ComponentUnitDescription
tcput_{\mathrm{cpu}}CPU-secondsTotal CPU time consumed
mpeakm_{\mathrm{peak}}MBPeak memory usage (published, not priced)
bnetb_{\mathrm{net}}KBBytes transferred (published, not priced)
ejoulese_{\mathrm{joules}}JEnergy consumed (priced)
cestc_{\mathrm{est}}USDPer-run cost from the pinned price model (priced)

Adversarial Conditions

VerifyPrice assumes realistic, mildly adversarial network conditions:

  • Network RTT: 200ms (global average)

  • Packet loss: 10% (degraded conditions)

  • Witness size: Worst-case for the workload class (prevents gaming via cherry-picked inputs)

  • DoS hardening: Verifier must handle malformed proofs gracefully (no crash, bounded resource use)

Measurement Harness

  • Reproducible benchmark suite: Open-source, deterministic test vectors for each canonical workload.

  • Signed results: Verifiers publish measurements signed by their attestation key.

  • Aggregation: Observatory collects results from diverse verifiers (geo, ASN, hardware) and publishes p50/p95 with confidence intervals.

  • Auditable: Raw measurements are archived; anyone can reproduce and challenge published metrics.

Target SLOs (Reference Design)

Workload Classp95,tp_{95,t}p95,cp_{95,c}failNotes
ZK proof (SNARK)≤5\leq 5s\leq \0.01$≤0.1%\leq 0.1\%Standard recursive/aggregated proofs
MatMul-PoUW≤10\leq 10s\leq \0.05$≤0.1%\leq 0.1\%Large matrix verification
Provenance proof≤2\leq 2s\leq \0.005$≤0.1%\leq 0.1\%Media/document attestation
Corridor settlement≤30\leq 30s\leq \0.10$≤0.5%\leq 0.5\%Includes finality confirmation

These are targets, not guarantees. Actual SLOs are published per workload and adjusted as technology improves.

Why this matters: VerifyPrice is the hinge that determines whether proofs and verified compute behave as commodities (publicly checkable) or as platform IOUs (trust someone’s claim). If r(W)=v(W)/p(W)≪1r(W) = v(W)/p(W) \ll 1, verification is cheap relative to production and markets can form; if r(W)→1r(W) \to 1, the market is back to “trust the prover.”

Definition: Work Credits

A Work Credit is a typed, prepaid claim on reserved future service — privacy settlement, proof generation, or verified compute — owed by a specified provider or provider pool. Its issuance requires an admissible capacity commitment and an atomic reservation against outstanding obligations. Verified fulfillment extinguishes the claim and produces a receipt. The receipt is evidence of fulfillment and creates no further service obligation.

Lifecycle:

  1. Commit. A named provider or constituted pool commits capacity for workload WW at tier TT over a stated delivery window, with Facility Energy Receipts and Facility Capacity Receipts behind it.

  2. Sell and reserve, atomically. The sale and the reservation are one step: no valid sold claim exists without its capacity reserved against every outstanding claim competing for the same capacity.

  3. Deliver and verify. Delivery passes the registry acceptance criterion, with VerifyPrice(WW,TT) and the other SLOs within bounds.

  4. Extinguish and receipt. Verified delivery retires the claim and issues the Work Receipt.

Cancellation, expiry, default, and refund follow the terms written in the claim. A failed delivery becomes neither an open-ended promise nor a claim on the base asset.

Uses: a credit can be redeemed for its service, transferred, or pledged as collateral where its tier permits (Chapter 22: Layer 4: Truth & Work). Two neighbours are not Work Credits: a transferable record of historical work is a Work Receipt, which is evidence and not a claim, and advance proceeds that finance capacity not yet built are project finance, named and treated separately (Chapter 3: The World Forces New Monetary Primitives). Work Credits carry no governance weight: the franchise is time-locked base asset only (Chapter 25: Layer 6: Governance & Telemetry).

Energy anchoring: A credit cannot be sold without an admissible capacity commitment, and it cannot be extinguished without delivering work that passes verification, so the cost of honoring one is bounded below by the energy and hardware that work requires. The difference from SHA-256 PoW is that this work has an external buyer—which is the point of the design and also its cost, since a buyer can be regulated, subsidized, or coerced in a way that a hash puzzle’s absent buyer cannot (Chapter 34: Objections & Responses). Each credit references a Facility Energy Receipt (FER) chain; if the referenced plant drifts out of profile (PUE >1.5> 1.5, carbon intensity >> threshold, etc.), the credits reserved on it are flagged.

Deliverability bound: Outstanding claims are capped by stress-adjusted DVC for the specified workload and tier over the delivery horizon, not by gross energy, installed hardware, or benign-state proof throughput. DVC supports the reservation limit; it does not guarantee performance.

Non-debt property: Work Credits do not promise fixed coupons or redemption in fiat terms. Value floats with demand for triad capacity.

Failure mode: If VerifyPrice regresses materially, new sales halt until SLOs recover. Outstanding credits remain claims on their obligors under their stated terms and may trade at a discount, reflecting the network’s degraded utility.

Definition: Instrument Hierarchy

The thesis distinguishes five categories of objects:

Evidence Objects (not scarce, not money):

  • PIDL Receipt: Proof that a specific interaction occurred. Copyable, verifiable, not scarce.

  • Work Receipt: Proof that a unit of work was completed. Evidence of past work; confers no future rights.

  • FER/FCR: Evidence about energy, infrastructure, resilience, and the edge capacities used to compute DVC.

Capacity and Service Objects (typed claims, not presumed SoV):

  • Work Credit / WC-Voucher: Prepaid or transferable access to specified triad capacity under workload, location, hardware, SLA, and delivery terms. May expire. Useful for service procurement and hedging, not presumed savings.

Duration-Bearing Credit:

  • Project Notes and Capacity Bonds: Explicit credit claims with maturity, covenants, default states, and loss waterfalls. Proof-audited, but never transferred onto the base asset.

Derivatives and Operating Claims:

  • LP/Staking Shares: Positions granting fee, slashing, corridor, or validator exposure. They are not monetary objects.

Conditional Monetary Candidate:

  • Base Asset: The native fee and settlement unit. It is evaluated for monetary premium only if DVC, non-bypassability, holder quality, agency, and the remaining chain conditions pass.

Hierarchy rule: Throughout this thesis, “the asset” refers to the base asset unless otherwise specified. Evidence, service claims, duration-bearing credit, and derivatives do not inherit its conditional monetary candidacy.

Definition: Lawful Privacy

Lawful privacy is the design principle: default privacy with optional, user-controlled disclosure.

Concretely:

  • Default state: Transactions, identities, and flows are encrypted and unlinkable without explicit consent.

  • Disclosure mechanisms: Viewing keys, auditable receipts, and selective-disclosure proofs allow holders to prove specific facts (e.g., “I paid X to Y for purpose Z”) without exposing the full transaction graph.

  • No backdoors: The protocol has no protocol-level master key, regulatory escrow, or “lawful intercept” API. The holder’s own spending-key root is a master key for its own tree and is never disclosed; per-epoch keys and per-note proofs are the units of disclosure (Chapter 23: Layer 5: Value & Settlement). Disclosure is always at the holder’s discretion.

Why “lawful”: The term signals that privacy is compatible with compliance when the holder chooses to disclose, without requiring surveillance infrastructure. Regulated entities can satisfy audits via viewing keys; the protocol itself remains neutral.

Coercion boundary: Lawful privacy is a technical guarantee. It cannot prevent social or legal coercion to disclose viewing keys. What it guarantees is that (1) non-custodial routes exist, (2) disclosure cannot be forced at the protocol level, and (3) coercion surface is minimized by keeping data encrypted by default.

Quick Reference: Political Economy & Physical Capacity

These terms carry the thesis’s political-economy and physical-capacity vocabulary. Full treatments appear at the cited locations; short forms are collected here for quick reference.

Quick Reference: Physical Sovereignty & Substrate

These terms make the physical layer falsifiable and name the closed-stack competitor. Full treatments appear at the cited locations.

  • Energy & Physical Interdiction (Chapter 5: Threat Model): adversary class using curtailment, rationing, tariff discrimination, interconnection denial, and load prioritization to raise verification cost without prohibiting cryptography.

  • Sovereign Optionality (Os\mathcal{O}_s) (Chapter 17: Layer 0: Verifiable Machines & Energy): capacity-weighted index from Facility Capacity Receipt fields; feeds risk haircuts and Red Line 13.

  • Disruption-Adjusted VerifyPrice (Chapter 17: Layer 0: Verifiable Machines & Energy): probability-weighted verification cost across physical disruption states; resilience is subordinate to constitutional VerifyPrice SLOs.

  • Red Line 13: Energy Sovereignty Failure (Chapter 30: Risk Analysis & Failure Modes): verification affordability becomes a sovereign policy variable; monitors upstream of Red Line 1.

  • Closed vs. open sovereign stack (Chapter 33: The Closed Sovereign Stack): convergent trust-minimization applied to matter; inverted locus of sovereignty (state vs. participant).

  • Real-Resource VerifyPrice SLO vs. Physical VerifyPrice (Appendix A: Formal Model of Verification Asymmetry & VerifyPrice, glossary): the constitutional cost band on verifying receipts in real resources on reference hardware (Red Line 1) vs. the cost to audit FCR infrastructure claims (Red Line 10).

Quick Reference: Market Realization & Price Formation

This is the market-structure vocabulary for reasoning about price without confusing it with adoption. Full treatments appear at the cited locations.

Contents