The Triad as Monetary Base

Traditional monetary regimes pick a base reality and build promises on top of it:

• Gold: geology + metallurgy.

• Fiat: law, taxation, and war.

• Bitcoin: thermodynamics and code.

Each regime implicitly answers two questions:

1. What counts as real work?

2. What object or capacity will we treat as the canonical memory of that work?

In a civilization where intelligence is largely machine-executed and verification can be cheap and public, the answer shifts: work is what machines can do and humans can verify cheaply, and the “object” that records that work no longer has to be a metal or a pure ledger entry. It can be a capacity.

This thesis treats three capacities as monetary primitives:

• Privacy: censorship-resistant settlement that preserves agency.

• Proofs: portable attestations of computation and provenance.

• Compute: useful work wrapped in succinct guarantees.

Each is:

• Indispensable in a dense digital economy (no safe commerce without privacy; no safe coordination without proofs; no AI without compute).

• Verifiably scarce at any point in time (bandwidth, cycles, proof capacity are bounded by physics and capital).

• Cheap to verify (a user can check whether they have privacy, a valid proof, or a verified FLOP without trusting a platform).

The physical and service base in this frame is the networked capacity to deliver Privacy, Proofs, and Compute under adversarial conditions. It is not itself money. Those services may support an associated bearer base asset as a conditional monetary candidate only if all nine links pass; Work Credits remain typed claims on service or capacity.

A few distinctions help:

Services vs. instruments:
DVC measures how much verifiable Privacy/Proofs/Compute per unit time the stack can deliver at target SLOs. Work Credits slice specified service capacity into transferable claims; staking and LP positions are derivatives or operating claims; the separate base asset is the only monetary candidate.

Nominal vs. real:
Nominal pricing of the triad will oscillate in terms of fiat and BTC. Real value is “does this capacity still buy me censorship-resistant settlement, proofs, and verified FLOPs when repression and AI get worse?”

Symbol vs. utility:
Gold and BTC partly trade as symbols. The triad trades as plumbing: “can I still pay people, prove things, and run intelligence without asking permission?”

For the associated base asset, recurring service demand is necessary but insufficient:

• Treasuries and individuals purchase private settlement to escape surveillance and yield-curve control.

• Platforms, enterprises, and states purchase proofs to secure provenance, compliance, and audit trails in an AI-polluted information environment.

• AI labs, agents, and applications purchase verified compute to sell trustworthy services.

The claim is not that the triad services behave like a reserve asset. “Private Money” and “AI Money” are analytical lenses on settlement and compute demand. Monetary premium, if any, belongs to the associated base asset after deliverability, non-bypassability, holder quality, and the remaining chain conditions pass.

The Conditional Chain, End to End

Chapter 1: Introduction promised that the thesis would establish its claim through a conditional chain rather than an assertion. That chain is defended link by link across the whole thesis, which makes it easy to lose. This section walks it once, in one place, and says where each link is argued and what would sever it.

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, which is why the weak ones are named explicitly at the end rather than leaving the reader to find them.

1. Utility demand exists and persists. A dense, synthetic-media, AI-mediated economy must keep buying private settlement, portable attestations, and verified compute through every cycle—including, and especially, under financial repression (Chapter 3: The World Forces New Monetary Primitives, Chapter 9: Privacy as Private Money, Chapter 10: Proofs as Attestation Money, Chapter 11: Compute Through the “AI Money” Lens).

   One mechanism for persistence is named in Chapter 7: The Delegation Economy: Who Buys Verification: work decomposed across machine agents generates a verification purchase at every consequential delegation hop that crosses a trust perimeter, and the number of such boundaries does not deflate with compute. It is a mechanism, not evidence; the series that would confirm it, Cross-Perimeter Share, is specified and not yet computable.

   Severed if: the demand turns out to be cyclical discretionary spend rather than structural necessity, or delegation stays inside operator fleets that need no portable receipt.

2. Demand standardizes into canonical work. Diffuse demand becomes an economic unit only when workloads are specified precisely enough that two providers are selling the same thing—canonical workload registries, hardware profiles, and SLA tiers (Chapter 22: Layer 4: Truth & Work).

   Delegation supplies a standing pressure in this direction, since an agent cannot delegate what it cannot specify (Chapter 7: The Delegation Economy: Who Buys Verification); a specification private to one fleet is still bespoke.

   Severed if: workloads stay bespoke, so no fungible unit forms and there is nothing to price.

3. Work produces cheap-to-check receipts. Standardized work emits portable artifacts—PIDL receipts binding claim, proof, workload ID, tier, and timestamps—and verification stays far cheaper than production, $r(W) = v(W)/p(W) \ll 1$ (Chapter 22: Layer 4: Truth & Work, Appendix A: Formal Model of Verification Asymmetry & VerifyPrice).

   Severed if: verification cost creeps toward production cost, at which point “anyone can verify” collapses into “trust the prover.” This is Red Line 1, the hinge (Chapter 30: Risk Analysis & Failure Modes).

4. Receipts represent stress-deliverable service. A receipt is evidence, not capacity. For each disruption scenario, Delivered Verified Capacity traces the full path from energy and fuel through firm power, switchgear, cooling, hardware, network, workload, proof, verification, settlement, and usable service; service-claim issuance is bounded by the surviving max flow, with the active binding constraints named (Chapter 17: Layer 0: Verifiable Machines & Energy).

   Severed if: gross installed capacity or benign-state output materially exceeds the service that survives substitution latency and common-cause failure.

5. Receipts enable markets. Cheaply checkable receipts over deliverable service let strangers transact without trusting each other: proof factories, neutral routers, SLA escrow and slashing, and procurement of proofs and verified FLOPs as spot or forward capacity (Chapter 22: Layer 4: Truth & Work, Chapter 24: The Modular Stack).

   Severed if: routers, provers, or matching engines capture the market and rent replaces work—Red Line 3 territory.

6. Markets produce fee flows. Working markets generate recurring, measurable revenue rather than one-off grants or subsidies, visible as fee-coverage ratios against the security budget (Chapter 22: Layer 4: Truth & Work, Chapter 26: Extended Telemetry).

   Severed if: fee coverage collapses and workload demand proves to be speculative rather than budgeted.

7. Fee flows accrue to a scarce asset—only under non-bypassable rules. This is the load-bearing link and the one most theses skip. Utility does not become money by being useful. The Value Capture Lemma states the reference design’s five channels: required fee medium, meaningful burn or retirement, staked collateral, disciplined issuance, and no bypass channel delivering equivalent service without touching the asset (Chapter 13: Why Hold the Base Asset?, Chapter 13: Why Hold the Base Asset?).

   Severed if: users obtain equivalent triad capacity through hyperscalers, stablecoins, or custodial APIs without the asset—Red Line 6 (Chapter 30: Risk Analysis & Failure Modes, Chapter 28: Operator & Investor Checklist).

8. A monetary-risk warehouse forms. Gross native demand is not a monetary anchor. A persistent, self-custodied, loss-bearing, regime-responsive constituency must retain balances, lengthen holding periods, and accumulate countercyclically (spending on the service during stress counts as use, not exit) rather than merely acquire fees just in time, recycle operator inventory, satisfy collateral rules, or hold wrappers (Chapter 26: Extended Telemetry).

   A cohort must also be classified by principal before it counts: software agents can satisfy every measurable clause of this link, and ten thousand of them running one policy are one holder (Chapter 7: The Delegation Economy: Who Buys Verification).

   Severed if: native demand disappears into immediate sell-through, leverage, wrappers, or forced deleveraging during the very stress in which the asset is meant to preserve agency, or the constituency proves to be one operating policy at many addresses.

9. A scarce, captured, anchored asset may earn a store-of-value premium. If the asset also remains liquid, neutral, verifiable, legally holdable, and agency-preserving, it can plausibly earn monetary premium (Chapter 35: Why a Base Asset Behind These Could Become Money, Chapter 16: SoV Evaluation Framework, Chapter 4: First Principles: What a SoV Must Survive). This final link, not fee accrual or gross demand, is where the premium is argued to live, through three mechanisms: pledgeability without due diligence (Chapter 13: Why Hold the Base Asset?), denomination (Chapter 13: Why Hold the Base Asset?), and the state-contingent holder-side service flow (Chapter 13: Why Hold the Base Asset?), each with its own instrument and red line. The third must first beat its strongest alternative, Bitcoin converted on the day, and the access experiment tests whether it does (Chapter 13: Why Hold the Base Asset?).

   Severed if: any of the nine store-of-value requirements fails, telemetry showing them is captured, or any of the three mechanisms reads null on its instrument, as its red line specifies; if only outsiders decline to reckon in the unit, the link is weakened rather than severed.

The Chain Says Nothing About Price

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. Wrappers, leverage, dealer hedging, and allocation mandates can move price with no protocol use at all, in either direction (Chapter 13: Why Hold the Base Asset?). The chain is measured on the protocol, capacity, and native-buyer boards; price is interpreted separately through VerifyFlow (Chapter 26: Extended Telemetry) and never cited as evidence for the chain.

The chain rests on something beneath it.

Links 2 through 6 consume bulk power, and link 3 (the verification hinge) is denominated in real resources on reference hardware. That makes the chain dependent on conditions that states partly set: energy availability and pricing, the obtainability of unprivileged reference hardware, and the continuity of every conversion edge through usable service (Chapter 5: Threat Model, Chapter 17: Layer 0: Verifiable Machines & Energy). Sovereign Optionality measures pathway diversity; Delivered Verified Capacity measures surviving flow. The chain is not suspended in mathematics; it is bolted to a grid and held on balance sheets.

Where the chain is weakest.

Honest accounting rather than uniform confidence:

Link-by-link strength of the conditional chain. Six links remain Medium or Medium (conditional): standardized work and market formation are engineering-maturity risks; stress-deliverable service is a physical-topology and common-cause risk; non-bypassability is an unmeasured magnitude; the native holder anchor is an unproven risk warehouse; and monetary premium remains conditional on the entire chain.

The medium ratings are the point.

Non-bypassability is a magnitude: bypass is never impossible, only priced, and the marginal buyer’s willingness to pay for the protocol’s differential properties has not been estimated. Delivered service is not nameplate capacity: substitution latency and common-cause cuts can erase apparently diverse supply. Holder demand is not risk absorption: fee purchases, burns, collateral, and wrappers can coexist with no constituency willing to own the asset through a drawdown. The premium, if it exists, comes from link 9 through three mechanisms the thesis argues: acceptance without due diligence (Chapter 13: Why Hold the Base Asset?), reckoning in the unit (Chapter 13: Why Hold the Base Asset?), and the state-contingency of differential value (Chapter 13: Why Hold the Base Asset?). Does the thesis size them? No. Two questions stay open beside them: whether the convenience yield, if it exists, exceeds the premium gold or Bitcoin already carries, and whether the open duration warehouse (Chapter 34: Objections & Responses) can finance long-lived infrastructure without concentrated credit intermediaries. Ratings that go up are self-congratulation; ratings that identify the unmeasured bridges carry information.

Four questions, and where the answers branch.

Read from top to bottom, the nine links look like a procession in which each success hands the next its premise. The thesis already allows every branch: the stack is fundable as public infrastructure whether or not a coin follows (Chapter 32: Kardashev Labs: Build and Measure), Work Credits remain service claims however well they perform (Chapter 12: Work Credits: Reserved Service Claims), and the architecture comparison leaves open whether the three services share one asset at all (Chapter 8: The Triad and the Monetary Candidate). The links answer four separate questions (Chapter 8: The Triad and the Monetary Candidate), and a yes to one does not carry a yes to the next. Services can succeed without the asset capturing their value; the asset can capture value without offering its holders anything a buyer on the day lacks; and a held asset can attract demand that never becomes the self-custodied, agency-preserving use the ninth requirement asks for (Chapter 4: First Principles: What a SoV Must Survive). Each exit in Chapter 8: The Triad and the Monetary Candidate ends in an outcome the thesis already names.

The procession is one path through a tree.

• 1. Useful services links 1–5

  stops here

  Infrastructure without money. Services paid in fiat or stablecoins; fundable with no coin (Chapter 29: Adoption Curve & Ecosystem Dynamics, Chapter 32: Kardashev Labs: Build and Measure)

  yes

• 2. Asset value capture links 6–7

  stops here

  A service asset. A fee claim and a collateral lockup, valued as cash flows (Chapter 13: Why Hold the Base Asset?); Warning 13’s reclassification (Chapter 30: Risk Analysis & Failure Modes)

  yes

• 3. A distinct holder service link 9, the holder-side flow

  stops here

  A balance held for the band. Useful where conversion fails and native settlement survives (Chapter 13: Why Hold the Base Asset?); pledgeability and denomination read separately

  yes

• 4. Monetary use consistent with the mission links 8 and 9

  stops here

  Holders without users. Demand met through wrappers and custody: a financial product rather than agency-preserving money (Chapter 13: Why Hold the Base Asset?)

  yes

• A defensible monetary candidate price still not evidence (Chapter 13: Why Hold the Base Asset?)

What follows defends links 7 through 9, where the monetary argument actually lives. The stack chapters defend links 2 through 6 by building and measuring what supplies them (Chapter 6: Layers of the Cypherpunk Stack), and the telemetry and the red lines make every link falsifiable (Chapter 26: Extended Telemetry, Chapter 30: Risk Analysis & Failure Modes).

Topological Scarcity and the Pressure–Capacity Corridor

Topological Scarcity Lemma

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.

Aggregate abundance and local scarcity can therefore coexist without contradiction. Crude is not diesel when refining is the minimum cut; savings are not duration absorption when no balance sheet can hold DV01; installed accelerators are not verified service when power, cooling, firmware, connectivity, verification, or settlement fails. What determines the service is the topology: the transformation path, location, actor, and horizon.

The physical-conversion example is adapted selectively from Doomberg’s Endangered Specious [Doomberg 2026b]; the duration-absorption example from Michael Green’s Anchors Aweigh, My Boys [Green 2026b]. Both are analyst commentary used for mechanism rather than quantities. The lemma and its application to verified service are this thesis’s own.

Let $R$ denote regime pressure, $\Delta(R)$ the holder’s differential value over the best institutional substitute, $A_{\mathrm{full\mbox{-}stack}}(R)$ the availability of the complete service path under that pressure, and $H(R)$ the holder’s practical ability to self-custody, transact, prove, and exit. The monetary service scales with the product of the three, on the product-form premise

$$\Pi_{\mathrm{monetary}}(R) \;\propto\; \Delta(R)\times A_{\mathrm{full\mbox{-}stack}}(R)\times H(R).$$

This is the Pressure–Capacity Corridor. Its likely shape is an inverted U, not a crisis escalator. At low pressure, courts, custodians, and indemnitors work, so $\Delta$ is thin. At moderate pressure, substitutes weaken while the open stack and holder remain operational, so differential value can rise. At extreme physical or political pressure, power, networks, hardware, liquidity, custody, or exit may fail and the service falls with them.

More crisis does not imply more premium.

$H(R)$ has an agent form. A software agent’s practical ability to self-custody, transact, prove, and exit is bounded by its operator’s: a fleet instance inherits one jurisdiction’s pressure all at once, while independently operated agents inherit it operator by operator. That is the coercibility split of Chapter 7: The Delegation Economy: Who Buys Verification in one symbol, and it is why a holder base made of agents must be read by operator class before $H(R)$ is credited to it. $A_{\mathrm{full\mbox{-}stack}}(R)$ is read the same way, because redundant paths under one controller, creditor, or jurisdiction fail under the same pressure and count as one path (Chapter 26: Extended Telemetry).

The Triad Coherence Test

Privacy settlement, portable proof, and verified compute are different goods with different users, bottlenecks, collateral needs, political risks, and duration warehouses. A common asset is justified only if shared security, settlement, liquidity, and transaction-cost benefits exceed cross-subsidy, governance, and wrong-way-risk costs.

Triad architectures under test; none is pre-selected.

For each architecture ask: Do the services share a security budget and users? Does demand for one improve the economics of the others? Are bottlenecks complementary or correlated? Does common settlement reduce transaction costs more than it creates cross-subsidy? Can one constitution credibly govern all three? Does one service dominate issuance, fees, or political risk? Architecture A is a candidate, not the thesis.

Monetary Objects and Value Capture

The thesis claims that triad capacity can earn a “durable store-of-value premium.” For that claim to be testable, four questions must be answered without poetry:

1. What exactly is the asset?

2. What do users pay in?

3. How does holding capture value?

4. Why does value not leak entirely to operators?

Question 1: What is the asset?

The triad stack can issue several kinds of holdable instruments:

Instrument hierarchy. Utility, evidence, credit, derivatives, and the conditional monetary candidate remain distinct.

The base asset is only a conditional monetary candidate: the unit in which fees may be paid, burns may occur, and collateral may be posted. Work Credits can be valuable, transferable, workload-specific, location-specific, SLA-specific, and temporally perishable without becoming savings instruments. FCRs, FERs, and PIDL receipts are evidence; project notes warehouse duration and bear default risk; LP and staking positions are derivatives or operating claims.

A terminology contract.

This thesis uses two distinct words that are easily confused, and the distinction carries real analytical weight:

• Native instruments are protocol-internal claims: the base asset, typed Work Credits, staking and LP positions, corridor claims, capacity vouchers, and evidence artifacts. They touch the protocol, but only the base asset is evaluated as a monetary candidate.

• External financial wrappers are conventional market products written on the asset: spot ETFs, exchange-traded products, treasury companies, custodial balances, futures, options, swaps, and leveraged or inverse ETPs. They do not touch the protocol. Holding them exercises nothing.

Both are sometimes called “wrappers” in casual usage. From here forward, “wrapper” without qualification means an external financial wrapper. The full object hierarchy runs from physical capacity out to recursive financial claims, and monetary treatment differs sharply along it.

Object hierarchy from base capacity to recursive financial claims. Monetary properties do not survive the descent: a daily-reset leveraged wrapper cannot inherit the underlying asset’s store-of-value status, because its return depends on the path, not merely the endpoint (Appendix H: Formal Model of Market Realization, Wrapper Flows, and Price Capture).

How to read Questions 2–4.

The answers below are stated in the reference-design register. They specify routing rules: where fees go, what must be locked, what may not be inflated away. They are design commitments, not findings, and there are two things they deliberately do not do. They do not establish that the routed fee is large: that is the level question, taken up in Chapter 13: Why Hold the Base Asset?, where the sustainable fee is bounded by differential value $\Delta$ rather than by anything in this section. And they do not establish that any of this is monetary premium rather than a cash-flow claim: Chapter 13: Why Hold the Base Asset? shows why that reading fails, and Chapter 13: Why Hold the Base Asset? relocates the monetary claim to a holder-side service flow. The percentages below are illustrative of a design space, not measurements of a market.

Question 2: What do users pay in?

In the reference design, all triad services are quoted and settled in the base asset:

• Proofs: paid to provers in the base asset; a published share retired.

• Privacy settlement: corridor fees paid in the base asset; a published share retired.

• Verified compute: inference and MatMul paid in the base asset; a published share retired.

• Staking/collateral: provers, routers, and LPs lock the base asset to participate.

This is a routing rule, not a demand theorem. It creates transactional demand only to the extent that users cannot route around it (Value-Capture Condition 1). Even where they cannot, the demand it creates is for a medium of settlement held for seconds, not for a store of value held through a cycle. Chapter 13: Why Hold the Base Asset? bounds what that toll can be, and Chapter 13: Why Hold the Base Asset? names the incumbent that already routes around it. Nothing in this list is evidence of moneyness.

Question 3: How does holding capture value?

Fee value reaches holders through four routing channels. Each is a cash-flow or lockup mechanism; none is monetary premium, and the thesis says so at Chapter 13: Why Hold the Base Asset?:

1. Fee retirement (burn) (30–50% of fees): a pro-rata buyback. It reduces net issuance only when retired fees exceed scheduled issuance, which at early-phase fee coverage they will not; it is published as its own series and read as such.

2. Staker yield (20–40% of fees): income for holders who stake, a dividend on a productive claim.

3. Operator share (20–40% of fees): incentive for provers, routers, and LPs.

4. Collateral requirements (10–20% of capacity value): immobilizes float while operators remain solvent and choose to keep operating; Chapter 13: Why Hold the Base Asset? shows why it is a slope effect on price impact rather than a valuation floor or proportional accrual, and bounds the fixed dollar quantity it can lock.

The first three channels are a partition of one fee pool, not three independent receipts: burn share, staker yield, and operator share must sum to 100% of every fee collected. The bands above are alternative interior choices within that partition, not independent ranges, and any point allocation, such as Design A’s 40/30/30 split (Chapter 8: The Triad and the Monetary Candidate), must close the identity. Reading the bands as additive would sum the maxima to 130% of the pool, which is not an allocation the design can make. The reference design this document actually works from is fixed once, in Chapter 25: Layer 6: Governance & Telemetry: 70% to capacity providers and the stakers who delegate to them, 20% retired, and 10% to an assurance budget that funds Layer 0 sampling, audits, and security review. Its 20% burn sits below the band above deliberately, as the harder case for the value-capture claim (Chapter 22: Layer 4: Truth & Work), and every worked example in Parts III–V uses that point; Design A’s split is an alternative inside the bands, not a second reference.

Question 4: Why does value not leak entirely to operators?

The “utility token trap” occurs when operators capture all economic value while token holders merely provide exit liquidity. The routing rules are designed so that a positive fee, if one exists, does not leak entirely to operators:

• Fee retirement: 30–50% of fees are retired pro rata to all holders, a buyback with the accrual (not moneyness) reading Chapter 13: Why Hold the Base Asset? gives it.

• Staking yields: Passive holders can stake to earn fee share without operating infrastructure.

• Collateral requirements: Operators must hold significant base-asset collateral, aligning their interests with holders.

• Governance rights: Holders vote on fee splits, issuance changes, and protocol upgrades, within the constitutional constraints of Chapter 25: Layer 6: Governance & Telemetry.

• Issuance constraints: Base-asset issuance follows the constitutional schedule and is independent of Work Credit dynamics; it is Work Credits that are sold only against committed, reserved capacity, with any sale beyond deliverable capacity rejected and visible in dashboards.

Net effect, routing only: these rules route a fee of size $f \cdot Q$ to retirement, staking, and operator share. Whether $f$ can be positive at all is a function of differential value $\Delta$, not of routing; whether the routed revenue constitutes monetary premium is a separate question taken up in Chapter 13: Why Hold the Base Asset? and answers in the negative at Chapter 13: Why Hold the Base Asset?.

Three Reference Designs

To make the thesis testable, it commits to three concrete designs. Implementations may vary, but at least one must be viable for the SoV claim to hold.

Design A: Base Token as SoV (Primary)

• Issuance: Fixed schedule with halvings (like BTC), set ex ante.

• Fee medium: All triad services priced in base token.

• Burns: 40% of fees permanently destroyed (a point choice inside the 30–50% reference band).

• Staking: 30% of fees to stakers; 10–15% collateral requirement.

• Operators: 30% of fees to provers/routers/LPs.

• Governance: Token-weighted voting on parameters.

SoV properties: Credible scarcity (capped + burns), native demand (fees), duration-neutral (no coupons), cheap verification (VerifyPrice dashboards).

Risk: If demand stalls, burns decline and scarcity weakens.

Design B: Work Credits as Capacity Vouchers (Hedge Instrument)

• Issuance: Sold against committed capacity (FERs + FCRs), reserved atomically; outstanding claims bounded by stress-adjusted DVC; no fixed cap.

• Redemption: Extinguished by verified delivery at the contracted tier and rate; a priority tier is a term of the contract, paid for when the credit is bought.

• Expiry: Each credit carries its delivery window; unexercised credits expire or refund on stated terms, which prevents hoarding and bank-run dynamics.

• Transferable: Yes, but primarily used for cost hedging, not long-term savings.

Use case: Enterprises hedge against compute cost spikes; treasuries lock in future settlement capacity.

Not a SoV: Supply expands with capacity; expiry prevents indefinite accumulation. This is infrastructure hedging, not a store of value.

Design C: Triad Index Token (SoV Candidate)

• Backing: Diversified revenue streams across privacy corridors, proof pools, and compute markets.

• Value capture: Protocol revenue used for periodic buyback-and-burn or dividend distribution.

• Issuance: Fixed supply; no new minting after genesis.

• Governance: Index holders vote on revenue allocation and rebalancing.

SoV properties: Diversified exposure to triad demand; fixed supply; yield via buybacks or dividends.

Risk: Concentration in specific corridors or proof markets; governance capture.

Which design does the thesis endorse?

None by default. These instrument designs sit inside the broader architecture comparison of Chapter 8: The Triad and the Monetary Candidate. A fixed-supply base token may be tested as the monetary candidate; capacity vouchers remain service hedges; an index token is a revenue-bearing security whose buybacks or dividends do not establish moneyness. The text uses “base asset” for the monetary candidate and “Work Credit” only for a typed capacity or service claim.

What actually differs, and who loses.

