§25. Operator & Investor Checklist

Jason St George. "§25. Operator & Investor Checklist" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v2.0. /v/2.0/read/part-v/25-operator-investor-checklist/

Operator & Investor Checklist

The last piece of Layer 6 is a practical checklist: how builders, operators, and allocators decide whether this stack qualifies as a next-generation store of value.

Triad Supply: Privacy, Proofs, Compute

For each leg of the triad:

Privacy:

• Are there live, non-custodial privacy corridors with measurable anonymity sets?

• Are shielded pools growing in depth and churn?

• Are lawful-privacy patterns (viewing keys + receipts) actually used?

Proofs:

• Is there robust supply of proofs for canonical workloads?

• Are VerifyPrice SLOs met consistently?

• Is proof production diversified across hardware profiles and geographies?

Compute:

• Are meaningful amounts of useful compute being proven?

• Is there a liquid market for Work Credits?

• Are triad workloads tied to real-world demand?

Value Capture & Anti-Bypass

The most important questions for evaluating whether the SoV thesis holds:

• Can users buy equivalent Privacy, Proofs, or Compute service without the native asset?

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

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

• Is there a visible bypass channel (hyperscaler-hosted provers, stablecoin-denominated services) that captures most of the demand without flowing through the asset?

• Does governance have the power to redirect value away from holders (e.g., by eliminating burns, inflating supply, or changing fee routing)?

• Is the Wrapper Dominance Ratio (§10: Work Credits: Energy-Anchored Claims) rising while native fee share, private settlement, and collateral lockups stagnate?

• Is price being cited as evidence of monetary adoption in place of native fee, burn, collateral, and settlement series (§10: Work Credits: Energy-Anchored Claims)?

If the answer to any of these is “yes,” the system may be useful infrastructure but the SoV thesis is weakened or falsified.

Institutional Holdability

• Is custody support available from regulated custodians?

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

• Is the asset auditable enough for institutional reporting requirements?

• Is liquidity deep enough for institutional-scale positions?

• Is there a valuation policy that allocators can apply (fee-flow models, comparable frameworks)?

Holdability is a virtue with a bill attached (§4: Threat Model). Every question above should therefore be paired with its market-realization counterweight:

• Does wrapper growth seed native usage, or substitute for it? Is the Wrapper–Native Growth Gap (§23: Extended Telemetry) persistently positive?

• What share of supply sits under custodial control (CCR), and how concentrated is that custody?

• Is delta-adjusted synthetic exposure (SER) large relative to liquid free float?

• Do daily-reset leveraged products exist on the asset, and what is their net mechanical gain $\kappa$ and Wrapper Recycling Ratio?

• Is exposure concentrated in a small number of dealers or counterparties, and has the hedge-instrument mix shifted from physical to swaps to options?

• Is demand governed by a small number of common rebalancing policies (Policy Concentration Ratio)?

Stack Health: Layers 0–6

Layer 0.
Documented hardware profiles? Open hardware participation? Visible incident reports? Facility Capacity Receipts available and independently verifiable (§14: Layer 0: Verifiable Machines & Energy)? Physical VerifyPrice within bounds (§19: Layer 4: Truth & Work)?

Layer 1.
VerifyReach shows resilient connectivity? Alternative transports exist?

Layer 2.
Clients distributed via multiple channels? Reproducible and signed binaries?

Layer 3.
Pseudonymous credentials integrated? Actors can prove rights without doxxing? Non-custodial usage share and dossier-minimization score visible (§3: First Principles: What a SoV Must Survive)?

Layer 4.
Canonical workloads documented? VerifyPrice within SLOs? Proof production decentralized?

Layer 5.
Non-custodial corridors healthy and diversified? Refund safety enforced?

Layer 6.
Public dashboards? Documented governance processes? Recent incident reports?

Market Realization Plane.
Is VerifyFlow published at all (§23: Extended Telemetry)? Are wrapper inventory, creations/redemptions, flow elasticity, concentration, and the Wrapper–Native Growth Gap visible? Is the market-realization stress harness (§23: Extended Telemetry) run and reported? Remember that this plane sits around the stack, not inside it: its failure does not break the protocol, but its opacity breaks price interpretation.

Telemetry Honesty

Telemetry itself can be gamed. Checklist for honesty:

• Open data. Are raw metrics public? Can independent teams reproduce Verify* metrics?

• Client diversity. Metrics gathered by multiple operators?

• Incentive alignment. Any incentive to under-report problems?

• History. Historical series for metrics, or only recent snapshots?

Red Flags and Failure Patterns

Finally, some patterns that should trigger skepticism:

Closed hardware monoculture.
One TEE, one vendor, no sampling, no open profiles $\to$ Layer-0 cliff.

Opaque bridges.
“Magic multisig” bridges with no proofs, unclear jurisdiction, and no incident history $\to$ not settlement rails, just custodial risk.

Foundation fiat.
Major parameter or policy changes via blog post, with no on-chain trace, no telemetry, and no incident report $\to$ governance capture.

Zombie corridors.
Privacy rails that haven’t moved meaningful volume in months but still appear in marketing. Anonymity sets that are effectively dead.

Proof theater.
Lots of “ZK” branding but no public VerifyPrice metrics, no canonical workloads, no commodity verifiers.

Governance theater.
Token votes with single-digit participation deciding fundamental parameters; no constraints; no SLOs.

Price as proof.
Marketing that cites market capitalization, wrapper AUM, product launches, or trailing returns as evidence that the monetary thesis is working, while native fee, burn, collateral, and settlement series are absent or flat $\to$ financialization narrated as adoption (§10: Work Credits: Energy-Anchored Claims).

Any one of these is survivable in the short run; taken together, they say:

“This is not a triad-backed money system; it is a platform dressed as one.”

A system with no telemetry is untrustworthy. A system with one vendor’s telemetry is fragile. A system with multi-source, reproducible telemetry has a shot at being money.

Part V closes the governance loop:

• It treats SLOs and dashboards as the constitution.

• It makes Verify* telemetry the lifeblood of neutrality and repression-resilience.

• It frames law and politics as constraints to be engineered around, not as deities to be appeased.

• It gives builders and allocators a practical checklist for deciding whether a system’s “store of value” claim is mathematically grounded or just well-typeset.

With Layer 6 in place, the stack has all three angles: Money (triad as SoV), Stack (Layers 0–6), and Telemetry (Verify* keeping it honest). Part VI can now focus on dynamics (adoption curves, risk, and implementation sketches): how this thing actually gets built, traded, attacked, and, if it works, quietly becomes part of what the world calls “money.”

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