§6. The Triad as Monetary Base

Jason St George. "§6. The Triad as Monetary Base" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v1.4. /v/1.4/read/part-ii/6-triad-as-monetary-base/

§6. 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.

The claim is conditional: Privacy, Proofs, and Compute can support store-of-value instruments if verification remains cheap, privacy settlement remains usable, useful-work markets avoid capture, and protocol design converts recurring triad demand into scarce, non-bypassable asset value.

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 (you can check whether you have privacy, a valid proof, or a verified FLOP without trusting a platform).

The monetary base in this frame is not “the token” but the networked capacity to deliver Privacy, Proofs, and Compute under adversarial conditions. Tokens, credits, and instruments are just ways of slicing claims on that capacity.

A few distinctions help:

• Base vs. wrappers: The base is “how much verifiable Privacy/Proofs/Compute per unit time this stack can deliver at target SLOs.” Wrappers are things like Work Credits, corridor tokens, and staking positions that slice this capacity into transferable claims.

• 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?”

From a monetary perspective, the key property is that the world must keep buying the triad’s utility:

• 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 replaces all money, but that it behaves like a reserve asset: a base layer of verifiable capacity that other instruments reference, hedge with, or settle into. Private Money and AI Money are just two lenses on how that base is held and used.

The Conditional Chain, End to End

§0 promised that the thesis would establish its claim through a conditional chain rather than an assertion. That chain is defended link by link across six Parts, 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 → standardized work → receipts → markets → fee flows → a scarce asset (only under non-bypassable accrual) → 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 we name the weak ones 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 (§2, §7, §8, §9).

   Severed if: the demand turns out to be cyclical discretionary spend rather than structural necessity.

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 (§19).

   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$ (§19, Appendix A).

   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 (§27).

4. Receipts enable markets. Cheaply checkable receipts 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 (§19, §21).

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

5. 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 (§19, §23).

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

6. 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 five conditions: required fee medium, meaningful burn or retirement, staked collateral, disciplined issuance, and no bypass channel delivering equivalent service without touching the asset (§6.2, §6.3).

   Severed if: users obtain equivalent triad capacity through hyperscalers, stablecoins, or custodial APIs without the asset — Red Line 6 (§27, §25).

7. A scarce, captured 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 (§31, §13, §3).

   Severed if: any of the nine store-of-value requirements fails, or telemetry showing them is captured (Red Line 4).

The chain says nothing about price. Completing all seven links would establish that the asset deserves monetary premium. 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 (§6, Market-Price Non-Equivalence). The chain is measured on the protocol boards; price is interpreted separately through VerifyFlow (§23) and never cited as evidence for the chain.

The chain rests on something beneath it. Links 2 through 5 all consume bulk power, and link 3 — the hinge — is denominated in real resources on reference hardware. That makes the chain dependent on conditions that states partly set: energy availability and pricing, and the obtainability of unprivileged reference hardware (§4.6, §14.10). The substrate exposure is aggregated as sovereign optionality (§14.9) and made falsifiable by Red Line 13. The chain is not suspended in mathematics; it is bolted to a grid.

Where the chain is weakest. Honest accounting rather than uniform confidence:

The two medium links are engineering and market-structure risk, not logical gaps.

The rest of this section defends links 6 and 7, which are where the monetary argument actually lives. Parts III and IV defend links 2 through 5 by building the stack that supplies them. Parts V and VI make every link falsifiable.

6.1 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, we must answer four questions without poetry:

1. What exactly is the asset?
2. What do users pay in?
3. How does holding capture value?
4. Why doesn’t value leak entirely to operators?

This section answers those questions by committing to three reference designs—not infinite agnosticism, but concrete instruments that can be evaluated.

Question 1: What is the asset?

The triad stack can issue several kinds of holdable instruments:

The primary SoV candidate is the base token: the unit in which fees are paid, burns occur, and collateral is posted. Work Credits and LP positions are secondary instruments whose value derives from the base.

A terminology contract. This thesis uses two words that are easily confused, and the distinction carries real analytical weight:

• Native instruments are protocol-internal claims: Work Credits, staking and LP positions, corridor claims, capacity vouchers. They touch the protocol. Using them exercises fees, burns, or collateral.
• 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:

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: for leverage $L$ on an underlying with drift $\mu$ and volatility $\sigma$, compound growth is approximately $g_L \approx L\mu - L^2\sigma^2/2$, and the variance penalty grows with the square of leverage. At sufficiently high volatility such a product destroys capital even when the underlying has a positive average return.

Question 2: What do users pay in?

All triad services are priced in the base token:

• Proofs: Pay base tokens to provers; portion burned.
• Privacy settlement: Pay base tokens for corridor fees; portion burned.
• Verified compute: Pay base tokens for inference/MatMul; portion burned.
• Staking/collateral: Provers, routers, and LPs must lock base tokens to participate.

This creates structural demand: every use of the triad requires acquiring the base token.

Question 3: How does holding capture value?

Value accrues to holders through four channels:

┌─────────────────────────────────────────────────────────────────┐
│                    VALUE CAPTURE LOOP                           │
├─────────────────────────────────────────────────────────────────┤
│  Triad Demand (proofs, privacy, compute)                        │
│           ↓                                                     │
│  Users acquire base tokens to pay fees                          │
│           ↓                                                     │
│  Fees paid → Split: [Burn %] + [Staker %] + [Operator %]        │
│           ↓                          ↓              ↓           │
│  Burns reduce supply    Stakers earn yield   Operators paid     │
│           ↓                          ↓                          │
│  Scarcity increases     Holding earns income                    │
│           ↓                          ↓                          │
│  Price appreciation ←────────────────┘                          │
└─────────────────────────────────────────────────────────────────┘