The three designs are not three shades of the same bet; each one moves the risk onto a different balance sheet. Design A concentrates it in the base asset: if demand stalls, burns decline, and the scarcity story thins with it; the holder discovers that a burn schedule is a claim on volume, not a property of the token. Design B pushes the risk onto the service buyer: capacity vouchers hedge compute cost beautifully until capacity is scarce in exactly the state the buyer hedged for, at which point delivery terms rather than price are the binding constraint, and the hedge is only as good as the stressed path behind it. Design C hands the risk to governance and to the revenue mix: an index token is a claim on whatever the protocol happens to earn, so concentration in particular corridors or proof markets is not a footnote to the thesis but the thesis, and buybacks do not convert a revenue stream into money (Chapter 13: Why Hold the Base Asset?). Watch the same three numbers in all three cases: fee share actually paid in the native asset, net supply after burns, and the share of exposure sitting in wrappers (Chapter 13: Why Hold the Base Asset?). They matter because Chapter 13: Why Hold the Base Asset? takes up the question these boxes deliberately do not answer: not where the fee is routed, but whether there is a fee to route.

Cash used to be default private money: anonymous, bearer, final on receipt. In a world of KYC’d banks, programmable payments, and networked surveillance, that role has decayed. At the same time, the repression playbook (negative real rates + capital controls) makes bearer-like savings economically necessary, not ideologically optional.

“Privacy” in this thesis is not romantic opacity; it is the ability to hold and move value without chokepoints, plus the option to disclose on your own terms.

Interiority has a history.

The capacity this chapter argues for has a five-hundred-year arc behind it, and the arc is worth naming because it reframes what is being defended. The private interior self is not a natural constant that technology is eroding; it is, on the account of the orality-literacy literature [Ong 1982], substantially a product of a technology: sustained silent reading, a practice individuals had to acquire, that only became mass practice with print. Interiority was an externality of a medium, and it has since been mistaken for the default state of persons. On that reading, surveillance does not violate a natural privacy so much as withdraw a subsidy that a particular medium had been paying, quietly, for centuries. The implication for this chapter is not that the case for private settlement strengthens — the repression economics stand on their own — but that the loss is larger than it looks: what is being unbuilt is not an amenity but a specific, technology-dependent form of the person that took centuries to build and that no one planned. Defending it is therefore also not an amenity.

Concretely:

Bearer-like holding:
Keys, not accounts, define control. Custodians may exist, but custody is an optional service, not a mandatory chokepoint.

Non-custodial settlement:
Cross-asset flows (BTC$\leftrightarrow$XMR today; BTC$\leftrightarrow$shielded-ZEC when a corridor exists, Chapter 23: Layer 5: Value & Settlement) execute as atomic swaps or corridor protocols; neither side needs to trust a centralized intermediary.

Auditable by consent:
Viewing keys and structured receipts allow specific flows to be disclosed to auditors without exposing the entire graph.

When these properties hold, private settlement capacity itself starts to behave like a monetary asset:

• A treasurer facing capital controls is not just asking “what’s the yield?” but rather, “can I still get value to my people next year if on-/off-ramps are throttled?”

• A dissident journalist or NGO cares less about upside and more about “will this still be here and spendable if my local banks freeze?”

Blockchain may be waiting for its SSL moment. The analogy is suggestive: in 1994, putting credit card information on the Web seemed reckless until SSL made encrypted commerce viable. E-commerce grew into a multi-trillion-dollar industry once confidentiality became default. Today, most public blockchains are “public by default” the way HTTP was—every transaction visible, every address linkable. Privacy is plausibly the bottleneck for mass institutional adoption.

The institutional version is straightforward: no enterprise wants payroll, vendor rates, or treasury operations visible by default. The unlock is one-click, non-custodial BTC$\leftrightarrow$XMR (and BTC$\leftrightarrow$shielded-ZEC once that corridor exists) with refund-safe UX and clear settlement analytics—privacy as a product, not a promise.

In that environment:

• The rails (privacy corridors, shielded pools) earn fees for providing unseizable, auditable settlement capacity.

• The claims on those rails (e.g., corridor LP positions and Work Credits) are service, operating, or derivative claims. They may be held, but are not presumed stores of value.

You can think of Private Money as:

“Rights to future, censorship-resistant, auditable settlement capacity.”

The SoV properties from Chapter 4: First Principles: What a SoV Must Survive map naturally:

• Credible scarcity. Capacity is constrained by bandwidth, cryptographic verification costs, and capital at risk.

• Cheap public verification. Anyone can verify that a transaction was correctly formed, swapped, or refunded.

• Censorship-resistance & portability. Flows ride over non-custodial corridors; exit options span multiple assets and jurisdictions.

• Neutrality & permissionlessness. Adversarially diverse relays, routers, and LPs; public metrics on concentration.

• Native demand. Demand is created by repression itself.

• Lawful privacy. Viewing keys + PIDL receipts mean regulated entities can prove compliance without deanonymizing entire networks.

• Duration-neutrality. Claims participate in fee flows and scarcity premiums, not fixed coupons.

• Asset-level value capture. Fees, collateral, and settlement are denominated in the base asset, so consuming the service touches the asset rather than bypassing it (Chapter 13: Why Hold the Base Asset?).

• Agency preservation. Selective disclosure and non-custodial settlement equip the holder rather than managing them (Chapter 4: First Principles: What a SoV Must Survive).

The ninth requirement carries a capability reading the eighth does not, and the distinction matters because a ledger can satisfy the formal properties while failing the practical one. Formal access — a valid balance, a working key, a legal right to transact — is not the same as capability: command over the necessities of an independent life. A perfectly accurate ledger can faithfully preserve an unequal starting state; making claims harder to alter does not broaden who can acquire them (Chapter 34: Objections & Responses). The requirement as enforced (Chapter 26: Extended Telemetry) therefore reads on both layers: the Agency Preservation Board tracks non-custodial usage share and disclosure scope — the formal layer — and the participation telemetry of Chapter 3: The World Forces New Monetary Primitives tracks whether users can in practice acquire and hold meaningful claims through wages rather than inheritance or incumbency — the capability layer. A stack that passes the first and fails the second has hardened the incumbent distribution more efficiently than fiat did.

On a balance sheet, Private Money can coexist with BTC and fiat, but it plays a different role:

• BTC: thermodynamic base, global risk asset, macro hedge.

• Fiat: near-term unit of account, legal tender, credit medium.

• Private Money: repression-hedged rail, a way to ensure you can still pay and be paid without being fully seen.

If Privacy is the hull, Proofs are the receipts.

Proofs Are Not Truth

Proofs are bounded attestations, not truth. A proof can show that a computation followed a circuit, that a file descends from a signed provenance chain, or that a settlement rule executed correctly. It cannot prove that a camera was pointed at what matters, that an event was representative, that a witness is honest, or that an AI output is substantively correct. Throughout this chapter, “proof” means “cryptographic attestation under stated assumptions,” not semantic or social truth.

In a world of synthetic media, platform moderation, and “liar’s dividend,” the scarce thing is no longer content but trustworthy provenance and computation history. Proofs are the mechanism layer that answers, cheaply and publicly:

“Did this actually come from where it claims, and did the computation actually run as stated?”

Clarification: Proofs vs. Proof-Backed Instruments

Proofs themselves are infinitely replicable outputs once generated. A ZK proof can be copied and verified anywhere. On its own, a proof is not a scarce bearer asset—it is an attestation.

What is scarce is:

• The ability to produce valid proofs at scale (requires compute, hardware, energy).

• Rights embedded in instruments that reference proofs (Work Credits, staking positions, capacity claims).

Proofs therefore play three distinct roles in the monetary stack:

1. Proofs as a commodity market: Standardized attestations priced by VerifyPrice. You buy proofs the way you buy bandwidth—as a priced input to operations.

2. Proofs as collateral enablers: Proofs make other contracts collateralizable. An inference SLA backed by proofs of correct execution can be used as collateral because the proof makes default detectable.

3. Proof-backed service instruments: Work Credits tied to verified proof workloads are typed service or capacity claims whose integrity is enforced by proofs. They are not presumed money.

“Attestation Money” survives as an analytical lens or legacy label for proof-demand economics. The instruments beneath that lens are proof-backed service claims; any monetary candidacy belongs to the separate base asset.

From a monetary perspective, two features matter:

1. Proofs travel: A PIDL receipt can be moved across systems, archived, or collateralized. It outlives any single platform’s UX, TOS, or reputation.

2. Proofs can be priced and standardized: Once you know the VerifyPrice of a workload, you can treat “valid proof of workload $W$” as a commodity unit.

This gives rise to an Attestation Money analytical lens:

• Media platforms, insurers, and courts demand proofs of origin, editing history, and custody.

• AI services demand proofs that a model of a given hash ran on given inputs with given bounds.

• Enterprises demand proofs that compliance computations actually ran.

Initially, proofs are purchased as opex (“we pay per proof”). Over time, markets will create claims on future proof capacity:

• Reservations or futures on proof-of-provenance capacity for a media network.

• Proof pool shares that entitle holders to a portion of fees from high-value workloads.

• Work Credits sold against committed proof capacity that meets certain VerifyPrice and SLO thresholds.

Under the legacy Proof/Attestation Money analytical lens, these instruments are typed claims on proof capacity, not monetary instruments. Work Credits remain service claims; only the separate base asset may become a monetary candidate if the full conditional chain passes:

“Rights to future, standardized, verifiable attestations about data and computation.”

From the triad perspective:

• Privacy protects who is involved.

• Proofs protect what actually happened.

• Compute powers how we arrive at outputs.

The “Attestation Money” lens describes demand arising where verification, not vibe, mediates trust. Claims on proof capacity remain service instruments; they are not what this thesis asks holders to treat as money.

Compute has always been an economic input: first as muscle, then as steam and electricity, now as FLOPs. The AI boom made this explicit: GPUs, TPUs, and datacenters are priced like oil fields.

Raw compute is not even a standardized service claim:

• Most compute markets are opaque capacity rentals (cloud contracts, colo deals).

• There is no standardized unit of verified work; only hours and instance types.

• There is no cheap, public way to verify that a claimed computation actually ran correctly.

Research Maturity Caveat

Verified inference remains technically immature. Only Tier A cryptographic verification (full ZKML) should support high-assurance capacity issuance without an additional trust haircut. Probabilistic or TEE-backed inference verification (Tiers B and C) receives haircuts or lower-assurance service status. The service-value claim weakens if verified compute trades at no durable premium to ordinary cloud compute; that result would say nothing by itself about monetary premium. See Chapter 24: The Modular Stack for the tier taxonomy.

The “AI Money” analytical lens reframes verified-compute demand by insisting on:

• Canonical workloads: Matrix multiplications, FFTs, and core model primitives.

• Proofs of useful work (PoUW): Miners/provers earn rewards for producing proofs that these workloads ran correctly, with verification asymmetry.

• Verification economics: VerifyPrice turns “one unit of verified MatMul at dimension $n$” into something that can be priced and traded.

In that context, verified compute capacity becomes a standardized service commodity:

“Rights to future, standardized, cheaply verifiable units of useful compute (verified FLOPs).”

Compute Deflation and What Remains Scarce

A skeptical reader will object: “Compute gets cheaper every year. Moore’s Law drives raw FLOP cost down. How can rights to compute retain service value when the underlying commodity deflates?”

This is a serious objection. Here is the response:

What deflates:

• Raw FLOPs per dollar (secular decline).

• Cost of unverified, permissioned compute from hyperscalers.

• Commodity inference for non-sensitive workloads.

• The price of installed capacity after a clearing event. Compute built on financing written against utilization assumptions that did not arrive can change hands at a fraction of its capital cost with the silicon unchanged — financial deflation [Perez 2002] on top of technological deflation [Booth 2020]. See Chapter 13: Why Hold the Base Asset? for the effect on the fee base.

What remains scarce:

• Verified FLOPs with receipts: Compute where correctness is cryptographically proven, not vendor-asserted.

• Policy-constrained capacity: Compute that runs under specific jurisdictional, privacy, or compliance constraints.

• Censorship-resistant access: Compute that cannot be denied by TOS changes, sanctions, or platform bans.

• Priority access under congestion: During demand spikes, priority slots are scarce even if raw capacity is abundant.

• Specific hardware profiles: Compute on L0-C or L0-D grade hardware may remain scarce even as closed alternatives proliferate.

• Receipts for delegation across trust perimeters: FLOPs deflate; the boundaries between operators that a decomposed task must cross do not, and cheaper compute makes finer decomposition cheaper (Chapter 7: The Delegation Economy: Who Buys Verification). Whether those hops cross perimeters at all is an open measurement, not a forecast.

The instrument should reference capacity share, not “one timeless FLOP”:

Under the “AI Money” lens, the relevant service claim is not “rights to 1 FLOP forever.” It is:

“Rights to $X$% of verified compute throughput under SLA $Y$ on hardware profile $Z$.”

This is analogous to how oil futures reference “barrels of WTI crude delivered at Cushing”—not “energy” in the abstract. The specificity (verification, SLA, profile) is what creates persistent scarcity.

Telemetry that detects deflation risk:

If raw compute deflation outpaces the scarcity premium of verification/censorship-resistance, the following metrics will signal it:

• VerifyPrice for verified FLOPs converges toward unverified market rates.

• Capacity utilization on verified networks falls below thresholds.

• Fee revenue from compute workloads declines as a share of total fees.

These are observable. The thesis predicts that a verification service premium may persist because demand for trustworthy AI is structural and the compliance/sovereignty premium may grow as AI becomes more consequential. If telemetry shows otherwise, the compute service case weakens. Neither outcome determines whether the separate base asset earns monetary premium.

Verified-compute service instruments can include:

• Work Credits: typed claims on reserved verified-compute capacity, owed by a named provider and redeemable or transferable for specified future workloads.

• Compute futures: for specific workloads (e.g., “$X$ verified inferences at model $M$ with SLO $Y$”).

• Stake in proof factories: whose entire business is converting energy + silicon into verified FLOPs with transparent VerifyPrice.

Why can these be valuable service claims rather than arbitrary utility tokens? Because:

• Demand is global and secular: As long as AI is an input to value creation, there is demand for FLOPs.

• Verification is public: Anyone can check that a Work Credit corresponds to a valid proof and a stated DVC envelope.

• Terms are explicit: Workload, tier, delivery window, redemption, and expiry determine value rather than an implied monetary promise.

Every era that mechanizes work eventually writes claims on it. Grain receipts became banking; warehouse receipts became money-market funds; and in each case the instrument was born useful and lived or died on one question — did the claim stay tethered to the thing in the warehouse? The tether is everything. A receipt that outruns its warehouse is a promissory note wearing a receipt’s reputation, and the bill arrives the day everyone redeems at once. This chapter builds the tether before it builds the claim.

The triad supplies three capacities. Making them tradable without confusing service with money requires a unit of account for work: something that binds energy, hardware, delivery terms, and verification into a transferable typed claim.

Call these Work Credits (WC).

Informally:

A Work Credit is a typed, prepaid claim on reserved future service, 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, which is evidence and creates no further obligation.

Key distinction: Work Credits are energy-priced, not energy-pegged. They are denominated in work, not in kWh. Energy enters through Facility Energy Receipts (FERs) and VerifyPrice, not through a one-dimensional peg. See Chapter 12: Work Credits: Reserved Service Claims for the full treatment.

Clarification. Throughout this section, “Work Credits” are generic, notional service claims, not product branding and not the base asset. “AI Money” and “proof money” survive only as historical shorthand for service-instrument design spaces; the analytical objects are typed compute, proof, and settlement claims. That separation — claim versus money — is stated once here and defended twice, at Chapter 12: Work Credits: Reserved Service Claims and Chapter 12: Work Credits: Reserved Service Claims; it is not repeated as a caveat at every mention.

Work Credits can be described along a few axes:

Definition: Work Receipts vs. Work Credits

A common source of confusion is conflating “proof that work was done” with “transferable claim on future capacity.” These are different financial objects: one proves the past, the other reserves the future. They split cleanly:

Work Receipt (WR)

A Work Receipt is a PIDL artifact proving that a specific unit of work was completed under attested conditions.

• Content: Claim hash, proof hash, workload ID, SLA tier, timestamps, hardware profile, prover signature.

• Properties: Copyable, verifiable by anyone, not scarce.

• Analogy: A receipt from a completed transaction. It proves the past but confers no future rights.

Work Receipts are not money. They are evidence.

Work Credit (WC)

A Work Credit is a transferable, typed claim on reserved future service, issued against an admissible capacity commitment and extinguished by the Work Receipt that verified delivery produces.

• Issuance: Sold when (a) a named provider or constituted pool has committed admissible capacity for the workload, tier, and window, and (b) that capacity is reserved against every outstanding claim on it in the same atomic step.

• Properties: Scarce (outstanding claims bounded by reserved capacity), transferable, fungible within workload, tier, and window.

• Rights: The service terms written in the claim: workload, quantity, tier, delivery window, substitution terms, and remedies.

Base asset and Work Credit separation:

Hierarchy rule: The base asset is the only object evaluated for monetary premium, and even then only conditionally. Work Credits are useful for service procurement and cost hedging and are explicitly not pitched as stores of value.

The Work Credit Lifecycle

A Work Credit lives through four steps, and one of them is indivisible:

$$\text{commit capacity} \;\rightarrow\; \boxed{\text{sell} + \text{reserve}} \;\rightarrow\; \text{deliver} + \text{verify} \;\rightarrow\; \text{extinguish} + \text{receipt}.$$

There is no interval in which a valid sold claim exists while its capacity is unreserved. Four commitments make the lifecycle a contract rather than a slogan.

• The obligor is named. Each credit binds a provider or an expressly constituted provider pool. “The network” is not an answer unless the network’s collective obligation, funding, and loss allocation are themselves defined.

• The service is named. Workload, quantity, assurance tier, delivery window, location or substitution terms, and remedies are written in the credit. A substitution right states what may replace what.

• Reservation is against everything outstanding. The constraint is not how many credits were sold this epoch but whether every outstanding claim competing for the same future capacity remains feasible. Shared power, hardware, and delivery windows cannot be reserved independently for incompatible workloads, which is why the reservation limit is computed jointly (Chapter 17: Layer 0: Verifiable Machines & Energy).

• Failure resolves by terms. Verified delivery retires the claim. Cancellation, expiry, default, and refund follow stated terms, and a failed delivery becomes neither an open-ended promise nor a claim on the base asset.

Delivered Verified Capacity supports the reservation limit; it does not guarantee performance. In the reference design, payment sits in the fulfilment and escrow arrangement of the claim until delivery rather than quietly financing construction. Where advance proceeds do finance capacity not yet built, that exposure is project finance, named and carried separately (Chapter 3: The World Forces New Monetary Primitives), and not concealed inside the ordinary Work Credit. The receipt that delivery produces is evidence of fulfilment and creates no further service obligation, which is the line between this section’s two objects.

Issuance mechanics for Work Credits:

For a canonical workload $W$ (e.g., “MatMul of size $n$ with error bound $\varepsilon$,” “provenance proof for content type $C$,” “corridor settlement of size $S$ with anonymity set $\geq A$”), define:

• $p(W)$: production cost (energy + hardware amortization + opex) to generate one unit and produce a valid proof.

• $v(W)$: verification cost.

• $r(W) = v(W) / p(W)$: verification asymmetry.

A Work Credit of type $W$, tier $T$ is sold only when:

• A named provider or pool commits admissible capacity for $W$ at $T$ over a stated window, with FER and FCR evidence behind it.

• Telemetry confirms that VerifyPrice($W$,$T$) and other SLOs (latency, failure rate, decentralization) are within bounds for that provider.

• The sale and the reservation happen together, and outstanding claims on the same capacity stay within the issuance envelope (see Chapter 12: Work Credits: Reserved Service Claims).

The credit represents only the service rights stated in its terms. A receipt attests historical work and a credit promises reserved future service; neither becomes the fee/staking medium or inherits the base asset’s conditional monetary candidacy.

Energy Anchoring

Like PoW, Work Credits are ultimately energy-anchored:

• The cost of honoring one more credit is bounded below by the energy and hardware required to produce work that passes the verification threshold.

• Where SHA-256 PoW has no buyer for its work, this work has one: it powers privacy settlements, proofs of provenance, and AI computation.

This anchoring gives Work Credits:

• Credible scarcity: A credit cannot be sold without an admissible capacity commitment, and it cannot be extinguished without real resources spent producing proofs and settling flows.

• Economic meaning: One credit corresponds to a service somebody was willing to pay for (anonymized payrolls, authentic media, verified inference).

And the cost of the same property.

The buyer that gives a Work Credit its economic meaning is also an attack surface the hash puzzle does not have. Nobody buys a SHA-256 output, so there is no buyer of the work to subsidize, mandate, or sanction — though miners themselves can be; demand for verified inference can be all three. The energy anchor is therefore a service-cost and provenance anchor, not a monetary one. Bitcoin’s monetary objectivity and a Work Credit’s link to real activity are different properties (Chapter 34: Objections & Responses).

Layer 0 Maturity and Economic Consequences

Work Credits are only as trustworthy as the hardware that produces them. A world where all proving runs on opaque, vendor-controlled hardware is different from one with diversified, partially open designs.

Chapter 17: Layer 0: Verifiable Machines & Energy (Part III) defines a Layer 0 maturity ladder with grades L0-A through L0-D. This section previews how those grades affect Work Credit economics:

How this affects issuance and pricing:

1. Tiered issuance caps: WC reserved on L0-A profiles may face stricter issuance limits than L0-C/D profiles. This prevents the system from becoming dependent on opaque hardware.

2. Market pricing: WC from different L0 grades can trade at different prices if markets distinguish them. Treasuries and institutions may pay premiums for L0-C/D-backed capacity.

3. Risk disclosure: Every Work Receipt includes the hardware profile (HID) used. Aggregated telemetry shows what fraction of total WC is backed by each grade.

4. Deprecation impact: If an L0-A profile is compromised (TEE backdoor discovered), WC reserved on that profile can be quarantined, discounted, moved to substitute capacity under their terms, refunded, or excluded from certain uses. This is the “bond downgrade” analog.

Why this matters for service-claim quality:

If 90% of Work Credits are reserved on L0-A hardware and a major TEE is compromised, claim quality and DVC take a hit—not because the cryptography failed, but because the service path depended on a common hardware assumption.

By making L0 grade explicit and tying it to economic consequences, the system:

• Creates incentives to invest in open hardware.

• Bounds the impact of hardware compromises.

• Gives users and allocators the information to price risk appropriately.

This is covered in detail in Chapter 17: Layer 0: Verifiable Machines & Energy (Part III). The key point for Part II: hardware trust is not binary; it is graded, measured, and priced — and because it is priced, the service claim’s quality is legible without anyone having to take the word “typed” on faith.

Robots, AI, and the Demand for Work Money

In a robot- and AI-heavy economy the demand story for Work Credits becomes almost embarrassingly straightforward.

Consider a warehouse or factory where most of the physical activity is carried out by robots, and most of the planning and oversight is handled by models. The day-to-day budget splits into:

• Energy to power robots and data centers.

• Compute to run models and generate proofs.

• Privacy and settlement to pay workers, suppliers, tax authorities, and investors without leaking trade secrets or exposing everyone’s graph.

Each of those budgets expresses itself as a recurring need for receipts:

• Proof of correct inference for high-stakes decisions.

• Proof of compliance and risk calculations for regulators and insurers.

• Privately settled wages and vendor payments with lawful audit trails.

Today that flow is mediated through cloud bills, payroll files, bank wires, and audit PDFs. In the stack described here, it can be mediated through Work Credits and receipts. The robots and services are paid in typed claims; in exchange they produce receipts that can be verified cheaply and settled over privacy rails. High turnover can make the claims useful working balances. It does not establish reserve demand for them or for the base asset. On the base asset the reading that tells the two apart is just-in-time fee acquisition on the Native Monetary Buyer Map (Chapter 26: Extended Telemetry), since a unit bought inside a declared window and spent at once adds to turnover and leaves no balance behind.

This is one concrete way to discipline remarks like “money will just be energy.” Energy, compute, and hardware are inputs; Work Credits denominate future access to verifiable, robot-mediated output. They do not become joules, reserve assets, or monetary anchors by denomination.

Why Work Credits Remain Service Claims

A claim can be honest and still not be money. Scarcity, transferability, public verification, censorship resistance, and recurring demand are together enough to make a Work Credit a high-quality commodity or forward service claim; none of them, singly or jointly, is enough to make it savings. The reason is physical rather than rhetorical: the credit stays exposed to workload basis, location, hardware, SLA, expiry, delivery, and common-cause risk, and a promise of future service may carry duration. It is a warehouse receipt with a date on it, and a savings instrument has to survive the day the warehouse is the problem. DVC and the evidence artifacts determine whether the claim is fulfillable; the Native Monetary Buyer Map determines whether the separate base asset has a holder constituency capable of bearing loss. Two different questions, two different instruments, and neither answer transfers.

Monetary Role

Work Credits sit at the junction between base capacity and service contracting:

• For operators, they are revenue in kind: miners/provers/routers earn credits by contributing triad capacity.

