privacy · proofs · compute
v3.5 · checksummed

4. Value Capture Is Not Monetary Premium

v3.5
Cite this section

Copy/paste (plain text):

Jason St George. "4. Value Capture Is Not Monetary Premium" in AfterFiat: The Load-Bearing Thesis. Version v3.5. /v/3.5/brief/read/value-capture-is-not-monetary-premium/

Value Capture Is Not Monetary Premium

The protocol can route service demand into a base asset through native fees, retirement of supply, operator collateral, and disciplined issuance. These mechanisms matter, but they answer where economic value goes, not whether the asset is money.

Value Capture Channels

In the reference design, service demand accrues to the base asset through five channels, and the design relies on all five holding together:

  1. the asset is required for core fees at equivalent service quality;

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

  3. capacity providers must post the asset as collateral;

  4. gross issuance follows a schedule fixed ex ante, not governance fiat; and

  5. users cannot obtain equivalent service through a bypass channel that avoids the asset.

Each is necessary to this design’s route to accrual and none to value capture in general: a buyback funded by fees in another unit, pro-rata distribution, or native fees without native collateral capture value by other routes. None is sufficient for monetary premium.

A competitive service market can still support a transaction fee: the fee is a wedge on turnover rather than a claim on operator profit. But the sustainable fee is bounded by what the protocol is differentially worth. If cpc_p is protocol delivery cost, cbc_b the best bypass cost, ff the fee, and Δ\Delta the buyer’s willingness to pay for checkability, neutrality, non-discretion, and exit, routing requires

cp+f−Δ≤cb,f≤Δ−(cp−cb).c_p+f-\Delta\leq c_b, \qquad f\leq\Delta-(c_p-c_b).

The protocol begins with a cost handicap because proving and redundancy consume real resources. Bypass is therefore a magnitude, not a switch. The commercial question is whether the high-Δ\Delta tail—cross-jurisdictional, pseudonymous, politically exposed, or audit-critical users—is large enough to support a fee after the verification premium is paid. That tail is two populations, not one: supervised counterparties who need evidence, and unsuable counterparties who need absence, and each one’s requirement is the other’s disqualifier through the shared anonymity set. Revenue is not additive across them. A fork runs the same technology, so against a fork the bound is coordination value alone.

Even when the five conditions hold, they produce two familiar valuation objects: a claim on the fee stream and a balance-sheet lockup of required collateral. A burn is economically a buyback. Collateral is a lockup that holds while operators stay solvent and choose to participate; it places no bid, and it is not a premium. Neither mechanism makes Visa, a pipeline, or a clearinghouse into money, and neither does so here.

Protocol value and market price are different machines

Native value capture is service use →\rightarrow fees →\rightarrow burns, collateral, and operator demand. Price capture is demand for exposure arriving through funds, custodians, treasury companies, futures, options, swaps, leverage, passive allocation, or dealer hedging. Either can move without the other. Therefore

price appreciation⇏monetary adoption,monetary adoption⇏immediate price appreciation.\begin{align*} \text{price appreciation}&\nRightarrow\text{monetary adoption},\\ \text{monetary adoption}&\nRightarrow\text{immediate price appreciation}. \end{align*}

VerifyFlow interprets price formation; it does not replace VerifyPrice, VerifyReach, VerifySettle, capacity telemetry, or native-holder measurement. Price is an output to explain, never evidence to cite by itself.

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