Concrete parameters (reference design):

Why this creates SoV behavior:

• Demand is structural: AI, commerce, and compliance create ongoing need for triad services.
• Supply is bounded: Issuance is capped; burns reduce circulating supply.
• Holding is rewarded: Stakers earn yield; appreciation accrues to all holders via burns.
• Velocity is limited: Collateral requirements lock significant supply.

Question 4: Why doesn’t value leak entirely to operators?

The “utility token trap” occurs when operators (provers, LPs, routers) capture all economic value while token holders merely provide exit liquidity.

The stack avoids this through:

Net effect: At steady state, fee burns ≥ new issuance, so total supply is flat or declining. Holders benefit from both yield (if staked) and appreciation (via burns).

Value Capture Lemma

Demand for Privacy, Proofs, and Compute creates store-of-value premium for the native asset only if five conditions hold simultaneously:

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: issuance is capped by schedule, capacity, or both—not by 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.

If any condition fails, the system may be useful infrastructure but not a store-of-value asset. This lemma is the central bridge between ‘these capacities are indispensable’ and ‘therefore a specific asset earns monetary premium.’

The lemma has a frequently-missed converse. It states the conditions under which native demand accrues economically to the asset. It does not state that movements in the asset’s observed market price are caused by that native 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:

price appreciation does not imply monetary adoption

monetary adoption does not imply 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, §23).

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 → native fees → burns, collateral lockup, and operator demand → scarcity and monetary premium. It is governed by the Value Capture Lemma above.

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.

Only the top-left cell is monetary validation. 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.

Three Reference Designs

To make the thesis testable, we commit 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) or capacity-linked ceiling.
• Fee medium: All triad services priced in base token.
• Burns: 40% of fees permanently destroyed.
• 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: Minted against verified work (FERs + proofs); no fixed cap.
• Redemption: Burnable for priority access to proofs/compute/settlement at SLA-guaranteed rates.
• Expiry: Credits decay or expire after N years to prevent 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?

The thesis is compatible with all three, but Design A (Base Token as SoV) is the primary reference design because:

1. It is closest to the BTC model that has demonstrated SoV behavior.
2. Fee burns create clear, measurable scarcity.
3. Staking and collateral create structural demand beyond speculation.
4. VerifyPrice and telemetry make the value linkage auditable.

Design B is useful for enterprises but is explicitly not pitched as a SoV. Design C is viable but adds complexity (index construction, rebalancing).

The rest of Part II assumes Design A as the default when discussing “the asset” or “Work Credits as SoV.” Where Design B semantics apply (vouchers, hedging), we will note it explicitly.

6.2 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:

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. Every use of the triad must flow through the base token. If operators accept fiat directly, the asset is optional.

3. Fees must produce burns, retirement, or staking yield. Fee revenue must reduce circulating supply or compensate holders, not merely pay operators.

4. Operators must post the asset as collateral. Provers, routers, and LPs must lock the asset to participate, creating structural demand beyond fee payment.

5. Issuance must be capped or capacity-constrained. New supply cannot expand by governance decree; it must track real, verified capacity.

6. Users must not be able to bypass the asset at equal service quality. If AWS, a ZK prover marketplace, or a stablecoin-based privacy wallet can sell equivalent triad capacity for fiat, the native asset becomes unnecessary.

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 condition fails, the asset is infrastructure exposure, not money. It may still be useful and valuable, but it does not earn a store-of-value premium distinct from its service value.

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 can earn monetary premium.

6.3 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 Work Credits entirely?’

The objection is valid unless the protocol enforces native value capture. The required mitigations:

1. Core fees are denominated in the base token. Provers, routers, and settlement corridors accept only the native asset for protocol-level fees. Fiat or stablecoin payment requires acquiring the asset first.

2. Collateral must be posted in the base token. Operators cannot participate without holding significant quantities of the asset, creating structural demand beyond speculation.

3. Burns create scarcity tied to usage. A meaningful share of fees is permanently destroyed. Higher triad usage means lower circulating supply.

4. SLA priority requires the asset. Gold-tier SLAs, governance participation, and priority access during congestion require holding or staking the asset.

5. Settlement paths are natively denominated. Privacy corridors and settlement rails denominate in the base token; off-ramps exist but are not the default.

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 (§23).

Sidebar: 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).

6.4 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.

Definition: 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}}$

Both are bounded and 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.

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 §27 and tracked on a dedicated Wrapper Dominance Board (§23).

6.5 The Market Realization Plane

The Wrapper Dominance Ratio measures a stock: 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 we model it as a plane around the stack rather than a layer within it.

Definition: 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:

Create/Compute → Prove → Settle → Verify

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

Narrative → Wrapper → Allocate/Lever → Dealer Hedge → Price → 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.

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, AI concentration, and compute demand. Regime pressure generates demand for triad capacity, $D_t^{\text{triad}} = g(R_t)$. This is the causal layer developed in Part I.

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, non-bypassability). Then native captured demand is $D_t^{\text{native}} = \phi_t D_t^{\text{triad}}$. As $\phi_t \to 0$, the system can remain enormously useful while the monetary object fails. This is the Value Capture Lemma restated as a coefficient.

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 fundamental or native monetary impulse, $Q_t$ is aggregate exposure demand, $\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 develops the flow mechanics formally — holder flow elasticity, the net mechanical gain coefficient, the recycling boundary, market impact, and volatility drag — and §23 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.

Tip: hover a heading to reveal its permalink symbol for copying.