• For users, they can be pre-paid capacity: hold credits to secure future access to specified triad services, or trade expected scarcity.

Their service value depends on:

• Demand for specific workloads: Work Credits tied to high-value workloads (e.g., compliance proofs, LLM inference) may command higher premia.

• Governance & telemetry honesty: If VerifyPrice and decentralization metrics are falsified or gamed, the link between credits and real work weakens.

• Regime pressure and deliverability: Differential demand may rise as substitutes weaken, while DVC may fall; the Pressure–Capacity Corridor prevents a monotonic crisis claim.

In portfolio terms, Work Credits are typed service or capacity exposure. LP and staking positions are the equity-like or derivative layer; the base asset is evaluated separately.

Issuance: Tying Credits to Real Capacity

There are many possible issuance schemes; what matters here is not choosing a particular curve, but enforcing two principles:

1. Issuance is legible.

2. Issuance is constrained by real capacity.

One extreme is the Bitcoin model: a fixed schedule, regardless of demand, with the understanding that price will equilibrate. The other extreme is a pure capacity-linked model, and it is the one the reference design takes: a Work Credit is a capacity reservation, sold when committed capacity is reserved and retired when the service is delivered, inside an issuance envelope set by stress-adjusted DVC.

In such a system, adding a new proving cluster, plant, or corridor is not just a marketing slide; it is an event that expands the envelope of Work Credits the system can credibly support. The converse is also true: if plant retires or corridors die and are not replaced, the reservations against them must move to substitute capacity under their terms or default, and any sales that continued on autopilot would show up as VerifyPrice drift, SLA breaches, and deteriorating energy metrics. The governance layer’s job is not to guarantee any particular price, but to keep issuance and capacity in rough proportion and to make any departures visible.

From an allocator’s perspective this yields a familiar pattern: Work Credits look like prepaid claims on the output of a portfolio of infrastructure (proving farms, AI chains, privacy corridors, and plants) rather than a purely arbitrary balance sheet. The difference from conventional “infra tokens” is the insistence on receipts and KPIs: if claimed capacity and observable behavior diverge, the discrepancy is not a rumor; it is a datapoint.

The Supply Balance Equation

Here is the question that kills most “energy-backed” tokens in the cradle: why does demand not simply expand supply, neutralizing scarcity? The mechanism sounds self-defeating. If Work Credits are sold whenever a customer wants service, then every new customer who arrives creates new supply to serve them. The token is busy, the network grows, and the scarcity — the very thing that was supposed to make holding worthwhile — evaporates into its own success. Demand, on this reading, is not a source of scarcity but an exhaust valve for it.

That is not a bug in the design. It is the design, correctly read. Work Credits are sold against reserved capacity and retired on delivery, so supply growing with demand is not leakage; it is the claim staying honest. A service claim whose supply could not grow to meet service demand would be a shortage instrument, not a savings instrument — and neither of those is a reserve asset. The interesting quantity is therefore not gross issuance but what remains after the service is delivered, and that is a balance, not a schedule.

The answer lies in the net supply dynamics. It can be written as a balance equation:

$$\Delta\text{Outstanding WC} = \text{Issuance} - \text{Redemption/Retirement} \pm \text{Governance}$$

Lost or forgotten wallets do not leave the outstanding count — the units still exist on-chain — so they are not a term in this identity; the effective (circulating) supply additionally nets them out.

For Work Credit supply to remain aligned with deliverable service, the design must ensure:

$$\text{Outstanding claims} \leq \text{haircut stress-adjusted DVC over the delivery horizon}.$$

Read that as a solvency test, not a scarcity test. It is the warehouse being asked to show that every receipt outstanding corresponds to something physically present and deliverable. It places no ceiling on how many receipts a busy system writes; it places a ceiling on how many can be outstanding at once, and the ceiling moves only when the physical world moves. That distinction carries the whole chapter:

• During growth: Work Credit issuance may grow with independently verified DVC and contracted demand.

• At maturity: Claims retire through delivery, expiry, or cancellation under published terms. Scarcity can affect service price without making the claim a reserve asset.

What prevents runaway issuance?

The same four doors, in the order an operator would try them:

1. DVC envelope: Total WC outstanding for each workload, tier, and horizon is capped by haircut stress-adjusted DVC.

2. Capacity evidence: The envelope expands only when FERs, FCRs, hardware profiles, and scenario flow support additional deliverable service.

3. Contract retirement: Delivery, expiry, cancellation, and default rules remove or impair claims explicitly.

4. Governance friction: Changes to service-claim rules require supermajority and are visible in dashboards before activation.

Telemetry that detects supply risk:

• Inflation rate: Issuance / circulating supply. Should decline over time.

• Retirement rate: retirements / issued. Should track delivered service and expiry terms.

• Net supply change: $\Delta$Supply per epoch. Positive during growth, flat or negative at maturity.

• Issuance vs. capacity: If issuance grows faster than verified capacity, this signals potential dilution.

If these metrics drift outside healthy ranges, it becomes visible in dashboards—holders and operators can respond before the SoV thesis is undermined. A system that sells against a warehouse cannot hide a shrinking warehouse; the drift shows up in the issuance numbers before anyone has to allege anything.

Energy-Priced, Not Energy-Pegged

In popular discourse one often hears that “money will just be energy,” especially in the context of robotics and AI. As shorthand, this is attractive: robots and data centers run on electricity, so why not quote everything in kWh and be done with it? The problem is that not all kilowatt-hours are created equal. Time of day, grid node, reliability, carbon intensity, and siting constraints all affect their economic and political meaning. A winter-peaking kWh on a stressed urban grid is not the same as a curtailed hydro kWh in a remote valley. Pretending otherwise smuggles a lot of hidden politics and risk into the unit of account.

The discipline in this thesis is to admit that complexity and route around it with receipts.

Energy is measured and wrapped into Facility Energy Receipts (FERs), which record, for each facility and time window:

• kWh in,

• kWh delivered to IT,

• heat reused,

• PUE/ERE/WUE,

• water use,

• carbon intensity,

• and outages/curtailments.

On top of that, the thesis measures verified work per kWh:

• $\eta_{\text{vFLOP}}$ for FLOPs,

• proofs-per-kWh for proof workloads,

• swaps-per-kWh for settlement.

VerifyPrice then tells us how much it costs, in time and money, for an independent verifier to check that a given amount of work was done.

The result is an implicit conversion path:

energy $\to$ FERs $\to$ verified work (proofs/FLOPs/swaps) $\to$ receipts $\to$ Work Credits

The design never pretends that one Work Credit is one kilowatt-hour; instead it makes it easy for anyone to estimate, at any given time, how many kilowatt-hours of which quality and where in the world sit behind a portfolio of Work Credits, via the receipts.

Pricing in energy then becomes an inference problem for markets:

• Work Credits are implicitly energy-priced because their production and redemption depend on energy-intensive workloads whose cost curves are public.

• FERs and VerifyPrice make those curves legible without forcing a brittle kWh peg.

What distinguishes Work Credits from naive “energy tokens” is precisely this separation:

• The unit of account is denominated in work, not in kWh.

• Energy enters through FERs, $\eta_{\text{vFLOP}}$, and VerifyPrice, not through a one-dimensional peg.

Markets, regulators, and builders can look at those receipts and say, with some confidence, “a Work Credit currently corresponds to about this much capacity, with this energy and carbon profile, under these SLAs.” That is enough to make the asset priceable and analyzable without forcing it into a crude energy standard.

Why Work Credits Are Typed Service Claims, Not Presumed Money

It is equally easy to make the opposite error: to observe that Work Credits are scarce, transferable, and tied to necessary workloads, then promote them from service claims into money by vocabulary. This thesis does not make that move. A Work Credit is a typed claim on capacity or service whose quality depends on workload, location, hardware, SLA, delivery window, and the stressed path that can actually fulfill it. That case was made at Chapter 12: Work Credits: Reserved Service Claims; this section asks the harder question it left open. What would have to be true (not said, not branded, but observable) for a Work Credit to cross from service claim into money?

Four things, each visible in telemetry before it is visible in price:

1. Issuance is constrained by stress-deliverable capacity, not nameplate capacity.

   FERs, FCRs, and Delivered Verified Capacity bound claims by the service that survives scenario-specific binding constraints. Gross installed hardware, energy procurement, or benign-state output is insufficient.

2. Demand can be budgeted without being monetary.

   Proofs, inference, settlement, and related workloads may sit on recurring OPEX lines. That supports a service market. It does not establish reserve demand, long holding periods, self-custody, loss-bearing capacity, or countercyclical accumulation.

3. Verification makes the claim legible, not monetary.

   A PIDL receipt can make fulfillment cheap to check and FCR/FER artifacts can make provenance auditable. Evidence reduces information asymmetry; it does not erase delivery, basis, counterparty, or temporal risk.

4. The claim must not absorb project duration by implication.

   A prepaid capacity claim, a claim on future service, and a project note are different instruments. If a Work Credit promises par, redemption, a coupon, or emergency support against construction failure, it has become duration-bearing credit and must be labeled and underwritten as such.

So what would the crossing actually look like? Not a marketing decision and not a milestone on a roadmap, but a change in holding behavior that the dashboards can see: holding periods lengthening rather than claims being redeemed at term, and balances retained through drawdowns instead of recycled into service. The tell that would settle it is buyers acquiring the asset while the service it claims is cheap and available, which is the signature of savings rather than procurement. None of that is a design property. It is holder behavior, and it is exactly what the Native Monetary Buyer Map watches for on the base asset (Chapter 26: Extended Telemetry). Until those series move, Work Credits belong beside capacity vouchers and service contracts, not beside the base monetary candidate. They may trade at a premium for scarce delivery rights and may serve as collateral where their terms permit. Those are properties of typed service claims. Monetary treatment remains a separate empirical question answered, if at all, by the holder-side mechanism and buyer map (Chapter 13: Why Hold the Base Asset?).

A holder who wants verified service in a bad state can hold one of three things: a Work Credit, which is a typed claim on reserved service owed by a named provider (Chapter 12: Work Credits: Reserved Service Claims); Bitcoin, to buy what is needed when the need arrives; or the base asset. The first two are well understood. The case for the third has to be made against them, and it is made here in the order a skeptical reader would demand: the strongest alternative first, then the channels through which service value reaches the asset, then the reasons that value might be monetary, then the instruments that would show it is not.

Why Hold Rather Than Convert on the Day?

Where payment requires the base asset, a Bitcoin balance remains dependent on acquisition until that acquisition has settled. A balance held in advance removes that dependency. That is the whole of the advantage, and it exists only in a band: where conversion is unavailable, too slow, or incompatible with the transaction’s required privacy and control conditions, while native settlement and the complete service path remain usable. Outside the band, the holder of Bitcoin buys what is needed when it is needed and carries none of the base asset’s risk in the meantime.

Two different advantages are easy to run together. The stack’s advantage is that it can deliver what the best institutional substitute cannot. Preholding’s advantage is that a holder can obtain that delivery when the best Bitcoin-funded strategy cannot. The first does not establish the second. Chapter 30: Risk Analysis & Failure Modes explains why a Work Credit hedges the wrong state and why Bitcoin does not itself produce a proof; neither argument defeats Bitcoin-funded procurement.

The two paths are

$$\begin{gather*} \text{held native balance} \;\rightarrow\; \text{native payment} \;\rightarrow\; \text{service},\\ \text{Bitcoin balance} \;\rightarrow\; \text{acquisition or other procurement} \;\rightarrow\; \text{service}, \end{gather*}$$

and the mechanism exists only where the extra dependency in the second path makes a material difference, not because the second path has one more arrow. For outright timing failure the condition is

$$T_{\text{native}}(s,W) \;\leq\; \tau \;<\; T^{\ast}_{\text{BTC}}(s,W),$$

where $s$ is the stress state; $W$ carries the workload, assurance tier, privacy requirements, and delivery terms; $\tau$ is its deadline; $T^{\ast}_{\text{BTC}}$ is the completion time of the best feasible Bitcoin-funded strategy; and both strategies start from the same purchasing-power budget. The broader case includes differences in cost and in the probability of failing, not only outright inability to transact, but every such difference must survive the cost and risk of holding the base asset beforehand.

• Why hold rather than convert on the day?

  • In the band: where conversion is unavailable, too slow, or incompatible with the transaction's required privacy and control conditions, while native settlement and the complete service path remain usable

    A balance that may remain spendable when acquiring that balance would no longer be feasible

  • Outside the band

    The holder of Bitcoin buys what is needed when it is needed

The access experiment: equal-budget strategies are fixed before the disruption

1. a held native balance
2. Bitcoin with acquisition on the day
3. Bitcoin with provider-side conversion
4. an existing reserve asset plus diversified service reservations
5. direct procurement where it exists

Where the band might be.

The states in Chapter 13: Why Hold the Base Asset? are hypotheses registered in advance, not examples of the mechanism working.

The last row gives the delegation buyer of Chapter 7: The Delegation Economy: Who Buys Verification a concrete role, with a limit: it is a reason for prefunded transaction balances, not for monetary reserves.

What the balance buys there, and what it does not.

It buys payment capability that is immediately usable inside the service economy that survives. It does not buy a reserved quantity of compute, a fixed service price, a queue position, a provider’s continued existence, or protection against the asset losing purchasing power. Providers promise no capacity, price, or priority because a customer holds the asset. Those rights are sold through specified service contracts (Chapter 12: Work Credits: Reserved Service Claims), and the contract, not possession of the payment asset, defines the obligation. That is why the base asset carries no claim on historical or future work, and why it is compatible with a provider accepting payment at the moment of procurement. Acceptance by providers is part of the service path, not a separate guarantee: even universal acceptance leaves open why the holder should not acquire the accepted asset immediately before paying. The condition is not acceptance by every surviving provider but enough independently supplied, reachable capacity accepting native payment to fulfil the workload on its terms; a provider that stays powered and refuses the asset contributes nothing to it.

The counterfactual is allowed to win.

The comparison is against the best Bitcoin-funded strategy actually feasible in the state, not a weak one such as opening an exchange account during the crisis. That strategy may use prepared wallets, existing non-custodial routes such as the corridor of Chapter 23: Layer 5: Value & Settlement, direct payment to providers, funded payment channels, independent conversion providers, and diversified service reservations. Above all, it may let the provider do the conversion: a protocol that requires native fees does not thereby require the customer to hold the fee asset. Two results would damage the mechanism, and both must be visible if they occur. First, a provider or router may accept Bitcoin and pay the fee from its own native inventory. The system then needs native inventory somewhere, but not a durable reserve held by the end user. That is the bypass that Conditions 1 and 5 of the Value Capture Lemma name, seen from the holder’s side, so this test is also the non-bypassability test. Second, providers that depend on selling native receipts to pay for power, hosting, and hardware may stop operating when the same acquisition market fails, so a disruption that first favours holders can then disable the service they hold for. The test therefore runs over the delivery horizon, not to the first successful payment, and the Pressure–Capacity Corridor (Chapter 8: The Triad and the Monetary Candidate) still governs: no balance insures access through a payment path whose suppliers stop during the same event.

The access experiment.

The holder service is tested before it is claimed. Equal-budget strategies are fixed before the disruption: a held native balance; Bitcoin with acquisition on the day; Bitcoin with provider-side conversion; an existing reserve asset plus diversified service reservations; and direct procurement where it exists. Each faces the same service request under the same adversarial scenario. The published readings are completed work, completion time, privacy and control failures, total procurement cost, and the losses borne during the holding interval, with balances held in anticipation of stress reported apart from balances acquired once the stress was obvious. A pass requires more than a native transaction succeeding. It requires a material advantage over the strongest alternative that was actually feasible. The failure condition is stated now: if Bitcoin-funded procurement reproduces the same service, within the same constraints, without a material disadvantage, the preholding mechanism is absent for that workload and state. The experiment is a Phase I deliverable of Chapter 32: Kardashev Labs: Build and Measure (Chapter 32: Kardashev Labs: Build and Measure), run first as an analog on an existing network whose fees must be paid in its own asset. It is not a counted red line. It is the evidence Red Line 16 stands on: the experiment asks whether holding changes what can be done, and the lending and basis series of Red Line 16 ask whether a mature market prices the holder service (Chapter 30: Risk Analysis & Failure Modes). Neither substitutes for the other.

A pass is not yet a reserve.

Even a positive result leaves the second question open: does the benefit support persistent, loss-bearing reserve demand, or only an operating buffer? Agent wallets, gas inventories, and precautionary balances do not become a monetary anchor by being added up; that is Premise 7, and it stands (Chapter 1: Introduction). Whether independent principals keep balances beyond their transaction windows, and bear the risk of them through stress, is what the Native Monetary Buyer Map (Chapter 26: Extended Telemetry) and Red Line 16 read.

The base asset is not a reservation on the machines. It is a balance that may remain spendable when acquiring that balance would no longer be feasible. Whether that difference survives the best Bitcoin-funded alternative, and supports anything beyond operating inventory, is the monetary experiment.

The access experiment’s arms are built at equal assurance, so that what separates them is the price of control and exit rather than of verification (Chapter 34: Objections & Responses).

Economic Linkage: How Triad Demand Becomes Asset Value

One question separates a systems manifesto from a monetary thesis: why does demand for Privacy, Proofs, and Compute raise the value of holding the asset, rather than merely rewarding consuming a service?

The familiar answer is a chain that runs from fee demand through burns to scarcity to price. That chain fails (Chapter 13: Why Hold the Base Asset?) and is not used here in any form. The answer below is in four parts, of which the first is a cash-flow claim the thesis does not describe as monetary, and the remaining three are the monetary content.

1. What exactly is the asset?

The base asset is the protocol-internal unit in which fees may be required, collateral posted, and settlement denominated. It is a conditional monetary candidate and nothing in this section upgrades it. Work Credits are typed capacity or service claims; FCR, FER and PIDL artifacts are evidence; project notes are duration-bearing credit; LP and staking positions are derivatives or operating claims (Chapter 8: The Triad and the Monetary Candidate). Only the base asset is evaluated as money.

The strong phrasing, that all uses of the triad must flow through the asset, overstates the design. Core protocol operations are denominated in the asset by rule. Equivalent computational content is obtainable elsewhere, always, at a price; bypass is a magnitude rather than a switch (Chapter 13: Why Hold the Base Asset?), and the design constrains what that magnitude is worth rather than abolishing the alternative.

2. Why is it scarce in a monetary sense?

Scarce capacity does not imply a scarce asset. The design forges the link through scheduled issuance, fee retirement, collateral lockup, and Work Credits sold against committed, verifiable capacity rather than by decree.

The link needs two precisions. First, base-asset issuance follows the constitutional schedule and is independent of Work Credit dynamics; it is Work Credits that are bounded by delivered verified capacity. Second, whether burns exceed issuance at steady state (whether net supply actually falls as workloads grow) is an empirical outcome the fee-coverage and issuance boards report, not a property the design confers. Issuance discipline is real. Net deflation is a reading.

3. Why does demand for triad capacity raise the value of holding?

Four channels, stated in ascending order of monetary content, with the first two explicitly conceded not to be monetary at all.

1. A fee stream (not monetary). Every proof, private settlement and verified inference pays a fee in the native unit, and routing rules direct it to retirement, staking, and operator share. What the holder owns through this channel is a competitively priced claim on a cash-flow stream bounded above by differential value $\Delta$ and deflating with unit price (Chapter 13: Why Hold the Base Asset?). A discounted-cash-flow valuation reproduces it exactly. A burn is a buyback and confers no moneyness.

2. A collateral lockup (not monetary). Required lockup in the native unit immobilizes float while operators remain solvent and choose to keep operating. Chapter 13: Why Hold the Base Asset? bounds how large a fact this can be (large-cap-equity magnitudes, not monetary aggregates) and shows it is a slope effect on price impact rather than a level effect on price, because a lockup places no bid.

3. Pledgeability without due diligence (monetary). This is the first channel through which growing triad demand raises the value of holding rather than of receiving. As verified throughput grows and receipts accumulate, the cost to any counterparty of establishing what a pledged position actually is falls toward zero, and a position nobody must investigate can be accepted no questions asked (Chapter 13: Why Hold the Base Asset?). The holder is not being paid; the holder is holding something that has become easier for everyone else to accept. Nothing is distributed through this channel, so a valuation of distributions alone omits it. Whether a holding service of this kind is monetary is what Chapter 13: Why Hold the Base Asset? and Red Line 17 test.

4. A unit with something to denominate (monetary). A growing endogenous service economy gives counterparties a reason to reckon in the unit rather than merely settle in it, and denomination is the stickiest monetary function because it is a coordination device rather than a portfolio choice (Chapter 13: Why Hold the Base Asset?). This channel is available to a service protocol and is not available to a bearer asset with no native goods.

A fifth channel, the state-contingent holder-side service flow, is argued separately at Chapter 13: Why Hold the Base Asset?, because it is a property of the regime rather than of demand growth.

Channels 1 and 2 pay the holder. Channels 3 and 4 change what holding is. Only the second kind is monetary, and only the second kind survives a correctly specified discounted-cash-flow valuation.

A holder of channels 1 and 2 alone is buying “a share of the fee stream from indispensable workloads,” a position “closer to equity in a utility than to a collectible.” That description is accurate for those channels, and it is the reason they cannot carry the monetary reading: a utility equity earns its cost of capital and carries no monetary premium. Channels 3 and 4 are the reply, and they are a reply about the asset’s acceptability and denomination rather than about its cash flows. Is either sized? Not in this document.

4. What prevents capacity providers from capturing all value?

The classic “utility token trap”: if operators earn the fees and governance can inflate supply, holders are exit liquidity. The design’s answers are routing rules, and they are stated as such: fees split between retirement, stakers and operators so no party takes the whole; base-asset issuance constitutionally scheduled; Work Credit sales bounded by reserved capacity, with overselling rejected and visible; core operations denominated natively.

These govern where the fee goes, and none of them governs how large the fee can be, which is the question Chapter 13: Why Hold the Base Asset? takes up and answers with a bound rather than a promise. Read this paragraph as a description of plumbing. The monetary argument is in channels 3 and 4 above and in Chapter 13: Why Hold the Base Asset?, and it does not depend on any number in this paragraph.

Summary: the Value Capture Lemma in plain language

Demand for triad capacity becomes value accrual to the native asset only if five conditions hold at once: all core usage requires the asset, usage retires supply, capacity provision requires staking, issuance is constrained, and capacity cannot be cheaply bypassed. These conditions are necessary and not sufficient, and what they establish is accrual — a cash-flow claim and a collateral lockup — not moneyness. If any one fails, the system may be indispensable infrastructure whose economics accrue to operators or customers.

A related but separate claim. The five conditions are properties of the monetary design and say nothing about the durability of the demand being routed. That workload demand is structural rather than speculative is a distinct empirical claim whose failure the thesis treats as its own falsifier: a workload mix that becomes and remains predominantly speculative retires the store-of-value claim through Red Line 5, not through this lemma.

Value Capture Lemma

In the reference design, demand for Privacy, Proofs, and Compute accrues economically to the native asset — as a claim on the fee stream and a collateral lockup — through five channels, and the design relies on all five holding together:

1. Required fee medium: the asset is required for core fees, and users cannot pay in fiat, stablecoins, or other tokens at equivalent service quality.

2. Supply reduction: a meaningful share of fees is burned or permanently retired.

3. Collateral lockup: operators must stake the asset as collateral to provide services.

4. Issuance discipline: gross issuance follows a schedule fixed ex ante, not governance fiat.

5. Non-bypassability: users cannot obtain equivalent triad capacity through bypass channels (cloud contracts, stablecoin-denominated services, direct fiat payment to operators) that avoid touching the asset.

Each channel closes a named leak, and in this design nothing else stands in for a channel that fails. The five are this design’s route to accrual, not the only route economics allows: a protocol can take fees in another unit and use them to buy and retire the asset, distribute revenue instead of burning it, or take native fees without native collateral, and each of those captures value by a different route with different risks. The lemma is the bridge between “these capacities are indispensable” and “therefore this asset accrues the value of that indispensability.” Accrual is a precondition the monetary claim builds on, not the monetary claim itself (Chapter 13: Why Hold the Base Asset?).

Which conditions the monetary channels actually use.

Of the five conditions, four govern accrual, which is a discounted-cash-flow quantity. Issuance discipline is the exception: a discretionary supply is information-sensitive on supply, for the reason Chapter 13: Why Hold the Base Asset? gives. Condition 4 is therefore doing monetary work that Conditions 1, 2, 3 and 5 are not. That is the same conclusion Chapter 13: Why Hold the Base Asset? reaches from the other direction, and the two agree for a stated reason rather than by coincidence.

What the five conditions do not address.

Every one of them governs where fees go. None governs how large they can be, and a routing rule applied to a fee of nothing captures nothing. Chapter 13: Why Hold the Base Asset? takes up the level question, finds that the standard objection to taxing a contestable market is wrong for a reason worth stating, and then finds that the correct answer supports a narrower conclusion than the claim that fees, burns, and collateral earn the asset a monetary premium (Chapter 13: Why Hold the Base Asset?). The conditions themselves are unchanged.

