The Instruments

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, Complete Edition, Chapter 9: Privacy as Private Money^†, Complete Edition, Chapter 10: Proofs as Attestation Money^†, Complete Edition, Chapter 11: Compute Through the “AI Money” Lens^†).

   One mechanism for persistence is named in Chapter 6: 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 (Complete Edition, Chapter 22: Layer 4: Truth & Work^†).

   Delegation supplies a standing pressure in this direction, since an agent cannot delegate what it cannot specify (Chapter 6: 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$ (Complete Edition, Chapter 22: Layer 4: Truth & Work^†, Complete Edition, 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 17: 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 (Complete Edition, 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 (Complete Edition, Chapter 22: Layer 4: Truth & Work^†, Complete Edition, 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 (Complete Edition, Chapter 22: Layer 4: Truth & Work^†, Complete Edition, 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 7: Why Not Something Already Here?).

   Severed if: users obtain equivalent triad capacity through hyperscalers, stablecoins, or custodial APIs without the asset—Red Line 6 (Chapter 17: Risk Analysis & Failure Modes, Complete Edition, 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 (Complete Edition, 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 6: 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 14: Why a Base Asset Behind These Could Become Money, Complete Edition, 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 15: The Three Monetary Mechanisms), denomination (Chapter 15: The Three Monetary Mechanisms), and the state-contingent holder-side service flow (Chapter 15: The Three Monetary Mechanisms), 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 7: Why Not Something Already Here?).

   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 (Complete Edition, 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 (Complete Edition, Chapter 5: Threat Model^†, Complete Edition, 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 15: The Three Monetary Mechanisms), reckoning in the unit (Chapter 15: The Three Monetary Mechanisms), and the state-contingency of differential value (Chapter 15: The Three Monetary Mechanisms). 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 (Complete Edition, 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 18: Kardashev Labs: Build and Measure), Work Credits remain service claims however well they perform (Complete Edition, Chapter 12: Work Credits: Reserved Service Claims^†), and the architecture comparison leaves open whether the three services share one asset at all (Complete Edition, Chapter 8: The Triad and the Monetary Candidate^†). The links answer four separate questions (Chapter 9: 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 9: 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 16: Stages, Phases and Macro States, Chapter 18: 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 (Complete Edition, 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 7: Why Not Something Already Here?); 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 7: Why Not Something Already Here?)

  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 11: Layers of the Cypherpunk Stack), and the telemetry and the red lines make every link falsifiable (Complete Edition, Chapter 26: Extended Telemetry^†, Chapter 17: 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 6: 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 (Complete Edition, Chapter 26: Extended Telemetry^†).

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 (Complete Edition, 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 15: The Three Monetary Mechanisms 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 7: Why Not Something Already Here? 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; Complete Edition, 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 9: 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 Complete Edition, 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 (Complete Edition, 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 Complete Edition, 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 Complete Edition, 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 7: Why Not Something Already Here?). 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.

Whether there is a fee to route belongs to the case for holding. First, the instrument the designs keep apart from the monetary candidate: Work Credits, typed claims on service. This chapter defines them, separates them from the receipts that prove work was done, and asks what would have to be true for one to become money.

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 (Complete Edition, 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 (Complete Edition, 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 Complete Edition, 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.

Why a Work Credit is not savings is physical, not rhetorical: exposed to basis, location, hardware, expiry and delivery, it is a warehouse receipt with a date on it, and a savings instrument has to survive the day the warehouse is the problem (Complete Edition, Chapter 12: Work Credits: Reserved Service Claims^†).

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 Complete Edition, 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 (Complete Edition, 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 15: The Three Monetary Mechanisms).