The lemma has a frequently-missed converse. It states when native demand accrues economically to the asset. It does not state that movements in the asset’s observed market price are caused by that demand. Those are different machines, and conflating them is the most common way a monetary thesis fools its own author.

Corollary: Market-Price Non-Equivalence

External financial wrappers can create price demand without exercising privacy settlement, purchasing proofs, consuming verified compute, paying native fees, locking collateral, or producing burns. Conversely, wrapper redemptions, leverage unwinds, dealer hedging, or broad risk-off flows can depress the asset’s price while native monetary usage improves. Therefore

$$\text{price appreciation} \;\nRightarrow\; \text{monetary adoption}$$

and

$$\text{monetary adoption} \;\nRightarrow\; \text{immediate price appreciation}.$$

Price is an output to explain, not a protocol KPI to worship. The monetary thesis must be evaluated through native fees, burns, collateral, settlement, receipt volume, verification health, reachability, and non-custodial use. Market-price interpretation requires a separate financial-flow telemetry layer (VerifyFlow, Chapter 26: Extended Telemetry).

Value Capture vs. Price Capture

It is worth separating the two phenomena explicitly, because the thesis is routinely “confirmed” by the wrong one.

Value capture is the existing loop: triad usage $\rightarrow$ native fees $\rightarrow$ burns, collateral lockup, and operator demand $\rightarrow$ scarcity and cash-flow accrual to the asset. It is governed by Chapter 13: Why Hold the Base Asset?. What it produces is a claim on a fee stream plus a collateral lockup; whether the asset also carries monetary premium is a separate question, answered separately in Chapter 13: Why Hold the Base Asset?.

Price capture is demand for exposure to the asset’s price, arriving through spot ETFs, exchange custody, treasury companies, margin products, options, futures, swaps, leveraged and inverse ETPs, passive indices, and systematic trading rules. Price capture can occur with no protocol use whatsoever.

Native value capture and observed price appreciation are neither equivalent nor mutually necessary. No cell is monetary evidence: that is a separate axis, read on Red Lines 16–18.

The diagonal is what makes the thesis falsifiable. A thesis that treats every price rise as confirmation and every price fall as noise cannot be wrong, and therefore cannot be right either.

Fee Incidence and the Level of the Fee

Every condition of the Value Capture Lemma answers one question: where does the fee go? Required medium, supply reduction, collateral lockup, issuance discipline, and non-bypassability are all routing rules. None of them answers the question a valuation actually needs answered, which is how large the fee can be. A protocol that routes the whole of a fee of nothing into a burn address has satisfied five conditions and captured zero.

The gap has a sharp form, best stated as the objection it invites:

“You have deliberately engineered the most contestable market you could. Workloads are canonical and interchangeable, verification is cheap enough that no trust is required, admission is open, and there are no vendor chokepoints. A contestable market competes economic profit to zero. Zero profit means no surplus, and no surplus means nothing to burn.”

The objection is wrong. It is worth showing exactly why, because the correct answer rescues considerably less than it first appears to, and what survives is not the claim that fees, burns, and collateral earn the asset a monetary premium.

Incidence: A Fee Is a Wedge on Turnover, Not a Claim on Profit

The objection conflates two different bases. A protocol fee is levied on transactions, not on residual profit. It is a tax wedge, and tax wedges do not require anybody to be earning rents.

Take the market the thesis is trying to build: many providers, free entry, roughly constant returns to scale in the relevant range, a canonical workload so that units are fungible. Long-run supply is then approximately horizontal at marginal cost $c$ (equivalently the protocol’s all-in unit cost $c_p$ of Chapter 13: Why Hold the Base Asset?; write $c \equiv c_p$). Impose a per-unit protocol fee $f$ on that market and the supply curve the buyer faces shifts to $c+f$. The new equilibrium has buyers paying $c+f$, providers receiving $c$, and providers earning exactly the zero economic profit they earned before. The protocol collects $f \cdot Q$. Nothing about that revenue came out of operator margin, because there was no operator margin to take it from; in the long-run competitive case the entire statutory burden lands on the buyer.

Operator margin compression is irrelevant to fee revenue. The fee is a wedge on turnover. Turnover is what a contestable market maximizes.

This is standard incidence analysis, and it means the objection proves too much: if contestability destroyed fee bases, no commoditized market could ever be taxed, and every one of them is.

Incidence explains who bears a fee. It does not explain why a positive fee is sustainable, and the two should not be run together. Exchanges, clearing houses, and toll roads are lucrative on top of viciously competitive flows for a further reason: the flow is competitive but the fee layer is not. There is one place to clear the contract, one road across the water, one book where the trade is legally final, so the competition among users of the layer never becomes competition to be the layer. That inescapability is a property those venues possess and a protocol must earn; it is the subject of Chapter 13: Why Hold the Base Asset? and Chapter 13: Why Hold the Base Asset?, and the fork channel is precisely the case where it is not earned.

The short run is different, and the difference matters.

With installed capacity fixed, supply is not horizontal. Deployed hardware has already sunk its capital, so in the short run the supply curve slopes upward and part of the fee is absorbed as a reduction in quasi-rent to existing machines rather than passed to buyers. That is not a problem for this quarter’s fee revenue; it is a problem for the next round of capacity. Quasi-rent is what funds replacement, and an operator whose realized return on deployed hardware is being clipped by a fee re-prices the entry decision accordingly. The long-run pass-through result therefore describes the destination, not the transition, and the transition is where entry and capacity growth are decided. A fee schedule set as though incidence were instantaneously long-run will suppress the capacity it is trying to tax.

The Base, and Why It Deflates

Fee revenue is not $f$. It is

$$\mathrm{Rev} = f \cdot Q(c_p + f),$$

and both terms are endogenous. Two consequences follow, and the second is the more serious one.

Quantity responds to the wedge.

The tollbooth analogy holds only where there is no parallel free road. Raising $f$ raises the delivered price, and at the margin some volume declines, defers, batches, or leaves. What the protocol can extract is bounded not by what buyers would pay for the service but by what they would pay through this channel rather than the next-best one, which is the subject of Chapter 13: Why Hold the Base Asset?.

An ad valorem fee on a deflating unit price is a shrinking real toll.

For this paragraph the protocol’s fee is modeled as ad valorem: a share of unit price rather than the per-unit wedge $f$ used in the incidence analysis above. Under a per-unit fee only the volume term below moves, and the deflation mechanism this paragraph isolates does not arise. Chapter 11: Compute Through the “AI Money” Lens argues that verified compute stays scarce even as raw compute deflates. Grant that argument entirely; it does not touch this one. Even if the verification premium is fully durable, a fee expressed as a percentage of a unit price that falls secularly collects fewer real resources per unit of service delivered every year. Real fee revenue then grows only if

$$\underbrace{\text{growth in verified units delivered}}_{\text{volume}} \;>\; \underbrace{\text{rate of decline in real unit price}}_{\text{deflation}}.$$

That inequality is an empirical bet, not a theorem, and the thesis is making it. It may well be a good bet (the historical pattern in compute is that unit-cost decline is met by more than proportional volume expansion), and a bet must say what would settle it against the thesis. Condition B of Red Line 14 (Chapter 30: Risk Analysis & Failure Modes) does: deflation-adjusted gross native fee turnover that fails to grow while physical throughput grows is this bet losing, in public.

The bet has a macro frame.

The volume-over-deflation bet is usually argued from technology curves: unit costs fall, demand expands more than proportionally, revenue grows. That is the technological channel, and it is the one Chapter 11: Compute Through the “AI Money” Lens treats. There is a second channel with the same signature but a different driver: a financial clearing event that transfers installed capacity from weakly financed owners to strongly financed users at lower capital cost, collapsing the effective price of capacity without any change in the technology [Perez 2002]. The two channels are observationally distinct. The technological channel shows up as gradual unit-cost decline with stable utilization, the financial one as a step-change in the price of installed capacity with utilization resetting. They have the same effect on the inequality above: both push the deflation term up. What the frame adds is timing. The technological channel is smooth; the financial channel is not, and a fee base built on the expectation of smooth deflation being outrun by volume will experience the financial channel as a shock to exactly the term it is betting on. The instrument is unchanged, since Condition B reads on the same series either way. But a reader tracking it should know that the two channels are live simultaneously, and that the financial one can move a quarter’s reading by more than a year of Moore’s law.

The Bound on the Sustainable Fee

Incidence tells us the fee has a base. It does not tell us how high the fee can be set. That ceiling is not a function of operator margin either; it is a function of what the protocol channel is differentially worth.

Differential Value $\Delta$ and the Sustainable Fee Bound

Let $c_p$ be the protocol’s all-in cost of delivering canonical workload $W$ at tier $T$, and $c_b$ the all-in cost of the best bypass channel delivering the same computational content without protocol-grade verification. Let $\Delta$ be the marginal buyer’s willingness to pay for the protocol’s differential properties: cryptographic checkability, neutrality, credible non-discretion, and non-custodial exit.

The buyer routes through the protocol only if $c_p + f - \Delta \le c_b$, so the sustainable fee satisfies

$$\boxed{\; f \;\le\; \Delta - (c_p - c_b) \;}$$

Here $\Delta$ is a scalar wedge in price units, not the difference operator used elsewhere in this Part.

The first term is the one a protocol designer wants to think about. The second is the one that decides the outcome, and it is structurally positive: verified compute costs more to produce than unverified compute, because proving overhead and redundancy are real resources spent on top of the underlying work. So the protocol begins every negotiation with a cost handicap and must recover it out of $\Delta$ before it collects a single unit of fee.

The document’s own tier multipliers are cost pass-through, not evidence of willingness to pay.

Chapter 22: Layer 4: Truth & Work prices assurance on its own axis: Replicated at $1.0\times$, Replicated-plus-audit at $1.4\times$, Probabilistic (M2) at $1.6\times$, Succinct (M1) at $2.5\times$, with a latency multiplier of $1.0$/$1.3$/$1.6$ multiplied in. Read those against what each tier costs to supply. Replicated-plus-audit is three independent re-executions and a randomized audit, so its multiplier is set against roughly three times the production cost; the M1 multiplier is set against a proving overhead that Appendix E: Hardware Profiles publishes as a quarterly series and does not yet know. The multipliers are rationale-set to cover redundancy or proving overhead plus a margin, and the document nowhere establishes that they do. That is a question about $c_p$ and the margin above it, not about demand, and nothing in the document establishes that any buyer’s $\Delta$ for succinct assurance is $2.5\times$ its $\Delta$ for a committee’s word. If it is not, headroom narrows as assurance rises, and at the top of the axis $\Delta - (c_p - c_b)$ can be negative: a tier that is technically superior, honestly priced, and unsellable. That is a testable prediction against the thesis, and a red line measures it (Chapter 30: Risk Analysis & Failure Modes).

Bypass Is a Magnitude, Not a Binary

Condition 5 of the Value Capture Lemma is written as an existence condition (users cannot obtain equivalent capacity through a bypass channel), and Red Line 6 is written as a direction condition: usage grows while native fees do not. Neither is wrong, and neither is changed here. But both are read, in practice, as though bypass were a switch.

It is not. Bypass is never impossible. It is priced. There is always a channel that delivers the same computational content without protocol-grade verification, and the only question is what the buyer gives up by using it, which is exactly $\Delta$. Condition 5 should therefore be read and measured as a magnitude claim: not “no bypass exists,” which is false everywhere, but “$\Delta$ is large enough, for enough of the volume, to support a fee worth burning.” The condition stands as stated. Its interpretation is what this section tightens, and its measurement is what Red Line 14 supplies.

This is why the chain-strength rating for non-bypassability is Medium rather than Strong (Chapter 8: The Triad and the Monetary Candidate). The condition is well specified as a binary and the binary is well enforced. The economics requires a magnitude, and the magnitude is nowhere estimated. A rating of Strong would rate the enforcement machinery, not the quantity the argument depends on.

What Determines $\Delta$, and Why It Is Probably Thin

To first order, the differential value of a proof is the loss it prevents, times the probability that loss survives the alternative:

$$\Delta \;\approx\; \varrho\,\mathcal{L},$$

where $\mathcal{L}$ is the loss from undetected misexecution or denial of service and $\varrho$ is the residual probability of that loss under the best bypass channel. This operationalization lower-bounds $\Delta$. It prices only loss-prevention, while the full definition in Chapter 13: Why Hold the Base Asset? covers four properties: cryptographic checkability, neutrality, credible non-discretion, and non-custodial exit. Neutrality and non-discretion therefore enter as additional terms the $\varrho\,\mathcal{L}$ form omits. ($\varrho$ and $\mathcal{L}$ are used rather than the conventional $\pi$ and $L$, which denote the inflation rate in Chapter 3: The World Forces New Monetary Primitives and the leverage multiple throughout VerifyFlow and Appendix H: Formal Model of Market Realization, Wrapper Flows, and Price Capture.)

$\Delta$ is a distribution, not a number.

Before evaluating either term it is worth fixing what object $\Delta$ is. Every buyer has their own $\varrho$ and their own $\mathcal{L}$, so $\Delta$ is a distribution across the buyer population. The fee bound of Chapter 13: Why Hold the Base Asset? binds at the marginal buyer (the last one the protocol wants to retain at the posted fee), not at the median one. These come apart, and the difference is the whole commercial question. A thin median is entirely consistent with a lucrative fee, provided the upper tail is deep enough to be worth serving. That tail is made of counterparties nobody will indemnify because they are sanctioned or pseudonymous, flows crossing jurisdictions where no single forum will hear the claim, regulated model-risk and audit functions that must evidence correctness to a supervisor rather than merely believe it. For those buyers $\varrho$ is not small, because the indemnitor substitute is unavailable rather than merely inferior. The protocol’s commercial problem is therefore not “is the median workload willing to pay,” which it plainly is not, but “is the high-$\Delta$ tail large enough, and reachable enough, to carry a fee.” That is a sizing question the thesis has not answered, and Red Line 14 measures it capacity-weighted across the served mix rather than assuming it.

And at the median the answer is unflattering.

Written as $\varrho\,\mathcal{L}$, the critical term is $\varrho$, and here the thesis has been flattering itself. The bypass channel is not “unverified.” It is reputationally and contractually verified. A hyperscaler’s alternative to a cryptographic proof is its balance sheet, its SOC 2 and ISO audit reports, its published incident history, and an indemnity clause enforceable in a court that will actually hear the case.

A creditworthy, suable indemnitor is an excellent substitute for a cryptographic proof.

For an ordinary commercial workload in a benign state, the buyer’s exposure to undetected misexecution is not $\mathcal{L}$; it is $\mathcal{L}$ net of a contractual recovery from a solvent counterparty under a legal system that functions. That makes $\varrho$ small, and therefore $\Delta$ thin over the bulk of the distribution. Thin $\Delta$ against a structurally positive $(c_p - c_b)$ is the strongest form of the objection this section opened with, and it is not answered by incidence analysis. It has to be stated plainly, because a critic will otherwise state it first and more crudely: for the median commercial workload in a working legal order, cryptographic verification is a premium product competing against a cheaper substitute that is good enough. What that sentence does not say, and what a fair reading of it must preserve, is that the median is the marginal buyer. It is not, and the fee is set against the tail.

The Tail Is Bimodal, and the Two Modes Are Mutually Corrosive

The fee is not set at the median. Chapter 13: Why Hold the Base Asset? put it at the marginal buyer in the upper tail — counterparties nobody will indemnify, flows no forum will hear, supervised functions that must evidence correctness rather than merely believe it — and then asked whether that tail is large enough to carry a fee.

That is the wrong question, because the tail is not one population. It is two. They want opposite things, and the thesis has been quietly adding them together.

The Two High-$\Delta$ Segments

Segment S (supervised). Regulated model risk, audit, clinical and pharmaceutical attestation, regulated AI deployment, supply-chain provenance under statutory duty. $\varrho$ is high because the loss is regulatory rather than financial: “we relied on the vendor” is not an answer a supervisor accepts, and no indemnity cures a sanction. What Segment S requires is evidence: scoped disclosure, viewing keys, named counterparties, jurisdictional clarity, retention.

Segment X (unsuable). Cross-jurisdictional, pseudonymous, sanctioned, capital-controlled, or adverse to the forum itself. $\varrho$ is high because the indemnitor substitute is unavailable rather than inferior — there is no solvent counterparty a court will make pay. What Segment X requires is absence: large anonymity sets, no disclosure surface, no perimeter identification, nothing that constitutes a subpoena target.

Both have genuinely high $\Delta$. Each one’s requirement is the other’s disqualifier.

The corrosion is not about the rail. It is about the set.

An anonymity set is a room. Segment S cannot afford to be seen entering a room that contains Segment X; Segment X is worth nothing in an empty room. Both want the same room, and each wants different people in it.

The obvious objection is that the thesis has already solved this: lawful privacy is default-private with optional disclosure, so Segment S turns viewing keys on and Segment X leaves them off, and both use the same protocol. That answer is correct at the level of the rail and it does not reach the actual problem, which is one level down.

Privacy is a network good. What Segment X buys is not a cryptographic property of its own transaction but the size and composition of the crowd it is indistinguishable within, and that crowd is shared. So is the crowd’s legal character. The two segments do not merely coexist on a rail; they occupy one another’s anonymity set, and each one’s presence changes what the set is worth to the other:

• S needs X to be absent. A compliance function cannot knowingly transact into an anonymity set containing designated parties, because the commingling is the sanctions exposure. The disclosure it can make about itself does not discharge a duty about who else is in the pool.

• X needs S to be present. Chapter 30: Risk Analysis & Failure Modes, Red Line 7, already states the mechanism: privacy that only outlaws use is a shrinking set. It is precisely the ordinary, legitimate, high-volume users who make blending plausible, and Segment S is the largest available source of them.

The dependency therefore runs one way and the repulsion runs the other. Segment X wants Segment S in the pool; Segment S wants Segment X out of it. That is not a stable composition, and no cryptographic feature resolves it, because the quantity in dispute is the population rather than the protocol.

Price discrimination is available and it destroys the good it prices.

The standard response to two segments with different willingness to pay is to serve them in separate tiers at separate prices, and the tier machinery of Chapter 22: Layer 4: Truth & Work would support it. Applied here it fails in a specific and instructive way.

Separating the segments into tiers separates their anonymity sets, and set size is the product. Two pools of half the size are worth less than one pool to every participant in both. Price discrimination on an ordinary good extracts surplus from each segment at its own willingness to pay; price discrimination on a network good extracts surplus while simultaneously reducing the quantity being sold, and here the reduction falls hardest on the segment whose $\Delta$ is highest.

You cannot segment a network good without degrading it. The protocol can price the two tails separately or it can pool them, and pooling is the only configuration in which either tail gets what it is paying for.

The consequence for the fee, stated precisely.

Chapter 13: Why Hold the Base Asset? binds the fee at the marginal buyer. With two segments sharing one pool, and price discrimination unavailable for the reason above, the protocol is not choosing between $\Delta_S$ and $\Delta_X$ and it is not collecting their sum. It is setting one fee against whichever segment it is unwilling to lose, and the achievable revenue is not additive across the tails:

$$\begin{aligned} &\mathrm{Rev} \;\leq\; \bigl(\min(\Delta_S,\Delta_X) - (c_p - c_b)\bigr)\cdot(Q_S + Q_X) \quad\text{under pooling, or}\\ &\qquad\text{separated tails at reduced } \Delta \text{ each.} \end{aligned}$$

Neither branch yields the quantity a naive reading of Chapter 13: Why Hold the Base Asset? suggests. $f$ and $Q$ are anticorrelated through the same distribution: a fee set at the higher tail sheds the volume of the lower one, and a fee set to retain both is bounded by the lower. The document has been treating “is the tail large enough” as a sizing question with one answer. It has two, and they interact.

Which architecture serves which segment.

Chapter 8: The Triad and the Monetary Candidate compares three architectures without pre-selecting one, and this subsection supplies a discriminating criterion the comparison did not previously have:

• Architecture A (one native monetary asset) forces both segments into one pool, one governance, and one legal posture. It maximizes set size and maximizes the corrosion. It is the configuration in which an enforcement action against Segment X is an enforcement action against Segment S’s counterparties.

• Architecture B (neutral reserve plus typed service claims) allows the segments to sit in different service claims over a shared reserve. It is the only one of the three in which the pools can differ while the monetary object does not.

• Architecture C (shared settlement, modular domain collateral) separates the collateral but not necessarily the sets, so it inherits the corrosion without the containment.

This does not select an architecture. It states, for the first time in this document, what the selection would have to be made on: not cross-subsidy and governance scope alone, but whether the architecture can hold two mutually corrosive high-$\Delta$ populations without losing one of them.

The instrument, and why it cannot be the obvious one.

The obvious measurement is anonymity-set composition by segment. That measurement is not available and must not be built, because a set whose composition is published is not an anonymity set — the instrument would destroy the property it measures, and a protocol that could report who is in its pool has already failed Chapter 4: First Principles: What a SoV Must Survive.

What is observable is departure, which is a behavioural series rather than a census:

• Compliance-side attrition after enforcement events. Supervised counterparty count and volume in the windows following a designation or enforcement action touching the protocol’s pools.

• Exit-side attrition after disclosure events. Shielded-pool activity and non-custodial share in the windows following the shipping or mandating of any disclosure surface, viewing-key requirement, or perimeter identification.

• The cross-correlation of the two series over rolling windows. A persistently negative correlation is the corrosion, measured without anyone being identified.

A protocol that shows both series declining together is losing the tail from both ends, which is the configuration in which the fee bound of Chapter 13: Why Hold the Base Asset? goes to zero without any bypass channel being responsible.

Two Bypass Channels the Thesis Has Not Been Counting

Both of the following erode the base without tripping the instruments currently pointed at bypass.

Partial bypass at the intensive margin.

Bypass has been modelled as a routing decision — the buyer uses the protocol or does not. In practice the buyer uses less protocol per unit of underlying activity: batching many operations under one proof, aggregating proofs recursively, or using the protocol purely for attestation while executing the work elsewhere. Each is a legitimate engineering optimization, and each cuts native fees per unit of real economic activity. None of it registers as a Red Line 6 style “usage without fees” signal, because usage does still route through the protocol — just thinner. The correct denominator for fee intensity is the underlying economic activity being attested, not the count of protocol interactions, and the thesis has not been measuring it that way.

The protocol can be forked.

This is the more important omission. In an open-source, open-admission, canonically-specified market, the cheapest bypass channel is not a hyperscaler. It is this protocol, copied, with a lower fee and no burn. Every property the thesis is proud of — published workload specifications, open verifier implementations, permissionless participation, no vendor chokepoints — lowers the cost of producing that copy. A fork inherits the technology and discards the tax.

What actually prevents the fork from winning is not any of the five conditions. It is liquidity depth in the native asset, anonymity-set size in the privacy corridors, the installed collateral base and the operator relationships around it, the Schelling-point status of the workload registry, and the accumulated receipt history that makes one chain’s attestations worth citing. Those are network effects and coordination assets. They are not enforcement rules, and the thesis has been attributing the moat to enforcement rules. Stated honestly: Chapter 13: Why Hold the Base Asset? explains why a user cannot get the service without the asset on this protocol. It does not explain why the user cannot get it on the copy. Whatever answer exists is a liquidity and coordination argument, it is empirical, and it belongs to link 7; whether holders then warehouse the asset’s risk belongs to link 8.

This is not purely hypothetical, and the one well-documented case ran exactly this experiment against exactly this kind of moat. In 2020, SushiSwap copied Uniswap’s open contracts and paid liquidity providers to migrate — a deliberate attack on a liquidity-and-coordination moat by an identical copy with better short-term incentives. The moat held. Liquidity depth, accumulated positions, and the receipt history a trader’s history lives in did not transfer with the code, and the copy won a share rather than the market. That is one observation in one corner of the design space, not proof — but it is evidence that the moat in question is real, and evidence about which moat: what defended the incumbent was not its technology, which was copied freely, but the coordination assets stacked on top of it. It is precisely those assets, and not the open specification, that a fork of this protocol would have to defeat.

The Fork Is an Equilibrium, Not a Competitor

The cheapest bypass is not a hyperscaler. It is this protocol, copied, with the fee removed.

Chapter 13: Why Hold the Base Asset? concedes that, and concedes what actually stops the copy: liquidity depth, anonymity-set size, the installed collateral base, the registry everyone cites, the receipt history worth citing. Network effects, in other words, and not one of the five lemma conditions. The concession is correct. It was filed under the wrong heading.

Modelled as a bypass channel, the fork looks like the end of the fee. Modelled correctly, it changes what the fee is bounded by.

Two different bounds, and the binding one is not always the same.

The sustainable-fee bound of Chapter 13: Why Hold the Base Asset? is $f \leq \Delta - (c_p - c_b)$, where $c_b$ is the all-in cost of the best bypass channel. Against a hyperscaler that expression carries the structurally positive cost handicap the section emphasizes: verified compute costs more to produce than unverified compute, and the protocol must recover the difference out of $\Delta$ before collecting anything.

Against a fork the arithmetic is different in a way worth stating explicitly. The fork runs the same technology, so $c_b = c_p$ and the handicap vanishes. What remains is

$$f \;\leq\; \Delta_{\mathrm{coord}},$$

the differential value of transacting on this instance rather than on an identical copy, which is not a cryptographic property at all. It is liquidity depth, anonymity-set size, the installed collateral base and the operator relationships around it, whether the workload registry is the one everybody cites, and whether a receipt from this chain is worth citing because of what else is in its history.

The two bounds are separate quantities and the protocol is subject to both:

$$f \;\leq\; \min\bigl(\underbrace{\Delta_{\mathrm{tech}} - (c_p - c_b)}_{\text{versus the unverified alternative}},\; \underbrace{\Delta_{\mathrm{coord}}}_{\text{versus the identical copy}}\bigr).$$

This is a real tightening of Chapter 13: Why Hold the Base Asset?, which stated only the first term, and it is the correct place to put the concession Chapter 13: Why Hold the Base Asset? made informally.

Contestable markets and coordination games give opposite predictions, and only one of them is the right model.

The objection that opened Chapter 13: Why Hold the Base Asset? (a contestable market competes economic profit to zero) is the right model for the hyperscaler comparison and the wrong one for the fork. Contestability assumes entrants and incumbents are substitutes at the margin for each buyer independently. They are not, when the good’s value to each buyer depends on how many other buyers chose the same instance. That is a coordination game, it has multiple equilibria, and equilibria are not competed away by a better price but displaced by a focal point moving, which is a different and much slower mechanism.

A contestable market has one equilibrium and prices race toward it. A coordination game has several, and the incumbent’s advantage is not that it is better but that everyone is already there.

Openness cuts both ways, and the thesis has counted only one direction.

Chapter 13: Why Hold the Base Asset? observed that every property the thesis is proud of (published workload specifications, open verifier implementations, permissionless participation) lowers the cost of producing the copy. True, and incomplete. Those same properties operate on the two bounds in opposite directions:

• Openness drives $\Delta_{\mathrm{tech}}$ against a fork to zero. There is no technical differentiator, by construction and by design commitment.

• Openness raises $\Delta_{\mathrm{coord}}$. A canonical workload registry that is public, stable, and cited by everyone is more focal than a proprietary one, not less. Schelling points are made of common knowledge, and publishing is how common knowledge is manufactured. The same is true of an open receipt history: its citability is a function of how many independent parties already read it.

So the honest statement of the trade-off, in the form Chapter 13: Why Hold the Base Asset? uses for collateral:

Openness must be total for the technology and is the mechanism by which the coordination assets accumulate. You cannot have a defensible technical moat and an open specification. You can have an open specification and a focal point, and the second is the only moat this design is entitled to.

And the moat is buyable, which is the part that keeps it honest.

$\Delta_{\mathrm{coord}}$ is not a law of nature. A challenger can rent it: subsidize liquidity, pay operators to migrate, underwrite the anonymity set, and buy the switching costs down. This is the fork’s actual attack and it is a capital question rather than a technical one. The defensible claim is therefore narrow: the fee is bounded by what it costs a challenger to move the focal point, and that quantity is empirical, contestable by capital, and not guaranteed to exceed the fee.

The one case, in the right reference class and with its limits stated.

Chapter 13: Why Hold the Base Asset? cites the 2020 SushiSwap attack on Uniswap: an identical copy of open contracts, paying liquidity providers to migrate, attacking a liquidity-and-coordination moat directly, and winning a share rather than the market.

Two corrections to how that case was used. First, the relevant reference class is not “forks” in general but coordination games in which an installed focal point is challenged by an identical copy with better short-term incentives. In that class the observation is on point rather than cherry-picked, because it is a direct test of $\Delta_{\mathrm{coord}}$ against paid switching. Second, and stated plainly because the thesis holds itself to base rates elsewhere: it is one observation, it was selected after the fact, the incumbent survived, and a single surviving incumbent is not a base rate. It establishes that coordination assets can hold against a funded identical copy. It does not establish how often they do, or that they would here.

What this changes in the instruments.

Two additions, both small and both closing gaps that the bypass framing left open:

• Red Line 14’s reference panel gains a fork row. The pre-committed panel of Chapter 30: Risk Analysis & Failure Modes lists hyperscalers and GPU marketplaces, venues that measure $\Delta_{\mathrm{tech}}$ only. The lowest-fee protocol-grade fork offering the same canonical workload must be priced into $P^{\mathrm{byp}}$ on the same terms, because it is the channel with no cost handicap and therefore the one that binds first. A wedge measured only against unverified alternatives is measured against the weaker competitor.

• Acceptance breadth becomes a published series. The number of independent venues, corridors, and counterparties that quote, settle, and cite this instance rather than any other is the observable form of $\Delta_{\mathrm{coord}}$, and it belongs beside the denomination series of Chapter 13: Why Hold the Base Asset? on the Value Capture Board (Chapter 26: Extended Telemetry). Both measure coordination; one measures whether people reckon in the unit and the other whether they converge on this instance of it.

Where this leaves link 7.

Non-bypassability was reduced from Strong to Medium in Chapter 8: The Triad and the Monetary Candidate because the economics requires a magnitude that is nowhere estimated. Nothing here raises it. The magnitude is now specified as two magnitudes rather than one, the second of which the document had been treating as an admission rather than a term, and both remain unestimated. What has changed is that there is now an instrument pointed at each.

Openness has one further effect that neither bound prices: a protocol anyone can implement is a credible entrant against the incumbents it contests, and the credible possibility of entry can discipline conduct without any entry being observed [Baumol 1982], which can serve agency while leaving the asset nothing to capture (Chapter 8: The Triad and the Monetary Candidate).

The open stack as an entrant that never enters.

The incumbents in question are the hyperscalers and the closed stack of Chapter 33: The Closed Sovereign Stack, the comparison for which contestability, wrong for the fork, is the right model. The mechanism is the one this Part already borrows for verification that is always available and seldom exercised (Chapter 13: Why Hold the Base Asset?). An incumbent that lowers its rent or loosens its lock-in to keep the users an open stack could take has handed those users part of the agency the stack exists to preserve, while the asset has collected no fee, warehoused no balance, and settled no transaction. That outcome is a success for agency and a failure for money. The investment thesis already counts the first half as a return on public infrastructure (Chapter 32: Kardashev Labs: Build and Measure), and the chain’s second question keeps it from being counted as capture (Chapter 8: The Triad and the Monetary Candidate).

Who earns the return on an open protocol.

The economics of innovation has a standard answer, and it is not reassuring for the asset: when imitation is easy, “the profits from innovation may accrue to the owners of certain complementary assets, rather than to the developers of the intellectual property” [Teece 1986]. An open protocol makes imitation easy by design. At the fork, the complementary assets that decide the contest are the protocol’s own coordination assets (the liquidity, anonymity set, registry, and receipt history that $\Delta_{\mathrm{coord}}$ prices), which is why the only moat left is a focal point rather than a technology. Against incumbents, they are the distribution, custody, and hardware that others already own, which is the wrapper problem met from the other side (Chapter 13: Why Hold the Base Asset?).

The fork’s four questions are the chain’s four, asked from the exit.

Each lands on a row of Chapter 8: The Triad and the Monetary Candidate, and the mapping adds no category the chain does not already have:

• Which benefits persist because coordination is genuinely valuable is the first question, useful services, asked at the margin of $\Delta_{\mathrm{coord}}$: what users get from this instance that an identical copy would not give them.

• Which revenues depend on avoidable friction is the second, asset value capture. Revenue above the binding term of the fee bound is friction a funded copy can remove, as an incumbent’s rent above the contestable level is friction the open stack can remove; only what sits under the bound is capture.

• What users can take with them when they leave is the mission’s half of the fourth question. Open specifications, portable receipts, and self-custodied keys leave with the user, and that portability is what makes exit credible enough to discipline anyone.

• What still requires the native asset does not land on a single row, because the asset is required for two different reasons: as the fee medium where the lemma’s conditions hold (Chapter 13: Why Hold the Base Asset?), which is the second question, and as a held balance only inside the band where conversion fails (Chapter 13: Why Hold the Base Asset?), which is the third.

What the Five Conditions Establish, and What They Do Not

Collecting the above fixes what the lemma’s conditions can deliver.

What they establish.

That a contestable market can be taxed and the proceeds routed to a token. Specifically: (i) a competitively priced claim on a cash-flow stream $f \cdot Q$, bounded above by the per-unit wedge $\Delta$ applied to volume ($\bigl(\Delta - (c_p - c_b)\bigr) \cdot Q$ at the sustainable-fee bound of Chapter 13: Why Hold the Base Asset?) and deflating with unit price; and (ii) a balance-sheet lockup of collateral required in the native unit. Both are real. Both are also, precisely, quantities that a discounted-cash-flow valuation captures: a fee stream and a lockup.

What they do not establish.

Monetary premium. A monetary premium is by construction value in excess of discounted cash flows; it is what gold has and a pipeline does not. A holder who buys a share of the fee stream from indispensable workloads owns something closer to equity in a utility than to a collectible, and a utility equity earns its cost of capital; it does not carry monetary premium. The routing rules of Chapter 13: Why Hold the Base Asset? are design commitments; nothing in this thesis claims that they set a price. The incidence question asked of the fee is asked of each monetary mechanism’s benefit as well (Chapter 13: Why Hold the Base Asset?).

Three corollaries follow:

• A burn is a buyback. Economically, retiring supply with revenue is a pro-rata return of value to an existing claim. Buybacks change per-share value; they do not confer moneyness. No quantity of buyback has ever made an equity a store of value, and no burn schedule will do it either.

• Collateral is a lockup, not a premium. A required lockup denominated in the asset immobilizes float while operators remain solvent and choose to stay, and it places no bid. It is a balance-sheet fact, and Chapter 13: Why Hold the Base Asset? bounds how large a fact it can be.

• A subsidy is a negative fee. Pass [Pass 2026] models proof-of-useful-work economies as three regimes: one in which the work is worthless and the token is pure seigniorage, one in which useful work is sold at cost, and one in which token issuance subsidizes the work below its compute cost. The fee-incidence bound places the second regime at $f \leq \Delta - (c_p - c_b)$ and the third at $f < 0$. A network in the third regime is buying volume with issuance; its receipts are real and its fee coverage is negative, and Red Line 5 and Red Line 14(B) are written to see it. Bitcoin’s work function, which has no external buyer, sits in the first regime by construction, and that is the content of the concession in Chapter 34: Objections & Responses.

The Test That This Reasoning Does Not Prove Too Much

If durable fee extraction from a commoditized flow made an asset money, the world would be full of monetary assets. CME clears standardized futures; DTCC settles equities; Visa takes a spread on card turnover; MSCI licenses indices that everyone benchmarks to; pipelines and port authorities meter physical throughput. All of them sit on flows more commoditized than canonical MatMul, all of them extract fees durably, several are structurally harder to bypass than any protocol will be, and not one of their equities is money. Visa’s take rate does not make Visa shares a store of value; it makes them a good business.

The comparison is the discipline. If the argument for the asset’s monetary premium is “recurring fees on indispensable throughput,” the argument is an argument for a high-quality utility equity, and it should be labelled as one. Something else has to be doing the monetary work.

Pledgeability Without Due Diligence

Nobody examines a banknote. That is not carelessness; it is the property that makes it money. A thing accepted only after inspection is being traded; a thing accepted without inspection is being spent, and the distance between those two — rather than any fact about scarcity or cash flow — is what the collateral literature means by moneyness.

This thesis has been engineering that property for six Parts and calling it a cost metric. Chapter 13: Why Hold the Base Asset? established what the five conditions do not reach; Chapter 13: Why Hold the Base Asset? relocates the claim to a holder-side flow. Between them sits the mechanism that arrives first and measures soonest.

The property that the collateral literature actually calls moneyness.

Outside the store-of-value framing, the working definition of a money-like asset in the study of collateral and short-term funding is not scarcity, not cash flow, and not convenience yield. It is information-insensitivity. An asset is money-like when no counterparty gains anything by investigating the particular unit tendered. Nobody looks, so it passes at face value, and a thing that passes at face value can be pledged without due diligence [Gorton & Pennacchi 1990] [Dang et al. 2020] [Holmström 2015]. Deposits, bills, and repo collateral circulate on that property. It is the property whose failure, rather than any change in fundamentals, is what a funding run consists of.

Two kinds of information, and only one of them is at issue.

The claim collapses immediately unless the object is specified, because transparency plainly does not produce insensitivity in general—equities are the most transparent securities in existence and among the most information-sensitive. The distinction that resolves this is between:

• Fundamental information—what the asset will be worth. Cheap verification does nothing to this, and this thesis claims nothing about it. A triad asset would remain fully information-sensitive on fundamentals, and so does gold.

• Unit-quality information—whether this unit, this receipt, this pledged position is what it purports to be. This is authentication and due diligence on the collateral itself rather than a forecast of its value.

The 2008 collapse in securitized funding is the reference case and it was the second kind. The question that stopped the market was not what housing would do; every participant held a view on that and had held one for years. It was whether a particular pool was good, nobody could answer it cheaply, and so lenders began producing private information about specific collateral, haircuts widened, and no-questions-asked acceptance ended [Gorton & Metrick 2012]. Moneyness failed along the unit-quality axis while the fundamental axis was already common knowledge.

If private information about fundamentals grew more valuable, the split says where collateral demand would lean: the more an edge is worth to its holder, the more the counterparty without one values collateral whose unit quality is public, the one axis on which no edge can be had.

Information-Insensitivity by Symmetric Knowledge

There are two routes to no-questions-asked acceptance, and they are opposites.

Symmetric ignorance is the historical route. Producing information about the specific collateral is expensive relative to the gain, so nobody produces it, and the asset trades at par. Opacity is the mechanism, not a defect of it.

Symmetric knowledge is the route a verification-native asset takes. Producing that information costs approximately nothing and the result is public, so no counterparty can come to hold an informational edge over another. The asset trades at par for the opposite reason.

Both deliver acceptance without due diligence. They differ in how they end. Symmetric ignorance is a knife-edge: it holds only while nobody looks, and the first agent to look acquires an advantage that every other agent must then defend against, which is the run. Symmetric knowledge has no such trigger, because there is no private information about unit quality available to produce; private views about fundamentals remain, and are priced as volatility rather than as due diligence. You cannot start a run by looking when looking is free and public, because looking buys nothing that everyone else could not have had for the same nothing.

The mechanism is deterrence, not audit, and the distinction is the one a critic will press first.

The formulation above deliberately does not claim that everyone has in fact looked. Universal audit is observed nowhere, including in the settings where looking is already close to free: public filings sit unread, open ledgers go unexamined, and the record is routinely both complete and unanalyzed — none of it hidden, and none of it examined ([Green 2026f], where the observation and its limits are attributed). An argument requiring every counterparty to have actually verified would be refuted by ordinary observation on its first day, and a version of this section that rested on one would deserve to be.

Nothing in the mechanism requires it. What removes the run trigger is the absence of a discoverable edge, and free public verification removes that whether or not anyone exercises it. The information is non-rival and non-excludable, so the agent who looks acquires nothing the agent who declines to look could not have had at the same cost. Symmetric ignorance fails because looking is privately profitable to the first mover; symmetric knowledge holds because looking is privately worthless to everyone—not because it is universally performed. A security camera does most of its work on the days nobody watches the tape. The incumbent side has a mirror case, conditional twice over: agents that managed cash by chasing rate would erode a bank’s deposit franchise, a cost of funding rather than a run, and would open a run channel only if they also screened its solvency, and then only on uninsured deposits, which would lose symmetric ignorance without gaining symmetric knowledge.

The discipline therefore operates on the claimant, before the claim is made, in the way the credible possibility of entry disciplines conduct in a contestable market without entry being observed [Baumol 1982]. A misrepresentation any counterparty could falsify at zero cost is not worth attempting, so it is not attempted, so nobody has to check. The equilibrium described here is one in which verification is constantly available and almost never used, and those two facts are the same fact. Two consequences follow that matter for how this thesis is read. The first is that the object to measure is the cost of verification and not the observed rate of it: Red Line 1 reads the standing threat, and a decline in measured verification activity is not by itself evidence against the mechanism provided verification cost has not moved. The second is that a system can be perfectly auditable and monetarily inert, because deterrence requires the claimant to believe that being caught would cost them something—a condition this thesis instruments separately, and takes up in Chapter 13: Why Hold the Base Asset? and Red Line 14 rather than assuming.

This thesis has been describing that mechanism as a cost metric.

The touchstone image of Red Line 1—expensive to smelt, cheap to assay—is not an analogy about operational efficiency. It is a statement that gold is information-insensitive on unit quality, which is why any counterparty could accept a nugget from a stranger without investigating the stranger. Gold’s monetary career is better explained by that property than by a convenience yield it does not have (Chapter 13: Why Hold the Base Asset? notes gold’s storage-theory convenience yield is near zero). The same substitution runs through the rest of the document: $r(W)$ (Chapter 22: Layer 4: Truth & Work), the PIDL receipt schema, the reproducibility contract, and the Layer 0 grade ladder are not merely cheaper ways to run an audit. They are machinery for removing the informational advantage that a counterparty could otherwise hold over the holder of a pledged position.

The clearest evidence that the thesis already believes this is that it already prices it. The collateral haircut schedule of Chapter 17: Layer 0: Verifiable Machines & Energy discounts a position by how legible its physical substrate is; risk haircuts (Chapter 25: Layer 6: Governance & Telemetry) discount it by sovereign optionality; bridge classes carry haircuts by trust assumption. Every one of those is a price on residual unit-quality uncertainty. The document derived an information-sensitivity schedule from engineering intuition without the monetary theory that explains what it was pricing.

What is made insensitive is the position, not the token.

A necessary precision, because the obvious version of this claim is trivial. That a unit of a public ledger is authentic is not a differentiator: it is true of every cryptocurrency and no counterparty has ever had to investigate whether a bitcoin is a bitcoin. That is table stakes and it has never made a token money.

The differentiator is the collateralized position. When the asset is pledged against an obligation to deliver a service—prover bonds, corridor collateral, SLA escrow—what a lender must assess is not the unit but the bundle: whether the capacity behind the obligation exists, whether the operator’s slashing exposure is what it claims, whether the physical substrate can deliver under the scenario the haircut assumes. That is where due diligence lives, and that is what Facility Capacity Receipts, energy receipts, Delivered Verified Capacity (Chapter 17: Layer 0: Verifiable Machines & Energy) and the grade ladder make cheap. It is the first argument in this document for why Layer 0 is a monetary requirement rather than an engineering preference, which is the role Chapter 4: First Principles: What a SoV Must Survive assigns it.

Necessary, not sufficient—and the test that says so.

The discipline of Chapter 13: Why Hold the Base Asset? applies to this section with equal force, and the counterexamples are the thesis’s own. Graded commodities are cheaply assayed and warehouse receipts never became money. Certified diamonds are authenticated to a published standard and are not money. Bearer bonds are authenticable at sight and are not money. Cheap unit verification is therefore not sufficient, and any argument that stops here proves far too much.

What separates the cases is a conjunction. Insensitivity on unit quality becomes monetary only alongside fungibility (certification tells you this stone’s grade; it does not make stones interchangeable), durability and portability (grain is gradeable, perishable, and bulky), and the absence of a counterparty (a warehouse receipt reintroduces the custodian whose solvency must then be assessed, and a bearer bond is somebody’s liability). Gold is the one historical object at that intersection: assayable, fungible, durable, portable, and nobody’s promise. The claim available here is narrow and it is the whole of what this section asserts:

A verification-native digital bearer asset is the second class of object to occupy that intersection—and the first whose assay cost does not scale with the size of the claim being assayed.

That last clause is the only genuinely new term. Assaying a larger quantity of metal costs more; destructive sampling scales with the lot. Verifying a succinct proof costs the same whether the claim underneath it is worth a dollar or a billion. The cost of establishing unit quality has been invariant to notional in no prior monetary object, and if information-insensitivity is what makes collateral money-like, an assay whose cost does not grow with what is at stake is a change in kind rather than in degree.

What this predicts, and what it does not.

A reader of Dang, Gorton and Holmström [Dang et al. 2020] will object that their insensitivity is a property of the payoff structure. A security is insensitive when the expected gain from producing private information about its payoff is below the cost of producing it. That is why over-collateralized debt—flat over the relevant states—is the natural money-like security, and why driving information cost to zero on a security with a state-dependent payoff makes it more sensitive, not less. The objection is correct, and it fixes the scope of this section. The argument made here is the adverse-selection argument on unit quality, not a claim about payoffs: free public verification removes the class of private information that concerns whether the pledged position is what it purports to be, and leaves the class that concerns what it will be worth untouched. Bitcoin is the control case. Its unit quality has been perfectly and freely verifiable since 2009, and its collateral haircuts nonetheless sit at 30–50% and vary widely across lenders, because those haircuts are pricing realized volatility and liquidation depth, which no verifier can compress. Cheap verification therefore cannot be expected to lower haircut levels on a volatile bearer asset, and the thesis does not predict that it will.

What it predicts is narrower and is the content of Red Line 17. Controlling for realized volatility and market depth, a position whose backing is publicly verifiable at VerifyPrice should show (i) lower dispersion of haircuts across lenders than an opaque comparable, because the due-diligence component that lenders price idiosyncratically has been removed, and (ii) faster convergence of haircuts after a shock, because there is no private information for the cautious lender to be waiting on. Pledgeability without due diligence attaches in full force to the position—over-collateralized, DVC-backed, with a debt-like payoff over the states the haircut assumes—and in attenuated form to the bare base asset; a lender who wants a flat payoff builds one out of the base asset and a haircut, and what Layer 0 sells that lender is the ability to size the haircut from public facts. Red Line 17 tests exactly that, and is specified so that Bitcoin’s own record—native units against wrapped and custodial representations of the same units—is a case it can pass or fail rather than one it fails by construction.

A second invariance, and the objection it answers.

The strongest available objection to any cheap-verification argument is that verification is not the only thing getting cheaper. If the cost of manufacturing plausible false claims falls at least as fast as the cost of checking them—synthetic corroboration, fabricated provenance, volume sufficient to exhaust the checker’s attention—then the informational balance is unchanged and nothing monetary follows. The objection is correct in general and it is fatal to arguments about verification conducted in natural language, where discrimination between a true and a false claim degrades as the adversary invests.

Cryptographic verification does not have that gradient, and this is the second respect in which it is unlike every prior assay. Under stated soundness assumptions — the hardness and parameter assumptions, and a circuit and verifier that constrain what they claim — a false proof is not expensive to produce; it is infeasible, and the verifier’s cost of rejecting one is identical to its cost of accepting a valid one. Attempts do not accumulate into persuasion: a thousand forged proofs are a thousand rejections, and no quantity of surrounding corroboration moves the outcome, because nothing outside the proof is consulted. Verification cost is invariant to the size of the claim and invariant to the effort of the adversary, and the second invariance is the one that survives contact with an opponent who is also getting better tools.

The bound on that claim is stated with equal force, and it is the bound already set out at the head of Chapter 10: Proofs as Attestation Money: a proof is a bounded attestation, not truth. It establishes that a computation followed a circuit or that a receipt descends from a signed chain. It establishes nothing about whether the workload was worth running, whether the operator’s off-ledger position is what they say, or whether the sentence a human attached to the artifact is honest. The class of claims over which this thesis’s verification is adversarially invariant is exactly the class that can be stated as a computation, and that class is considerably narrower than the class of claims on which trust is currently failing. Where the two do not overlap, this thesis has nothing to offer and should not be read as offering it.

Issuance discipline reappears here, and not as scarcity.

Condition 4 of the Value Capture Lemma required issuance to be capped by schedule or capacity rather than by governance fiat, and Chapter 13: Why Hold the Base Asset? observes that issuance discipline is the one lemma condition touching the monetary channel without explaining what distinguishes it. This section supplies the explanation. An asset whose supply is a discretionary decision is information-sensitive on supply: a counterparty must form and maintain a private view of what the issuing body will do, which is due diligence by another name, and an asset requiring due diligence cannot be accepted no questions asked. Credible non-discretion is not only a scarcity property. It is the condition under which the supply schedule stops being something anyone has to have an opinion about.

Who pays for verification, and why the free-rider problem does not bind here.

Grossman and Stiglitz [Grossman & Stiglitz 1980] established that a market cannot be both costlessly informative and informative at all: if prices already reflect everything knowable, no agent is compensated for the costly work of producing information, so the work is not done and the prices stop reflecting it. Informativeness has to be paid for by somebody, and an equilibrium in which nobody is paid is not an equilibrium. The same structure threatens the argument of this section in an obvious form. If verification is free, nobody earns a return on verifying; if nobody earns a return on verifying, what sustains the apparatus that makes verification possible, and why does the symmetric-knowledge regime not decay back into the ignorance it replaced?

The objection is a real one, and it is the reason this section does not rest on transparency in the general case—where it would bind, and where the historical record of unread disclosure suggests it does. What answers it is a property specific to proof systems and absent from the Grossman–Stiglitz setting: the cost of producing the information and the benefit of consuming it fall on different parties, and the party bearing the cost bears it voluntarily. In their model the same act, research, is simultaneously the expenditure and the source of the private return, which is what forces the informational rent that makes prices imperfectly informative. In a proof system the expenditure sits with the prover, who incurs it in order to be believed, and the result is consumed by every counterparty at negligible marginal cost. Verification is therefore not an underprovided public good waiting for a subsidy or a rent. It is a private good purchased by the party who wants their claim accepted, and its public checkability is a by-product that the purchaser cannot withhold without destroying the thing they were buying.

The same asymmetry, read from the financing side, is why the fee argument had to be conceded.

Chapter 22: Layer 4: Truth & Work states this separation as $r(W) = v(W)/p(W)$ and treats it as an engineering property. It is also an industrial-organization property, and reading it that way closes a loop this Part opened. Because the prover is buying credibility in a market where any competent competitor can sell the same credibility, the price of proving is competed toward the cost of proving. That is precisely the finding of Chapter 13: Why Hold the Base Asset?: the fee stream is ordinary service revenue, competitively priced, and reproducible by a discounted-cash-flow valuation. The property that makes verification sustainably supplied is the same property that stops it from being a source of excess return, and the thesis should not have expected to keep both. The two results are one result seen from opposite sides, and their agreement is a constraint the argument has to live inside rather than a coincidence worth celebrating: whatever monetary premium exists is not in the proving business, which is why Chapter 13: Why Hold the Base Asset? and Chapter 13: Why Hold the Base Asset? look for it somewhere a valuation cannot follow.

How symmetric knowledge fails, stated before a critic states it.

The mechanism is not indestructible, and its failure modes are already red lines, which is the useful part. Symmetric knowledge reverts to ignorance whenever verification stops being free and universal: when verification affordability breaks, when verification concentrates such that most participants are trusting a verifier rather than verifying, or when the underlying receipt data becomes unavailable or proprietary. Each of those has been treated in this document as a degradation of service. Each is also, on the argument above, a monetary run trigger, and should be read as one.

A fourth failure mode is not covered by any red line and is named here rather than deferred: scope drift between what is verified and what is exposed. A position can be perfectly legible on its proof and entirely opaque on the operator’s off-chain leverage, counterparty concentration, or rehypothecation. Verification that certifies the computation while the exposure sits elsewhere reproduces exactly the 2008 structure with better cryptography. The gap is measured as the off-ledger exposure disclosure series on the Value Capture Board (Chapter 26: Extended Telemetry, Appendix B: Practical KPIs & Telemetry Templates): the share of pledged-position notional whose operator publishes an attested disclosure of off-ledger leverage, counterparty concentration, and rehypothecation, bound to the position’s receipts. It carries no trigger of its own in this version; it feeds the RL17 lender panel and the RL10 opacity reading, and it exists so that the gap is a published number rather than a caveat.

What this section does not claim.

Four disclaimers, because the temptation to over-read this is considerable. It does not claim price stability: an information-insensitive asset can be violently volatile, and gold and Treasuries both are. It does not claim insensitivity on fundamentals, only on unit quality and pledged-position quality. It does not claim that acceptance follows automatically from measurability; whether any lender actually extends no-questions-asked terms is an empirical outcome, not a design consequence. And it does not raise any rating in Chapter 8: The Triad and the Monetary Candidate: this section supplies a mechanism and an instrument for link 9, not evidence that link 9 holds. Ratings that rise because an argument was added are self-congratulation.

The instrument: haircut level, and more sharply, haircut dispersion.

The mechanism is measurable well before the asset is anything, and one of the two available readings is much cleaner than the other. Haircut level confounds what this section is about with ordinary price volatility: a lender demands over-collateralization for both reasons and the level does not separate them. Haircut dispersion across lenders separates them better, but not by itself: lenders differ in funding costs, balance-sheet limits, liquidation capacity, and terms, and lenders running one shared model can agree while sharing its error. The comparison that isolates the sensitivity at issue is relative — dispersion on the native asset against dispersion on an opaque comparable of similar volatility, quoted by the same lenders at the same moment — because whatever is particular to each lender enters both quotes and differences out. What remains is evidence about unit-quality information under that comparison, not an identity with it, and agreement produced by a shared underwriting model is not counted.

Publish, per quarter, against a pre-committed panel of lending venues on the same custody and reproducibility terms as the Red Line 14 reference panel:

• Haircut level on the base asset and on pledged positions, by collateral class and Layer 0 grade.

• Haircut dispersion—the cross-lender interquartile range at a common timestamp—as the primary series.

• Due-diligence cost: the observable cost of onboarding the asset as collateral at a new venue, in time and fees, which should fall toward zero if the mechanism is working.

• Dispersion conditioned on stress, since the prediction with the most content is about the shape of failure rather than its level.

The prediction is specific enough to lose. An information-insensitive asset shows haircuts that are tight at whatever level volatility sets, and—this is the discriminating claim—dispersion across lenders that sits below that of comparable opaque collateral and does not widen relative to it when the market does, because there is no private information for a stressed lender to price. The historical signature of a funding run is dispersion widening before level, as the better-informed lenders withdraw first. If that signature appears here, against the comparables and with full receipt availability, symmetric knowledge did not hold, and the mechanism this section proposes is not present in the asset.

The falsifier. This mechanism is made falsifiable as Red Line 17 (Chapter 30: Risk Analysis & Failure Modes): cross-lender haircut dispersion on the native asset that is not lower than on comparable opaque collateral, or that widens relative to it or re-converges more slowly under stress while receipts remain available, is this section’s claim failing in public.

Two mechanisms, and they are complements.

This section and Chapter 13: Why Hold the Base Asset? are not rival accounts, and the difference between them is worth stating in one line because they answer different questions. Information- insensitivity is why a counterparty would accept the asset without investigating it. The regime-contingent holder-side flow is why a holder would want it when other arrangements fail. Acceptance without demand is a payment rail; demand without acceptance is a collectible. A monetary asset requires both, and Chapter 13: Why Hold the Base Asset? adds the third question — whether anyone will reckon in it. The thesis argues all three, sizes none, and publishes an instrument for each.

Who collects first.

An instrument that reads whether a mechanism works does not read whom it works for, and the incidence question that Chapter 13: Why Hold the Base Asset? put to the fee has to be put to each of the three, turned from who bears a cost to who collects a benefit. Each has a first beneficiary, a channel that would carry the benefit on to the asset, and evidence, or its absence, that the benefit reaches a persistent, self-custodied, loss-bearing holder rather than stopping with whoever touched it first. Asking is how the pass-through gets instrumented; it is not a doubt that the pass-through happens.

• Pledgeability. The saving from whatever the mechanism compresses on the over-collateralized position goes first to the borrower who posts it. Narrower dispersion across lenders, cheaper onboarding at a new venue and a smaller margin for what a cautious lender cannot check are savings to the operator or prover that pledges: it can borrow more against the same capacity, or post less for the same loan. The channel from that borrower to the base asset is asserted, not measured. The thesis asserts it twice: a lender who wants a flat payoff builds it from the base asset and a haircut, as the prediction above sets out, and the collateral Condition 3 requires must be native in order to create native demand (Chapter 13: Why Hold the Base Asset?). A borrower can equally take the cheaper credit and sell every unit it earns. Red Line 17 reads whether dispersion compresses, as its box specifies, and nothing in it says who keeps the gain. The pass-through is read from series that already exist: the lender panel’s split by borrower class (Chapter 30: Risk Analysis & Failure Modes), beside the buyer map’s operator sell-through, self-custodied reserve cohort, holding period and leverage, each classified by principal (Chapter 26: Extended Telemetry). Compression that arrives with retained, self-custodied, unlevered balances growing in the borrowing cohorts is read as the benefit travelling on; compression that arrives with sell-through and leverage rising is read as the borrower keeping it. Condition 3’s required collateral counts toward neither reading, because a lockup places no bid, and pledged units count only as far as the buyer map’s leverage and self-custody criteria allow. The reading carries no trigger of its own.

• The holder-side flow. Here the first beneficiary is the holder, and no channel is needed: the service accrues to whoever bears the unit, by bearing it (Chapter 13: Why Hold the Base Asset?). The question narrows to which holder. A wrapper holder is not one, since a wrapper premium is the price of not holding natively, and a holder who lends the unit out has sold the flow for the term of the loan (Chapter 26: Extended Telemetry). What separates a persistent holder from a buyer who arrives with the stress is when the units were acquired. The convenience-yield series say whether the flow exists at all; the buyer map’s countercyclical accumulation, read net of exercise, says whether the holders who collect it were there before the stress.

• Denomination. The first beneficiary of a contract the parties chose to write in the unit is the party whose costs and revenues both sit in it, which stops paying to hedge a basis it no longer carries (Chapter 13: Why Hold the Base Asset?). The channel to the asset would be the balance held against an obligation in the unit, and that is a working balance before it is anything else; turnover in a working balance is not reserve demand (Chapter 12: Work Credits: Reserved Service Claims). The denomination instrument counts contracts, not balances, so the evidence is the buyer map’s again: just-in-time acquisition against retained balances, and holding period by cohort.

Only the holder-side flow pays the holder first.

Where a Monetary Premium Would Actually Come From

The constructive half. If fees, burns, and collateral yield a well-valued cash-flow claim rather than money, the monetary claim has to be relocated rather than abandoned — and the place it relocates to is one the thesis has already spent six Parts describing without noticing that it was the monetary argument.

$\Delta$ is not a constant; it is a function of regime pressure.

Write $\Delta(R)$, with $R$ the regime-pressure index of Stage A (Chapter 13: Why Hold the Base Asset?). Chapter 13: Why Hold the Base Asset? showed why $\Delta$ is thin in benign states: a solvent, suable indemnitor substitutes for a proof. Invert that sentence and it names exactly when $\Delta$ is large. The substitute fails when the counterparty:

• cannot be sued — cross-jurisdictional, pseudonymous, or sanctioned, so no forum will hear the claim;

• will not be solvent when it matters — the failure is correlated, and the indemnity is worth least in exactly the state that triggers it;

• is the adversary — a state, a platform, or a regulator, where the entity you would sue is the entity imposing the loss;

• inflicts a non-compensable loss — censorship, seizure, deplatforming, or disclosure, where damages do not restore the position because the position was never about money.

That list is the threat model of Chapter 5: Threat Model, restated as a demand curve. The thesis is therefore internally consistent — but the consequence is unflattering to fee accrual as a monetary argument and places the monetary burden on links 8 and 9:

$\Delta$ is small in benign states and large in the tail. The asset’s usefulness is state-contingent, and its distribution is skewed toward exactly the states everyone else’s arrangements stop working in.

State-contingency does two different things, and only one of them is monetary.

The tempting move here is to say that an asset whose usefulness rises in states where the marginal utility of wealth is high must be worth more than the discounted expectation of its cash flows, because those cash flows arrive weighted by a high state price. That move fails the test this section’s own demolition just set. Chapter 13: Why Hold the Base Asset? defined a monetary premium as value in excess of discounted cash flows, and a discounted-cash-flow valuation carried out with the correct stochastic discount factor already weights every cash flow by its state price. State-price weighting is what a risk-adjusted discount rate summarizes — and a single discount rate summarizes it correctly only when payoffs are not heavily state-contingent, which this asset’s are. A payoff this state-contingent needs the stochastic discount factor itself, not the single scalar that compresses it. An argument that stops there has relocated the monetary claim into the denominator of a DCF, which is not outside the DCF at all. The argument therefore has to be split into two mechanisms, one conceded and one kept.

Mechanism one: a negative beta on the fee stream. Real, valuable, and not monetary.

Because $\Delta(R)$ rises when the substitutes fail, the fee stream is countercyclical with respect to regime pressure: the protocol can charge most for its differential properties in the states where wealth is scarcest. A rational investor pays more per unit of expected cash flow for that stream than for a procyclical one, and should. But this is exactly a discount-rate effect. It lowers the cost of capital applied to the same fee stream, it is fully representable inside a discounted-cash-flow valuation, and it therefore produces no moneyness. A countercyclical utility is a better utility, not a monetary asset. Conceded, and set aside: nothing in the monetary claim below rests on it.

Mechanism two: a holder-side service flow. This is where a monetary premium would have to live.

The bearer of the asset obtains something that is not a cash flow at all, and so has no cash flows to discount: the ability to transact, prove, hold, and exit at the moment when the substitutes for proofs, courts, and custodians have stopped working. That service accrues to whoever holds the unit, by virtue of holding it, and not by virtue of any distribution from the protocol. Nothing is paid out, so a valuation of distributions omits it however its discount rate is set; a valuation that prices services from possession, as transactional-demand models of tokens do, need not. This is the same category of thing as the value of holding a bearer instrument outside the banking system, and it is why an asset with no cash flows whatsoever can carry a price. It establishes a benefit of ownership. Whether that benefit becomes monetary use rather than inventory demand depends on others accepting the unit, which is the separate question of Chapter 13: Why Hold the Base Asset?.

The mechanism is standard, and the analogy is to the mechanism only.

That a non-cash-flow service from holding a thing can carry a price no cash-flow model reproduces is the storage-theory account of convenience yield in consumption commodities ([Kaldor 1939]; [Working 1949]): the holder of physical inventory obtains an option against stockout that the holder of a claim on future delivery does not. The analogy drawn here is to that mechanism — a service flow accruing to the bearer rather than to a claimant — and not to the setting. A triad asset is not a storage commodity, it faces no stockout risk in the storage-theory sense, and no magnitude in this thesis derives from the commodity literature.

The distinction the mechanism turns on is easiest to see with a fire extinguisher and a contract for the delivery of one. Both have a price. Both can be bought today, valued, resold, and hedged. Only one of them works during the fire. The premium you pay for owning the extinguisher rather than a delivery claim on one is the amount by which the physical commands more than the discounted contract. No discounted-contract valuation reproduces that number. It is the quantity this thesis means when it says the holder-side flow has no cash flows to discount. In the moment of use, the contract and the extinguisher are not substitutes at any price, and every argument in this section about regime states is an argument about when the market is on fire. An extinguisher is not money, though. The analogy establishes a benefit of ownership; the step from there to monetary use is independent acceptance and a persistent demand to hold, and this section does not supply it.

Gold, which this thesis keeps comparing itself to, is a separate case and should not be filed under storage theory. Its convenience yield in the storage-theory sense is near zero in normal regimes, which is why its lease rates are ordinarily negligible and its forward curve essentially full cost of carry. The early-2025 episode, when tariff-driven physical flows into New York pushed one-month lease rates to multi-year highs and spot into backwardation, is the exception that shows what a storage-theory yield on gold looks like when it briefly exists. What is true of gold is the part that matters here. It has no cash flows, negative carry, and industrial demand far too small to explain its price; every constructible DCF for gold returns a number well below the market. On the standard account that residual is monetary and portfolio demand — what holders pay for a bearer holding that is useful when other arrangements are not — which is the holder-side category described above, arrived at from a different direction.

Regime-Contingent Convenience Yield

The monetary premium available to a triad asset is the holder-side service flow generated by the state-contingency of $\Delta(R)$ — the bearer’s ability to transact, prove, hold, and exit when the substitutes for proofs, courts, and custodians have stopped working — conditioned on credible non-discretion in issuance and on bearer holdability. Those two are not added terms but enabling conditions: the flow is only a monetary service while issuance discipline holds and the unit remains bearer-holdable, and it collapses if either fails. The service accrues by virtue of holding rather than as a distribution, so there is no stream to discount. That is what places it outside a discounted-cash-flow valuation rather than merely at a different discount rate inside one.

It is not the countercyclicality of the fee stream. That is a negative beta on cash flows: real, valuable, and captured exactly by a DCF using the correct stochastic discount factor, which is why it confers no moneyness.

It is also not generated by burns, by collateral, or by fee share. Those produce a cash-flow claim and a collateral lockup (Chapter 13: Why Hold the Base Asset?).

Which conditions and which links this actually implicates.

The consequence of the split is immediate. If the monetary claim rests on the holder-side flow, then it rests on the properties that determine whether a holder can actually use the thing under pressure — and none of those are fee-routing properties. Of the five lemma conditions, only issuance discipline touches the channel at all, and it does so because credible non-discretion is part of the payoff rather than part of the accrual. The other four are conditions for value accrual, and accrual is a DCF quantity. Link 8 then requires a persistent self-custodied constituency capable of bearing loss. The premium itself hangs off link 9: liquidity, neutrality, verifiability, legal holdability, and agency preservation (Chapter 4: First Principles: What a SoV Must Survive). Those are the conditions under which a bearer can transact, prove, hold, and exit when it counts. No burn schedule reaches the premium: a burn operates on the claim, and the premium is not on the claim.

Now discount it honestly.

The hedge has a defect, and it is the same defect the thesis has already documented without drawing the monetary conclusion. The payoff is negatively correlated with the states you fear — that is the point — but the delivery is positively correlated with them. The states in which $\Delta(R)$ spikes are energy interdiction, hardware denial, network filtering, and jurisdictional pressure (Chapter 5: Threat Model, Chapter 17: Layer 0: Verifiable Machines & Energy). Those are precisely the states in which the protocol’s ability to supply privacy, proofs, and compute is impaired. Chapter 34: Objections & Responses half-concedes this and Red Line 13 makes the mechanism falsifiable, but both frame it as a threat to the hinge. It is also a discount on the hedging premium, which is the monetary consequence, and the honest statement of it is: you are being asked to pay a premium for insurance whose underwriter is exposed to the insured event.

Two further deductions from the same discount:

• The slots are occupied. Gold already holds “works when the network does not.” Bitcoin already holds “works when the state does not.” Neither requires a grid at the moment of use — gold requires none at all, and a Bitcoin key survives an outage even where settlement waits. A triad asset needs power, reachable networks, and obtainable reference hardware in order to deliver anything at all, which makes it a hedge against a narrower and more specific band of failure: adversarial conditions severe enough to need proofs and privacy, but not severe enough to take the grid.

• The band may still be the important one. That band — administrative repression, surveillance, synthetic media, platform and compute enclosure, financial repression without collapse — is the one Part I: Context & Claims argues is most likely. Sovereign optionality (Chapter 17: Layer 0: Verifiable Machines & Energy) exists to widen it, and disruption-adjusted VerifyPrice (Chapter 17: Layer 0: Verifiable Machines & Energy) exists to price whether the widening is real.

And do not overclaim it.

The state-contingency argument establishes a mechanism. Non-cash-flow service flows accruing to a bearer are ordinary in asset pricing, and there is nothing exotic in claiming one here. The holder-side flow is nonetheless unsized: nothing in this document estimates how large a regime-contingent convenience yield a triad asset could command, and no honest estimate is available before there is a market in which to observe one. This is an empirical question the thesis has not answered. What it can do is refuse to smuggle the answer in. That refusal is why the chain-strength rating for the store-of-value premium is Medium (conditional), why link 8 asks who bears the asset’s loss, and why the relocated claim is attributed to link 9 rather than to fee accrual. The measurement instrument exists so that the question can be settled rather than asserted: Chapter 26: Extended Telemetry publishes the lending-rate, basis, and wrapper-basis series against the regime-pressure index, and a series flat across regime states is the null result, reported as such.

Collateral: Unit-Elasticity, Float, and Wrong-Way Risk

Condition 3 requires operators to post the native asset as collateral, and the reference designs specify the requirement as a share of capacity value: “10–20% of capacity value” in Chapter 8: The Triad and the Monetary Candidate and a “10–15% collateral requirement” in Design A. That specification has a consequence.

Collateral Unit-Elasticity

Let $K$ be the USD value of deployed capacity, $\chi$ the required collateral ratio, and $P$ the asset price. The number of units that must be locked is

$$N \;=\; \frac{\chi K}{P}.$$

The requirement fixes a value, not a quantity. Collateral demand is therefore unit-elastic in price: a doubling of $P$ halves the units required to satisfy the same obligation.

($\chi$ is used here for the collateral ratio because $\kappa$ already denotes net mechanical gain in Appendix H: Formal Model of Market Realization, Wrapper Flows, and Price Capture and facility capacity share in Chapter 17: Layer 0: Verifiable Machines & Energy.)

It is a level effect on free float, not a slope on demand.

The mechanism immobilizes a fixed dollar quantity of float — a level effect on the free float, not a buy order of any kind, since a lockup places no bid — and the valuation it supports grows only as deployed capacity $K$ grows, not as price grows. Describing it as “structural demand that scales with the network” is true only in the sense that it scales with physical build-out, and physical build-out is slow, capital-rationed, and observable.

And $K$ deflates too.

Capacity value is the replacement cost of deployed infrastructure. It therefore inherits the same deflation exposure as the fee base in Chapter 13: Why Hold the Base Asset?: the same generation of throughput is worth fewer dollars of replacement capital each year. A collateral requirement pinned to $K$ shrinks in dollar terms unless deployed physical capacity grows faster than its unit cost falls. This is the same empirical bet, entering through a second door.

Reflexivity runs in both directions.

For small moves the mechanism is genuine negative feedback, and it is a real design achievement: price rises, fewer units are needed to cover the same $\chi K$, surplus collateral releases into float and meets the buying; price falls, operators must post more units, and they buy. An automatic stabilizer.

For large moves it inverts. Collateral denominated in the asset it insures loses value exactly when slashing risk and operator distress rise — textbook wrong-way risk, and in its dynamic form the familiar margin-spiral or leverage-cycle mechanism. The operator’s instruction in a drawdown is “post more units, at a moment when your existing holdings are worth less and your operating business is stressed.” A common answer is not to post; it is to exit capacity. Exiting reduces $K$, which reduces required collateral, which releases locked units into a falling market. The stabilizer becomes an accelerant, and it does so through the same equation that made it a stabilizer:

$$P \downarrow \;\Rightarrow\; N \uparrow \;\Rightarrow\; \text{operator exit} \;\Rightarrow\; K \downarrow \;\Rightarrow\; N \downarrow \;\Rightarrow\; \text{float} \uparrow \;\Rightarrow\; P \downarrow .$$

The value-leakage mitigations of Chapter 13: Why Hold the Base Asset? do not contemplate this loop. Red Line 15 (Chapter 30: Risk Analysis & Failure Modes) does: it reads on exactly this sequence as a conjunctive condition — a material drawdown, collateral coverage falling below realized slashing exposure, operator exit or forced liquidation, stress-adjusted DVC declining, released collateral raising liquid float, and core SLOs failing to recover — and Chapter 30: Risk Analysis & Failure Modes requires the pure-native, mixed, and native-plus-insurance designs to be stress-tested against it before governance chooses among them. The metric the loop needs, collateral coverage against realized slashing exposure with capacity-withdrawal rates conditioned on drawdown, is the one Red Line 15 publishes.

The design tension, stated plainly.

Collateral must be the native asset in order to create native demand, which is the whole of Condition 3’s monetary contribution. Collateral should be uncorrelated with the risk it insures in order to be credible, which is the whole of prudential collateral design. You cannot have both. Any move toward external collateral — stablecoins, bonded fiat, over-collateralization in an uncorrelated asset — strengthens safety and weakens Condition 3’s monetary contribution by exactly as much. This is not a problem to be solved; it is a trade-off to be chosen deliberately and disclosed.

The magnitude bound.

$\chi K$ is bounded by an accounting identity, and the arithmetic is worth doing even roughly. The following is an order-of-magnitude illustration, not an estimate: the inputs are chosen to be generous rather than defensible, and no claim rests on their precision.

Order-of-magnitude ceiling on collateral lockup. Illustrative arithmetic on assumed capacity values, not a forecast; the point is the exponent, not the digits.

Those are large-cap-equity numbers. They are not monetary-aggregate numbers, and no choice of $\chi$ inside a plausible range changes the exponent. Collateral therefore cannot be the source of moneyness. At best it supports holding demand while operators remain solvent and choose to participate, and it releases in the drawdown that tests it.

The one real contribution, stated in the document’s own notation.

Collateral does do something, and it is worth being precise about what. It creates a holding constituency whose supply is highly price-inelastic — operators cannot sell locked units at any price without exiting the business — which shrinks effective free float and steepens the price response to a given flow. In the Stage C decomposition (Chapter 13: Why Hold the Base Asset?), that is an operation on the liquidity and market-impact state $\Lambda_t$, not on the native monetary impulse $\theta_t$.

Collateral is a slope effect on price impact, not a level effect on price. By immobilizing float (a level effect on free float), it changes how much price moves per unit of flow. It does not establish where price belongs, because it places no bid.

And a slope effect cuts both ways: a steeper response to buying is a steeper response to selling. Calling this “structural demand” overstates it in one direction while concealing the symmetry in the other.

From Utility Demand to Monetary Premium

Many indispensable services (electricity, bandwidth, compute instances, legal services, cloud storage) have recurring demand without being stores of value. The monetary argument requires explaining why this utility becomes monetized savings demand, not just operating expense.

The bridge has eight conditions. The middle five are the Value Capture Lemma restated informally; they are named here in one line each and stated formally at Chapter 13: Why Hold the Base Asset?, not argued twice:

1. Utility demand is not enough. Recurring demand for a service does not automatically create a scarce, holdable asset. Bandwidth is indispensable, but claims on bandwidth do not become money.

2. The asset must be required for fees or settlement: required fee medium, Condition 1.

3. Fees must produce burns, retirement, or staking yield: supply reduction, Condition 2.

4. Operators must post the asset as collateral: Condition 3, whose worth Chapter 13: Why Hold the Base Asset? bounds as a slope effect on price impact, not a valuation floor and not a source of premium.

5. Issuance must follow a schedule fixed ex ante: issuance discipline, Condition 4.

6. Users must not be able to bypass the asset at equal service quality: non-bypassability, Condition 5.

7. Telemetry must prove the loop is working. Fee coverage, burn rates, collateral lockups, and workload demand must be publicly verifiable, not asserted.

8. If any value-capture condition fails, the asset does not even capture its own service value. It becomes infrastructure exposure whose economics accrue to operators or customers rather than to holders. Meeting those five conditions makes service value accrue to the asset; it does not make the asset money, establish stress-deliverable service, or create a loss-bearing holder constituency.

This section is the “utility-token trap” defense. The thesis does not claim that useful things automatically become money; it claims that under specific, testable value-capture conditions, a useful asset accrues the value of its usefulness to its holders: a cash-flow claim and a collateral lockup. Whether anything further, a monetary premium in excess of those, is available is argued separately and on different grounds in Chapter 13: Why Hold the Base Asset?. The Value Capture Lemma formalizes the accrual conditions; the telemetry regime (Chapter 25: Layer 6: Governance & Telemetry) makes them falsifiable.

Why Users Cannot Simply Bypass the Asset

The strongest economic objection to the thesis is simple: “Why can’t AWS, a ZK prover marketplace, or a privacy wallet sell the same service for fiat or stablecoins and bypass the base asset entirely?”

The monetary object at stake in this objection is the base asset (the fee, settlement, and collateral unit), not Work Credits. Work Credits are bypassable service claims by design, and their bypass threatens only service-claim economics, not the monetary thesis. What the thesis needs is that the base asset cannot be bypassed, and the objection is valid unless the protocol enforces native value capture. The required mitigations:

1. Core fees are denominated in the base asset. Provers, routers, and settlement corridors accept only the native asset for protocol-level fees. Fiat or stablecoin payment requires acquiring the asset first, for the seconds it takes to settle: transactional demand, not a savings motive.

2. Collateral must be posted in the base token. Operators cannot participate without holding significant quantities of the asset. Calling this “structural demand” overstates it in one direction while concealing the symmetry in the other (Chapter 13: Why Hold the Base Asset?): it immobilizes a fixed dollar quantity of float, which steepens the price response to flow in both directions rather than establishing where price belongs.

3. Fee retirement is a pro-rata buyback tied to usage. A published share of fees is retired. This returns fee value to holders (Value-Capture Condition 2) and reduces net issuance only when retired fees exceed scheduled issuance; it is a cash-flow mechanism and carries no moneyness inference (Chapter 13: Why Hold the Base Asset?).

4. Priority is sold in the asset, never held. Gold-tier SLAs and priority access during congestion are bought through service contracts paid in the asset, which keeps them a fee channel; holding the asset confers none of them (Chapter 13: Why Hold the Base Asset?). Governance participation requires staking.

5. Settlement paths are natively denominated. Privacy corridors and settlement rails denominate in the base asset; off-ramps exist but are not the default. Whether anyone keeps the unit after settling is the denomination question of Red Line 18, not a property of the rail.

Honest admission: If users can in practice bypass the asset (for example, if most operators accept stablecoins and immediately off-ramp, or if hyperscaler-hosted provers dominate the market and set prices in fiat), then the SoV thesis fails. The system may remain useful infrastructure, but the monetary claim collapses. The telemetry must track this: native-asset fee share, bypass channel volume, and operator off-ramp rates should be visible on the Economic Coverage Board (Chapter 26: Extended Telemetry).

The Incumbent Bypass Channel Is Not Hypothetical

The five mitigations above answer a proposal. They do not answer a precedent, and a precedent exists: stablecoins already settle a large fraction of the value the thesis is targeting, at scale, at near-zero cost, with no native monetary asset anywhere in the loop. Tron and Ethereum carry stablecoin transfer volumes at national-payment-system scale; in the emerging-market currency episodes Chainalysis documents [Chainalysis 2024] (Argentina, Turkey, Nigeria), dollar-stablecoin wallets, not Bitcoin and not Zcash, were the observed instrument of savings flight and censorship-adjacent settlement. That is a decade of revealed preference in exactly the states of the world this thesis calls State 3 (Chapter 29: Adoption Curve & Ecosystem Dynamics), and it is not engaged anywhere in the design.

The stablecoin channel is a live test of Condition 5 that has already been run, and the honest reading is unfavorable in three of four respects:

• Where stablecoins beat the triad: benign and mid-band repression. A stablecoin settles in seconds, costs cents, has no learning curve, and offers practical censorship resistance to the median user, because freezing a Tron address is harder than freezing a bank account even though it is easier than censoring a shielded pool. For payments-motivated flight, the bearer-asset properties this thesis prices (privacy by default, portable proofs, verified compute access) are mostly not on the buyer’s list.

• Where the triad can still differ: the upper band. The stablecoin’s weakness is structural and appears exactly where the thesis’s services begin: it is a claim on a custodian’s reserve and an issuer’s goodwill, it freezes under sanctions enforcement, it carries no proof or compute service, and its censorship resistance is borrowed from its host chain rather than owned. As repression crosses from financial into administrative and epistemic forms (compelled disclosure, platform deplatforming, attestation demands), the stablecoin inherits the substitutability of its issuer, not of cryptography. That is the band in which a triad asset’s $\Delta$ over a stablecoin is nonzero, and Chapter 13: Why Hold the Base Asset? prices the premium as regime-contingent.

• The arithmetic. None of that changes the base fact: for the median settlement need in benign and mid-band states, the incumbent bypass channel is cheaper, faster, and already deployed. The thesis’s five mitigations make bypass harder on this protocol; they do nothing about bypass around it. Red Line 6 is therefore best read as already having an empirical prologue: every stablecoin-settled triad-adjacent payment is a data point that the capturable wedge must be measured against, not assumed above.

The design implication is not despair but precision: the asset’s fee-bearing services must be ones a stablecoin cannot express: private settlement where the stablecoin is a custodial IOU, proofs where the stablecoin is silent, verified compute where the stablecoin has nothing to verify. Where the triad service is interchangeable with a stablecoin payment, Condition 5 should be presumed failed, and the Value Capture Board’s stablecoin-denominated fee share series (Chapter 26: Extended Telemetry) is the instrument that watches it fail or hold.

Co-option as Bypass

The bypass threat is not always a competing product. It can also be institutional co-option: ETFs, treasury companies, margin loans, and regulated custody that deliver exposure to the asset’s price without requiring users to interact with the protocol’s privacy, proof, or settlement rails. If the majority of demand is satisfied by custodial wrappers that bypass the fee-burn-collateral loop, the asset’s price may rise while its monetary thesis weakens. The telemetry must distinguish between custodial exposure (which does not exercise value capture) and protocol-native usage (which does).

Wrapper Dominance Risk

Co-option as bypass is dangerous enough to warrant a named, top-tier risk rather than a sidebar. A protocol asset can succeed as a financial product while failing as money. If ETFs, custodians, treasury companies, broker-dealers, lending desks, and stablecoin wrappers satisfy most demand for exposure, the asset’s price may rise even as native settlement, privacy usage, fee burns, collateral lockups, and non-custodial flows stagnate. This is not a contradiction. It is the signature of wrapper dominance.

Wrapper dominance is dangerous because it turns a monetary network into a reference price. It creates holders without users, exposure without settlement, and liquidity without sovereignty. The asset can moon while the monetary thesis dies.

The returns on an easily imitated technology may accrue to whoever owns its complementary assets rather than to its developers [Teece 1986], and for an open protocol those assets include the custody, brokerage, and distribution that wrappers already own, the same pressure the fork applies from inside the protocol (Chapter 13: Why Hold the Base Asset?).

Wrapper Dominance Ratio (WDR)

Wrapper dominance has a stock component and a flow component, and they must not be divided into one another: exposure is measured at an instant, usage over an interval, so a single ratio would scale with the arbitrary length of the measurement window. WDR is therefore reported as a pair.

Stock form — what share of economic exposure sits in custodial or synthetic form, where $E^{\text{wrapper}}_t$ and $E^{\text{native}}_t$ are exposures at time $t$:

$$\mathrm{CustodialExposureShare}_t = \frac{E^{\text{wrapper}}_t}{E^{\text{wrapper}}_t + E^{\text{native}}_t}$$

Flow form — how activity divides over a stated horizon $h$, where $V_{t-h:t}$ is volume across that window:

$$\mathrm{WrapperActivityRatio}_{t,h} = \frac{V^{\text{wrapper}}_{t-h:t}}{V^{\text{native}}_{t-h:t}}$$

The stock form is bounded in $[0,1]$. The flow form is not: it divides one volume by another, so it is bounded below by zero and unbounded above, and it is undefined when native volume is zero. Both are window-explicit. A rising stock share with a rising activity ratio indicates the asset may be financializing faster than it is becoming money. The horizon $h$ must always be published alongside the flow form.

Inputs to track: ETF/wrapper AUM; custodied balances; exchange balances; wrapped token supply; native fee share; non-custodial settlement volume; shielded/private settlement volume; staking/collateral lockups; fee-burn coverage.

Why wrappers come first, and why that is not reassuring.

The observation that first-generation use of a new medium wears the old medium’s form [McLuhan 1964] (early print looked like manuscripts, early television like radio with pictures) supplies the intellectual lineage of this ratio. It also changes what a rising WDR should be read as. It is not, on its own, evidence of pathology: during a medium transition, consumption of the new asset through the old form is the expected initial condition, not an anomaly. What it means is that the WDR is measuring a phase, and that the thesis’s claim is specifically about whether the transition completes. Wrapper dominance in year three is the manuscript stage of the bearer asset. Wrapper dominance in year twenty is a medium that never finished forming. The failure gate above exists precisely because the frame does not promise completion: first-generation use is always the old content, and the red lines, not the analogy, decide when waiting has become failing.

Gold ran this experiment already.

The financial lineage is a century old, and it is worth naming because it removes any temptation to treat wrapper dominance as a novel crypto pathology. Paper claims on gold grew until they dwarfed the metal: unallocated bullion accounts, gold certificates, and eventually exchange-traded products came to represent exposure-to-gold on a scale that holding-of-gold never matched. The vault holds a fraction of what the paper promises, and the fraction is the finding. A shareholder in a gold ETF owns a claim on a trust that owns gold; a holder of unallocated bullion owns, in the stress-relevant sense, a deposit at whoever holds it. Both are exposure. Neither is a coin in a vault, and on the day it matters (the redemption run, the allocation freeze, the jurisdictional block), the difference between allocated and unallocated is the entire difference. Paper gold did not destroy gold. It demonstrated the exact pattern this ratio watches for: the financial claim outgrowing the bearer object it references, prospering for decades, and leaving the underlying’s monetary character unchanged while the exposure stack did the volume. That is the precedent the WDR tracks, and the reason it is a stock and a flow rather than a single number.

Failure gate: If WDR rises for multiple quarters while native fee share, private settlement, and collateral lockups stagnate, the asset may remain investable but its SoV-as-protocol thesis is weakening. This gate is added to the Red Lines in Chapter 30: Risk Analysis & Failure Modes and tracked on a dedicated Wrapper Dominance Board (Chapter 26: Extended Telemetry).

The Market Realization Plane

The Wrapper Dominance Ratio is a pair — a stock share and a flow ratio — reported side by side and never divided into one another. The stock component measures how much ownership has migrated into custodial and synthetic form; it does not explain the flow mechanics by which those wrappers set prices. That requires one more construct.

Market realization is deliberately not an eighth layer of the stack. Layers 0–6 produce privacy, proofs, compute, settlement, and governance. Market realization produces none of those; it is the conventional financial machinery that represents claims on the resulting monetary object. It is orthogonal to the stack, so it is modelled as a plane around the stack rather than a layer within it.

Market Realization Plane

The set of external institutions and instruments through which claims on the native monetary object are represented, financed, allocated, and priced: exchanges and custody, spot ETFs, corporate treasury vehicles, index products, options and futures, leveraged and inverse ETPs, dealer swaps, prime-broker financing, passive mandates, systematic trend strategies, and rules-based or agentic treasury systems.

The result is two nested loops, and the thesis needs both to be instrumented.

The inner protocol loop determines whether the stack works:

$$\text{Create/Compute} \rightarrow \text{Prove} \rightarrow \text{Settle} \rightarrow \text{Verify}$$

The outer market-realization loop determines how the stack is financially represented:

$$\text{Narrative} \rightarrow \text{Wrapper} \rightarrow \text{Allocate/Lever} \rightarrow \text{Dealer Hedge} \rightarrow \text{Price} \rightarrow \text{Narrative}$$

The inner loop determines native monetary function. The outer loop determines market-price realization. Either loop can strengthen while the other weakens, and the outer loop can run for years on narrative alone.

The plane is not a precaution invented for a young asset. The reference asset of the entire financial system already has one, unacknowledged. When a central bank reads the long end as a message, the reply from market structure is that no unfiltered message exists for the Treasury curve. A measurable share of its demand is generated by benchmark rules and accommodated through leveraged intermediation (Chapter 3: The World Forces New Monetary Primitives). The decomposition that would have to come first—net demand by tenor, in risk units, separated by buyer and by decision rule, with a residual the authors are made to name—is the object this section specifies for the base asset. The difference is only that here it is built in from the start, where for the Treasury curve it would have to be reconstructed after the fact. If the price of the world’s risk-free asset cannot be read without first identifying who is speaking and under what rule, the price of a monetary candidate certainly cannot, and that is the whole of Premise 9.

A Three-Stage Model

The combined thesis can now be stated as three linked but separable processes.

Stage A: regime pressure creates structural need. Let $R_t$ index financial repression, surveillance, synthetic media, and AI concentration. Compute demand is deliberately not a component of $R_t$: it is a demand driver in its own right, entering alongside regime pressure rather than as part of the pressure index, so that $D_t^{\text{triad}} = g(R_t)$ is not partially defined in terms of its own output. Regime pressure generates demand for triad capacity:

$$D_t^{\text{triad}} = g(R_t)$$

This is the causal layer Part I: Context & Claims develops.

Stage B: protocol design converts need into native value. Let $\phi_t \in [0,1]$ measure the effectiveness of the monetary design: required fees, burn share, collateral, issuance discipline, and non-bypassability. Then native captured demand is

$$D_t^{\text{native}} = \phi_t \, D_t^{\text{triad}}$$

As $\phi_t \rightarrow 0$, the system can remain enormously useful while the monetary object fails. This is not the Value Capture Lemma restated as a coefficient: the lemma is an AND-gate on five conditions, while $\phi_t$ is an empirical capture fraction those conditions constrain. The lemma says partial capture is possible only when the gate is open; $\phi_t$ measures how much of the triad demand actually flows through once it is.

Stage C: market structure realizes native value as a price path. Observed price depends not only on native demand but on aggregate exposure flows and the liquidity available to absorb them:

$$\Delta \ln P_t = \theta_t + I(Q_t, \Lambda_t) + \eta_t$$

where $\theta_t$ is the non-flow fundamental or native monetary drift (defined to exclude flow effects, so that all flow impact enters once, through the $I(Q_t, \Lambda_t)$ term, rather than twice), $Q_t$ is aggregate exposure demand (a flow over the interval $[t-1, t]$), $\Lambda_t$ is the liquidity and market-impact state, and $\eta_t$ is residual. Aggregate demand decomposes by source:

$$Q_t = Q_t^{\text{native}} + Q_t^{\text{allocation}} + Q_t^{\text{levered}} + Q_t^{\text{dealer}} + Q_t^{\text{trend}}$$

Only the first term is monetary evidence. The remaining four can dominate the price for extended periods, in either direction. Appendix H: Formal Model of Market Realization, Wrapper Flows, and Price Capture develops the flow mechanics formally (holder flow elasticity, the net mechanical gain coefficient, the recycling boundary, market impact, and volatility drag), and Chapter 26: Extended Telemetry defines the telemetry that makes the plane observable.

Why a protocol should care about external market structure. A designer might object that this is someone else’s problem. It is not. External wrappers affect treasury behavior, collateral demand, governance concentration, liquidity-provider incentives, public understanding, security-budget expectations, regulatory pressure, and the price that the protocol’s own participants use when making decisions. The protocol should not manage its price. It must nonetheless instrument the structures through which its monetary claims are represented, for the same reason it publishes VerifyPrice: unmeasured dependencies are where theses go to die quietly.

The Numeraire Is Not Fixed

Everything above measures the price path in units of account whose own value is assumed constant. That assumption is doing more work than it appears to.

Chapter 13: Why Hold the Base Asset? establishes that price is not evidence of monetary adoption. The point here is adjacent and independent: even a price series that is informative about the numerator can mislead through the denominator. A rising quotation may report an appreciating asset, a depreciating unit of account, or any combination of the two, and the series alone cannot distinguish them.

Numeraire-Dependence

The property that a measured price path is jointly determined by the asset and by the unit in which it is quoted, such that the same series can support opposite conclusions about real command over resources depending on the denominator chosen.

For this thesis the consequence is a measurement requirement rather than a philosophical observation. The Market Realization Plane exists to prevent financialization from being narrated as adoption. A plane instrumented only in the sovereign unit of account is blind to the case where wrapper-led appreciation and currency depreciation move together—which is precisely the regime Chapter 3: The World Forces New Monetary Primitives argues is likely.

Requirement.

The core market-realization series—the Wrapper Dominance Ratio (Chapter 13: Why Hold the Base Asset?), the Wrapper–Native Growth Gap, and the native fee, burn, collateral, and settlement series—should be published in at least one non-fiat numeraire alongside the fiat series. A reference basket of energy, compute, shelter, and gold is sufficient and has the advantage that each component is a thing the holder might actually need. Where the two numeraires disagree in sign, the disagreement is the finding and should be surfaced rather than reconciled.

A sharper definition of the objective.

The thesis has so far spoken of purchasing power, which inherits the numeraire problem it is trying to escape. The more precise statement of what a store of value is for:

Wealth is durable, transferable command over necessary capacity under adversarial conditions.

Each term is load-bearing. Durable excludes claims that survive only while an issuer chooses to honor them. Transferable excludes capacity that cannot be moved or bequeathed. Necessary capacity names the denominator explicitly—energy, shelter, compute, mobility, time—rather than leaving it implicit in a currency. Under adversarial conditions is the requirement of Chapter 4: First Principles: What a SoV Must Survive and the reason Chapter 4: First Principles: What a SoV Must Survive is a design constraint rather than a preference. This is the definition the rest of the document should be read against.

Worked example: structure does not determine behavior.

A useful illustration, because it is easy to get backwards. An asset can be genuinely bearer-oriented, scarce, censorship-resistant, and independently settleable at the protocol layer, and simultaneously trade as leveraged technology beta at the wrapper layer—held through exchange-traded products, pledged as collateral, sized by volatility-targeting mandates, and sold first in a de-grossing episode. Both descriptions are accurate. They describe different planes.

The error in either direction is the same error. Concluding from correlated selloffs that the protocol properties are illusory mistakes the plane for the stack. Concluding from the protocol properties that the price will behave defensively mistakes the stack for the plane. Appendix H: Formal Model of Market Realization, Wrapper Flows, and Price Capture supplies the machinery for keeping them apart, and Chapter 26: Extended Telemetry the telemetry.

A related precision, since the language is routinely abused: a proof-of-work asset is energy-linked, not energy-backed. Its issuance and security consume energy; it is not redeemable for a fixed quantity of electricity, and no holder has a claim on a joule. The distinction matters because a genuine claim on capacity—a generation asset, a storage system, a Facility Capacity Receipt—has a payoff structure that an energy-linked bearer asset does not, and conflating them overstates the latter’s hedging properties.

Technology success is not incumbent success.

One further reading of the same distinction, which the thesis has stated elsewhere in monetary terms and which generalizes. A technology can transform an economy while destroying the equity, debt, and tokens of everyone who financed its first build-out; railways and long-haul fiber are the standard cases. This is Chapter 13: Why Hold the Base Asset? pointed at infrastructure rather than at protocols: the social return and the return to the first capital structure are different quantities, and the second is the one an investor actually receives.

Denomination: The Function the Thesis Has Never Measured

Ask a merchant in Buenos Aires what a thing costs and the answer comes in dollars, whatever ends up crossing the counter. That is the whole of the unit-of-account question, and it is the one monetary function the other instruments do not measure.

Chapter 13: Why Hold the Base Asset? treats the numeraire as a measurement hazard: the thesis’s own series are quoted in a unit whose value moves, so they must also be published in a non-fiat one. This subsection points the same word the other way, and asks a monetary question rather than a hygiene one — is anyone choosing to quote in this one?

Denomination is the strongest of the monetary functions and the one nobody instruments.

A store of value can be abandoned in an afternoon: the holder sells and is out. A unit of account cannot. It is welded into contracts whose counterparties would all have to move at once, and each of whom eats the basis if they move alone. That mutual dependence is what makes denomination sticky: it is a coordination device rather than a portfolio choice, and coordination devices are hard to acquire and correspondingly hard to lose [Doepke & Schneider 2017]. Assets that achieve denomination rarely lose it. Assets that achieve only holding lose it routinely.

The thesis measures fees, burns, collateral, settlement, holder cohorts, wrapper exposure, capacity, reachability, and verification cost. It does not measure whether a single contract anywhere is priced in the unit. That is the largest gap in a five-family measurement programme, and it is a gap on the monetary side rather than the service side.

The trap, stated first, because the obvious metric is worthless.

A naive denomination share would read one hundred per cent on the day the network launches and would mean nothing. Chapter 8: The Triad and the Monetary Candidate specifies that all triad services are priced in the base token; Condition 1 of the Value Capture Lemma requires it. Denomination that the protocol mandates is a routing rule — the same routing rule already stated, already conceded to be a design commitment rather than a finding, and already excluded from carrying monetary weight by Chapter 13: Why Hold the Base Asset?. Counting it as evidence of adoption would be the tokenomics inference in a new costume.

Everything of interest is therefore in the complement.

Free-Choice Denomination Share

Let $\mathcal{C}_{\text{free}}$ be the set of contracts in which the parties were not required by protocol rule to express price terms in the base asset — forward and term capacity purchases, SLA agreements above the mandated fee, bilateral prover–buyer contracts, corridor quotes, over-the-counter blocks, service retainers, employment and vendor agreements among operators, and any obligation denominated between counterparties rather than by the protocol.

Free-choice denomination share is the fraction of $\mathcal{C}_{\text{free}}$ whose price terms are written in the base asset, reported by contract count, by notional, by tenor bucket, and by counterparty class.

The mandated complement — fees, required collateral postings, protocol-set tier pricing — is published separately and is never added to it. It is a design commitment and reads as one.

Quoting and settling are different acts, and the crypto record turns on the difference.

A contract has two units and they need not agree. It can be quoted in dollars and settled in the asset; quoted in the asset and settled in the asset; or, rarely, quoted in the asset and settled in dollars. The second and third are unit-of-account observations, because the unit that fixes the obligation is the unit of account whatever instrument discharges it. The first — quoted in fiat, settled in the asset — is a payment-rail observation, and it is the configuration essentially all crypto commerce has actually taken.

This is worth stating at full strength because it is the strongest evidence against this thesis’s own expectations. Bitcoin is the most successful new store of value of the last century on the measures this thesis uses—credible scarcity, verification cost, censorship resistance, and capitalization—and after seventeen years it denominates almost nothing. Bitcoin-native businesses quote in dollars and settle in bitcoin. Salaries described as paid in bitcoin are, with few exceptions, dollar salaries settled in bitcoin. Whatever monetary premium bitcoin carries, it did not come with denomination attached and has not produced it since.

Two readings are available and the thesis should not pretend the choice is obvious. Either denomination is not necessary for moneyness — in which case this subsection measures something real but not load-bearing — or bitcoin’s moneyness is incomplete along a specific, measurable axis. This document takes the second reading and concedes it is contestable.

The one structural asymmetry that makes the second reading defensible.

Bitcoin has no native economy of goods. The things bought with it are produced by an economy that prices in dollars, so a bitcoin quote imports basis risk against every input the seller must pay for, and no coordination is available to remove it. A triad protocol is different in one respect that is not a matter of degree: the goods are produced by the system that issues the unit. A proof, a verified inference, a corridor settlement, and a unit of delivered verified capacity are priced, produced, collateralized, and settled inside the same accounting perimeter. A prover paid in the unit, posting collateral in the unit, buying capacity priced in the unit, has a naturally two-sided position and faces the basis risk that keeps bitcoin quotes in dollars only on the legs that reach outside.

That is the whole of the structural argument, and it is narrow. It says a service protocol has a coordination path to denomination that a pure bearer asset does not. It does not say the path will be taken.

The walled-garden test, before a critic applies it.

Internal denomination proves nothing on its own, and there are unflattering precedents. Airline miles are denominated, transferable, and priced against a schedule the issuer sets; in-game currencies denominate large and genuinely productive internal economies. None is money, and each would score highly on a share computed only over contracts internal to its own economy. The discriminating cut is therefore not free choice alone but where the counterparty stands:

• Tier I — inside contracts. Both legs are protocol services. Free choice, but the parties are already inside the accounting perimeter. This is where in-game currencies score one hundred per cent.

• Tier II — boundary contracts. One leg is a protocol service, the other is not: an enterprise buying verified inference, an operator’s power contract, a hardware purchase.

• Tier III — outside contracts. Neither leg is a protocol service, and the unit was chosen anyway.

The monetary content rises strictly from I to III, the three are published separately and never blended, and Tier I is reported as context rather than as evidence. A protocol scoring highly on Tier I alone has built a company scrip with excellent telemetry.

The incumbent quote.

At the boundary the share does not start from an empty field. Compute already has a list price, and on the international lists it is in dollars, Chinese providers’ included. Google Cloud, for one, states that the prices on its VM instance price list are in U.S. dollars [Google Cloud 2026]. Among Chinese providers, Alibaba Cloud’s international Model Studio list prices its Qwen models in US dollars per million tokens, its China (Beijing) deployments included [Alibaba Cloud 2026], and DeepSeek’s English-language API price list quotes in dollars [DeepSeek 2026]. A Tier II contract for compute written in the unit therefore displaces a dollar quote the buyer already has, and that dollar quote is the baseline against which the free-choice share is read.

The volatility objection, which is the serious one.

Nothing prices in a volatile unit if it can avoid it, and this is the standard and correct explanation for the bitcoin record. It bounds where denomination can appear, and the bound is useful precisely because it makes the prediction specific rather than directional. Denomination should appear first at short tenor, where the parties’ exposure to unit variance over the contract’s life is small, and first in two-sided positions, where a counterparty’s costs and revenues are in the same unit and the variance nets. It should appear last, or never, in long-dated one-sided contracts, which is exactly where a naive story would expect a strong monetary asset to show up first.

That is a shape prediction across the tenor and sidedness buckets, and a shape is harder to fake than a level. A denomination share that rose uniformly across all buckets would be evidence of subsidy or mandate rather than adoption, and should be read that way.

And it couples to the previous mechanism.

The reason volatility is prohibitive is not variance itself but the cost of carrying and hedging the exposure that variance creates over a contract’s life. That cost falls when positions in the unit can be financed cheaply and pledged without investigation — which is what Chapter 13: Why Hold the Base Asset? argues cheap universal verification supplies. The two mechanisms are not parallel additions to the same list. Information-insensitivity lowers the carrying cost of denomination, and denomination is what converts an accepted asset into a coordination device. Acceptance without denomination is a settlement rail; denomination without acceptance does not occur.

An ordering caveat the thesis should carry rather than discover.

The currency-substitution literature finds a consistent sequence when populations abandon a domestic unit: asset substitution first, unit of account second, means of payment last. Savings dollarize years before prices do. If that ordering holds here, free-choice denomination is a confirming indicator of monetary adoption rather than a leading one on the macro path, and this subsection should not be read as promising an early warning of anything.

The claim it does support is narrower and survives the caveat: denomination is leading with respect to the protocol’s own contract layer, because Tier I and Tier II contracts exist from Phase I onward and can be counted long before any external population is substituting anything. What is early here is the measurement, not the phenomenon.

Instrument.

Publish quarterly on the Value Capture Board (Chapter 26: Extended Telemetry), under the custody and reproducibility terms of Red Line 14 — the party collecting the fee may not classify the contracts:

• Free-choice denomination share, by contract count and by notional, split across Tiers I/II/III, and never aggregated with the mandated complement.

• Quote/settle matrix. The four-cell table of quoting unit against settling unit, by notional. The fiat-quoted, natively-settled cell is the payment-rail null and is reported as the headline denominator, not hidden in a total.

• Tenor and sidedness decomposition. Share by tenor bucket and by whether the counterparty’s position is one- or two-sided in the unit, so the shape prediction above can fail visibly.

• Subsidy disclosure. Any fee rebate, tier privilege, or incentive conditioned on native denomination, with the share recomputed excluding subsidized contracts. A purchased quote is not a chosen one.

• Redenomination events. Contracts that switch units in either direction at renewal, which is the cleanest available revealed preference and the series a critic will ask for first.

The falsifier. This mechanism is made falsifiable as Red Line 18 (Chapter 30: Risk Analysis & Failure Modes), in two conditions with different severities: outsiders declining to reckon in the unit weakens the thesis, and protocol participants declining to reckon in it on unmandated contracts kills it.

What this subsection does not claim.

It does not claim denomination is necessary for moneyness — bitcoin is the standing counterexample and it is named above rather than managed. It does not claim the protocol’s endogenous service economy makes denomination likely, only that it makes a coordination path available that a pure bearer asset lacks. It does not raise any rating in Chapter 8: The Triad and the Monetary Candidate: a new instrument on link 9 is an instrument, not a finding. And it does not promise an early warning on the macro path, for the ordering reason stated above.

What it does supply is an answer to the question the other instruments cannot answer: what would be visible, at Phase I, that distinguishes this from every service token that ever shipped? The answer is a contract nobody was required to write in the unit, written in the unit anyway, with a counterparty outside the perimeter, at a tenor long enough to matter, without a rebate.

Once work can be verified, the question is what to build on top of it. The triad produces three capacities, and Work Credits turn capacity into claims. But a claim is a design decision, not an inevitability, and the decision has consequences that outlive whoever made it. Pick the wrong instrument for a real buyer, and the buyer quietly routes around you: a treasury that needs a two-year hedge will not buy a perpetual index, and an AI lab hedging inference cost will not buy privacy credits it cannot redeem. The failure mode is not loud. Nobody announces they are leaving; the service just never gets the volume, and the instruments sit on the shelf with impeccable specifications and no counterparty.

That is why this chapter walks the design space rather than picking from it. Monetary candidacy remains confined to the base asset and subject to the Triad Coherence Test (Chapter 8: The Triad and the Monetary Candidate); what follows is the inventory of everything else you can build, organized by which triad leg the claim draws on, and by who — concretely — would ever hold it.

The legacy labels are kept because they name real demand clusters, but read them as lenses, not products. “ZK Money” is not a coin; it is the observation that privacy and proofs are usually bought together. “AI Money” is not a token; it is the observation that compute is bought forward, in size, by parties who fear shortage. Each lens describes a buyer, and each buyer implies a different instrument.

The “ZK Money” Analytical Lens

The legacy “ZK Money” label groups service instruments that primarily reference Privacy + Proofs. In practice this means claims on shielded settlement capacity — corridor LP positions, privacy-rail credits — and claims on zero-knowledge proof capacity such as SNARK/STARK service tiers.

What these share is a particular pairing: bearer-like, censorship-resistant settlement rights, bundled with attestations of compliant behavior. Neither half is worth much alone. Settlement rights without attestations are an offshore account with better cryptography; attestations without settlement rights are an audit trail nobody can act on. The value is in the bundle, which is why regulated actors — who need privacy from counterparties and provability toward supervisors simultaneously — are the natural buyer.

One transaction to fix the idea. A corporate treasurer operating under an emergent capital-control regime needs to move payroll to overseas staff without exposing vendor rates to competitors or the transaction graph to the local banking authority, and must still satisfy the parent company’s auditors at quarter-end. She buys corridor credits that settle shielded, and each settlement emits a PIDL receipt her auditors can verify without a viewing key. That single purchase — privacy toward the state, disclosure toward the auditor, both on purpose — is what “ZK Money” was always pointing at. Treasuries under repression, regulated actors needing simultaneous privacy and compliance, and individuals wanting cash-like digital assets are variations on the same shape.

The “AI Money” Analytical Lens

The legacy “AI Money” label groups service instruments that primarily reference Compute + Proofs: claims on verified FLOPs, futures on model-specific inference capacity with proof guarantees, and equity-like positions in proof factories whose output is standardized, verified compute.

The common thread is that compute is the one triad leg bought forward. Nobody pre-pays for privacy next year; plenty of parties pre-pay for inference next year. That asymmetry is the entire commercial logic of the lens: it exists because shortage risk, not usage, is what generates a term structure.

One transaction. An AI lab training a frontier model has a contractual delivery window for a customer deployment and has watched spot GPU prices move 40% in a quarter. It buys futures on verified inference for the specific model hash it will serve, with proofs of correct execution attached, locking both price and correctness for the delivery window. The hedge is only as good as the verification — an unverified forward on compute is just a promise from whoever sold it — which is why the claims are typed to workload and proof tier rather than to “compute” in the abstract. AI labs and application builders hedging compute shortage, and investors who believe AI demand outlives any particular model cycle, are the same buyer at different horizons.

Hybrid Instruments

Hybrids reference all three legs at once, and they exist because real obligations rarely arrive one leg at a time.

A triad basket is an index-like instrument backed by diversified Work Credits across privacy, proof, and compute workloads — for an allocator who wants exposure to the stack’s aggregate throughput without forming a view on which leg tightens first. A corridor-linked compute claim couples private settlement rights with AI inference capacity: the holder can pay for and receive verified inference without revealing who is asking, which is the shape an agent acting for a pseudonymous principal actually needs. An agent service treasury takes the same idea and makes the holder the agent — an on-chain system holding combinations of typed proof, settlement, and compute claims to fund its own operation, buying its own compute the way a factory buys its own electricity.

One transaction, and the one worth watching. A software agent under contract to serve a customer’s inference workload for a quarter holds its own treasury of corridor-linked compute claims, draws them down as it serves, and settles with its customer over privacy rails — no human in the loop, and every drawdown receipted. If that transaction ever runs at scale, the instruments holding it up are hybrids by construction. Chapter 7: The Delegation Economy: Who Buys Verification models the buyer this transaction implies, and Chapter 7: The Delegation Economy: Who Buys Verification states why an agent treasury must be classified by principal before it counts as a holder.

The key design constraint is always the same, and it is the chapter’s answer to the question it opened with: claims must stay tightly coupled to verifiable work and capacity, not to governance mood or marketing narrative. The moment a claim’s value can be moved by a vote or a slogan, it has stopped being a service instrument and started being a governance lottery — and the buyer who needed the hedge is already gone.

ZK is the accounting engine of this stack. If privacy is the right to speak softly and compute is the ability to think loudly, zero-knowledge proofs are the receipts that make both negotiable. They turn “trust me” into “verify me” without exposing the underlying state. A world that routes value and decisions through proofs rather than paperwork is, in effect, a zk-economy.

A zk-economy is not just “more proofs.” It is day-to-day life running on attestations: every payment, inference, bridge, and audit backed by succinct evidence that any party can check.

Why Open Hardware Is a Precondition for the ZK-Economy

A sound proof does not need an honest prover. That is what soundness means: a machine that lies about the computation produces a proof that fails to verify, whoever built the machine. What a dishonest machine can still do is everything soundness does not cover.

Today’s largest ZK systems run on stacks that are almost entirely closed: proprietary GPUs, opaque microcode, black-box TEEs, firmware that can be updated silently overnight. A government-mandated “secure enclave” with a secret backdoor can exfiltrate witnesses from supposedly private circuits; the proof verifies and the privacy is gone. A trusted setup whose toxic waste survived on someone’s hardware lets its holder forge proofs outright—a failure of the ceremony rather than of the prover, but one that lives on machines all the same. And every claim that reaches past the circuit—that this camera captured this scene, that this plant burned this energy, that this prover won this slot fairly—is only as good as the device that measured it.

Closed hardware leaves math-grade correctness wrapped around vendor-grade trust.

A genuine zk-economy therefore begins one layer below the circuits, with verifiable machines (Layer 0). At least part of the proving path must be open from the RTL up through the software stack.

Perfect certainty about every chip in circulation is not available, but the stack can move to a regime where:

“This proof came from this class of machine, built from this design, and it would have been extraordinarily expensive to tamper with it without being caught.”

That is enough to make “trust the hardware” a falsifiable claim instead of a sacrament.

Concretely, a zk-economy that wants to support the service markets described by the “ZK Money” and “AI Money” lenses needs three things from Layer 0:

• Open proving paths: For canonical circuits, at least one proving stack must be open from RTL through firmware and prover binaries.

• Sampled, attestable devices: Lots can be sampled with verifiable randomness, imaged, and subjected to structured tests.

• Hardware-level SLOs for witness confidentiality and physical claims: Profiles with weak sampling or poor audit history should be priced differently.

How This Opens a ZK + AI Economy

The same logic extends to AI. If proofs are the receipts of the digital order, AI is the industrial plant that consumes energy and data and emits capabilities.

The zk + AI economy is built on three interacting strata:

1. AI blockchains (“model chains”): Duplex-style and Ambient-style [Ambient 2024] PoUW systems treat model training and inference as work functions. Work Credits sold against these workloads remain typed verified-compute service claims. Pass [Pass 2026] formalizes the regime in which token rewards subsidize inference below compute cost (“Duplexia”); the fee-incidence bound of Chapter 13: Why Hold the Base Asset? says such a subsidy cannot be funded from fees and is therefore paid from issuance, which is the design’s cost of capital, not evidence of demand.

2. ZK blockchains (“proof chains”): Nockchain-style [Nockchain 2025] zk-PoW systems coordinate global prover markets and issue typed claims on future proof capacity.

3. Privacy rails as connective tissue: BTC$\leftrightarrow$XMR swaps (BTC$\leftrightarrow$shielded-ZEC gated on the work in Chapter 23: Layer 5: Value & Settlement), shielded pools, and private rollups let capital move without custody.

The daily-life version looks almost boring:

• Your phone proves you paid a toll without revealing your route.

• A DAO buys inference on a model chain; a proof chain clears the resulting proofs; payment moves over privacy rails.

• An exchange settles cross-chain obligations with batches of zk-proof-backed settlement receipts.

• An insurer prices climate risk from sensor networks whose readings are baked into proofs from open hardware profiles.

Underneath the surface, three demand curves reinforce one another:

1. Proof demand grows as systems move from “trusted unless flagged” to “untrusted unless proven.”

2. Verified compute demand grows as AI saturates workflows.

3. Privacy demand grows as financial repression and surveillance tighten.

These are three economic flywheels that, if the thesis is right, will spin up over time:

Proof flywheel.
More systems demand proofs $\to$ prover markets deepen $\to$ VerifyPrice falls or stabilizes $\to$ more systems can afford to demand proofs.

Compute flywheel.
More AI in workflows $\to$ more willingness to pay for verified compute $\to$ more Work Credits sold against AI capacity $\to$ more capital available to fund model chains.

Privacy flywheel.
More repression and surveillance $\to$ more demand for lawful private rails $\to$ deeper anonymity sets and corridor liquidity $\to$ cheaper and safer private settlement $\to$ more users adopt privacy by default.

Open hardware is what keeps these flywheels from collapsing into a handful of “trust me” platforms. zk-PoW is what coordinates proof work into a measurable, meterable commodity. AI-PoUW is what turns model work into an asset class whose revenues are natively tied to triad usage. Privacy rails are what keep capital flowing between them without recentering custody.

Put in one line:

ZK makes computation checkable by anyone. Open hardware keeps the witness private and the physical claims honest. AI gives us something valuable to spend that checking on. zk-PoW and AI-PoUW are the mechanisms that weld the three into an economy rather than a collection of clever demos.

Running this framework is not scoring a product. It is auditing a supply chain that runs in two directions at once — upward from machines into money, and outward from one balance sheet to whoever is standing behind it. The operator/investor checklist in Part V spans the whole stack; this chapter is the monetary lens, which evaluates whether the base asset is a credible store-of-value candidate while keeping the service and evidence instruments beneath it analytically separate.

Every question below is a way of asking one of two things: can this thing deliver what it promises under the conditions that make it valuable? and who absorbs the loss when it cannot? The first is the question a buyer asks; the second is the question an underwriter asks. A store of value has to survive both, which is why the checklist reads as though written by two people.

One distinction does more work than any other here, so it belongs at the front rather than buried as a note: legibility is not resilience. A facility can be perfectly transparent about being catastrophically fragile — publish every receipt, pass every audit, display its full telemetry, and still fail on the first stressed day. The reverse is rarer but real: a robust operation whose interior is opaque. Every measurement regime, this thesis’s included, is biased toward the first thing it can see; dashboards reward the visible. So the checklist deliberately separates the questions that ask can the substrate be seen from the ones that ask can what we see withstand anything, and treats a high score on the first set as establishing nothing at all about the second. Items 10 and 11 exist as two items for exactly this reason. Passing the legibility questions makes an asset auditable; only the resilience questions can make it a store of value.

For a candidate base asset $X$, ask:

1. What triad services does it route value from?

   • Exactly which Privacy, Proof, and Compute flows pay fees, burn supply, or require base-asset collateral?

   • Are those workloads canonical and well-specified?

   • Are the associated Work Credits reported as typed service claims rather than counted as monetary holdings?

2. How is base-asset issuance constrained?

   • Is issuance formulaic and transparent, and distinct from Work Credit issuance against DVC?

   • Can governance mint outside of those rules? Under what constraints?

3. Can anyone verify the service linkage?

   • Are VerifyPrice and workload telemetry public?

   • Can a third party recompute DVC and sample the proofs, settlements, and Work Credit claims that justify fee and collateral activity?

4. How does it behave under repression?

   • If real yields are $-300$ bps for 3 years, what happens to demand for $X$?

   • If on-/off-ramps are throttled, can $X$ still be acquired, held, and spent?

5. Is privacy lawful by design?

   • Are there clean paths for voluntary disclosure that do not reintroduce custody or KYC chokepoints?

   • Are the receipts (PIDL) expressive enough for auditors?

6. What is the duration profile?

   • Does $X$ promise fixed nominal coupons (bond-like) or variable participation in fee flows (equity/commodity-like)?

   • Can a sovereign push its real return negative by fiat?

   • If $X$ is duration-neutral as money, what separate instrument, if any, is supposed to warehouse the construction interval of the physical assets the stack requires? Conflating the two is a completeness failure, not a feature (Chapter 3: The World Forces New Monetary Primitives, Chapter 34: Objections & Responses).

7. Who can be locked out?

   • Is access to $X$ gated by one jurisdiction, cloud, or app store?

   • Do Layer-0/1/2 assumptions create hidden chokepoints?

8. Can users bypass the asset?

   • Can users buy equivalent Privacy, Proofs, or Compute service for fiat, stablecoins, or direct cloud contracts without touching the asset?

   • Are fees actually paid in the native asset, or do operators accept and immediately off-ramp alternatives?

   • Are burns and collateral lockups material, or negligible relative to total supply?

9. Can institutions legally and operationally hold it?

   • Is custody support available from regulated custodians?

   • Is the legal classification clear enough for treasury or fund mandates?

   • Is liquidity deep enough for institutional-scale positions?

   • Does governance redirect value away from holders?

10. Is the physical infrastructure behind it legible?

    • Are Facility Capacity Receipts (Chapter 17: Layer 0: Verifiable Machines & Energy) available and independently verifiable for a material share of active capacity?

    • Is Physical VerifyPrice (Chapter 22: Layer 4: Truth & Work) within published bounds, or does verifying the facility take months of trust-the-vendor diligence?

    • Is supply concentrated in a small number of hyperscalers, closed TEEs, or single-jurisdiction facilities (Homestead Ratio / Enclosure Risk Flag, Chapter 5: Threat Model)?

11. Is that infrastructure resilient, or merely visible?

    • What is network sovereign optionality, $\mathcal{O}_s^{\text{net}}$ (Chapter 17: Layer 0: Verifiable Machines & Energy), and is it published with its component vector and weights rather than as a bare scalar?

    • What share of VerifyPrice-tracked capacity sits in jurisdictions with an active curtailment, rationing, or interconnection-denial regime (Chapter 5: Threat Model)? Is Red Line 13 approaching?

    • Is the headline verification cost a benign-state figure, or is disruption-adjusted VerifyPrice published alongside it with stated disruption probabilities (Chapter 17: Layer 0: Verifiable Machines & Energy)?

    • Does the resilience premium demonstrably lower disruption-adjusted cost, or is it capital misallocation with a security narrative attached (Chapter 17: Layer 0: Verifiable Machines & Energy)?

    • Is issuance bounded by stressed Delivered Verified Capacity, with the active binding constraints named, or by nameplate power and installed hardware (Chapter 17: Layer 0: Verifiable Machines & Energy)?

    This is the pair to the previous question, and an operator will try to collapse them. The prior question asks whether the substrate can be seen; this one asks whether what we see can withstand anything — the distinction opened at the head of this chapter, and the reason Red Lines 10 and 13 are separate.

12. Is demand wrapped, or protocol-native?

    • What share of economic exposure sits in ETFs, treasury companies, and custodial wrappers versus protocol-native settlement (Wrapper Dominance Ratio, Chapter 13: Why Hold the Base Asset?)?

    • Is price rising while native fee share, private settlement volume, and collateral lockups stagnate?

13. Does anyone hold it through stress?

    • Is there a persistent, self-custodied, loss-bearing cohort that adds through drawdowns (net of units it spends on the service during stress, which count for it), or is native demand acquired just in time, sold on receipt, leveraged, or wrapped (Native Monetary Buyer Map, Chapter 26: Extended Telemetry)?

    • Does holding in advance beat Bitcoin plus conversion on the day, for any workload and stress state the access experiment has run (Chapter 13: Why Hold the Base Asset?)?

    • Is the persistent bid a rule that absorbs less risk as prices fall, or leverage that leaves on a margin call (Chapter 3: The World Forces New Monetary Primitives)? A large bid of either kind is not an anchor.

    • Where holders are agents, who is the principal, and can a person still revoke the agent through the protocol? Does the cohort move as one policy (Chapter 26: Extended Telemetry)?

14. Is anything monetary happening, or only accrual?

    • Pledgeability. Do lenders disagree less about haircuts on verifiable positions than on opaque comparables of the same volatility, and re-converge faster after a shock (Chapter 13: Why Hold the Base Asset?)?

    • Denomination. Does anyone write contracts in the unit that nobody required them to write in it, and do the protocol’s own participants denominate their short-tenor obligations in it (Chapter 13: Why Hold the Base Asset?)?

    • Holder-side service. Does the price of borrowing or parting with the asset rise in the pressure corridor above the pre-registered minimum increment (Chapter 13: Why Hold the Base Asset?), and does a held balance beat Bitcoin converted on the day (Chapter 13: Why Hold the Base Asset?)?

    This is the only question on the list that reads on moneyness itself. Every other question asks whether the conditions for it hold. Fees, burns, and collateral cannot answer it, because what they establish is a cash-flow claim and a collateral lockup (Chapter 13: Why Hold the Base Asset?).

15. Does it equip holders, or manage them?

    • What share of flows are non-custodial and require no global identity (Chapter 4: First Principles: What a SoV Must Survive)?

    • Does disclosure stay selective (predicates) rather than converging into a reconstructable dossier (Chapter 27: Legal, Policy, and Jurisdictional Posture)?

A base asset that scores well on these questions remains a next-generation SoV candidate:

• It is backed by verifiable work, not by decree.

• Its value is rooted in capacities that a digital civilization must keep buying: privacy, proofs, and compute.

• It is measurable under stress via telemetry, not defended by rhetoric.

Comparison: Traditional Hard Assets vs. the Base-Asset Candidate

For context, it is useful to compare how gold and silver—the canonical “old-world” stores of value—score against the same framework:

SoV comparison: traditional hard assets vs. the conditional triad base-asset candidate. Work Credits are excluded because they are typed service claims.

Gold and silver excel on Lindy (millennia of history), simplicity (no software, no network), and zero counterparty risk in physical form. They remain rational holdings during the transition window while the triad stack matures. Healthy VerifyPrice, VerifyReach, VerifySettle, DVC, and native-buyer telemetry can establish distinctive digital capabilities; they do not establish that the base asset is superior money or promote Work Credits into savings instruments.

The thesis does not claim gold is obsolete. It claims only that a base asset may earn a distinct premium for preserving agency across specific digital failure modes—financial repression under surveillance, synthetic media, and compute enclosure—if all nine links hold. The bridge is still load-bearing; the candidate remains under test.

The rest of the thesis will shift back to the stack angle (Layers 0–6) and the telemetry angle (VerifyPrice/Reach/Settle, DVC, buyer quality, decentralization, governance). The monetary question stays in the background: every design choice is judged by whether the base asset can preserve agency and satisfy the nine-link chain, while Work Credits stay what Chapter 12: Work Credits: Reserved Service Claims established them to be — service instruments — under every regime.