§14. Layer 0: Verifiable Machines & Energy

Jason St George. "§14. Layer 0: Verifiable Machines & Energy" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v1.9. /v/1.9/read/part-iii/14-layer-0/

Layer 0: Verifiable Machines & Energy

Layer 0 is where cryptography stops being metaphor and touches matter.

PoW had an implicit Layer 0: silicon, power, and warehouses hashing in the dark. The trust assumption was: “ASICs will do what the SHA-256 spec says.” In practice that meant: “we trust the vendor, the fab, the firmware, and the power company, and we hope no one has a better ASIC they haven’t told us about.”

Those assumptions were tolerable when the artifact was a hash nobody outside the system consumed: a compromised fab could win more blocks than it should, but no third party was relying on the output for anything. They stop being tolerable when the puzzle mints receipts that other people act on, and when proofs and verified compute become monetary primitives. Giving the work an external buyer raises the Layer 0 requirement rather than lowering it.

Why Layer 0 Is a Monetary Question

Gold worked as money because geology is hard to fake at scale. Bitcoin worked because hashing cost was hard to fake at scale. In both cases, the monetary story rested on silent assumptions: rocks behave; fabs behave; physics behaves.

The triad inherits those assumptions and tightens them:

• Privacy is only as real as the devices that hold keys and speak on the wire.

• Proofs are only as real as the machines that generate entropy, execute circuits, and sign receipts.

• Compute is only as real as the GPUs/ASICs that claim to have run workloads.

If those machines are opaque, remotely steerable, or quietly biased, Work Credits degrade into theater:

• A compromised RNG can turn “unpredictable leader election” into a slow rug-pull.

• A backdoored prover can leak witnesses or mishandle private inputs, even though it cannot emit invalid proofs accepted by a sound verifier unless the proof system or implementation is broken.

• A mandated TEE can become a kill switch for entire clusters of provers and routers.

All of this math still runs on matter.

Every proof, every encrypted wallet, every verified FLOP ultimately lives on a sliver of doped silicon that almost nobody is allowed to audit. Today’s “trusted hardware” stack is a daisy chain of NDAs: closed-source EDA tools, proprietary IP blocks, opaque PDKs, black-box fabs, sealed packaging, vendor-run attestation services.

Layer 0 Precision

Layer 0 does not make cryptographic proofs sound; soundness comes from the proof system and verifier. Layer 0 makes claims about the physical world credible: which machine produced a receipt, whether inputs were captured honestly, whether randomness was biased, whether witnesses were protected, and whether energy/capacity claims are real. A sound proof system should not require trusting the prover’s hardware for proof correctness. Layer 0 becomes essential when the claim includes physical capture, machine identity, energy use, witness confidentiality, randomness quality, side-channel resistance, or fair participation in useful-work markets.

From a monetary standpoint, Layer 0 asks:

“Can we treat triad capacity as collateral if we don’t know what the machines are really doing?”

The answer is “no.” Triad services delivered by machines we cannot interrogate cannot support a credible base-asset monetary candidate; they are IOUs on a hardware cartel plus the jurisdictions that regulate it.

So the mandate of Layer 0 is:

Translate “trust the vendor” into “trust these verifiable claims about the machine and its power,” or don’t pretend it’s money.

Design Goals and Non-Goals

Layer 0 has to be ambitious enough to matter and humble enough not to LARP full supply-chain omniscience.

Goals

1. Verifiability over purity. We aim for checkable claims about machines, not for metaphysical purity. Open RTL where we can; structured sampling where we cannot.

2. Common knowledge of security. Different actors should be able to agree on facts about hardware profiles, even if they disagree about policy.

3. Energy anchoring, not energy worship. Power use should be measurable enough that “Work Credit per joule” is meaningful.

4. Degradability under attack. When assumptions fail, the system should degrade visibly: telemetry spikes, profiles are deprecated, Work Credits tied to broken profiles are risk-flagged and may face prospective ineligibility for new collateral uses.

5. Composable exports. Layer 0 should emit artifacts that higher layers can consume mechanically.

Non-goals

1. Perfect trustlessness. We will not “solve” global hardware and supply chains.

2. Single-vendor dependence. Heterogeneity is a feature, not a bug.

3. Total hardware transparency on day one. Political and commercial realities exist.

4. Magical protection against all side-channels. We assign budgets to attack surfaces.

Hardware as Base Reality for Work Credits

In Part II, Work Credits were defined as claims on standardized units of triad work (privacy settlement, proofs, verified compute) anchored to energy and VerifyPrice.

Layer 0 defines the hardware profile that each Work Credit type rests on. For a canonical workload $W$, a hardware profile $H$ might specify:

• Chip family and stepping.

• Microarchitectural features (e.g., presence of certain accelerators or TEEs).

• RNG source and test regimen.

• Power metering and thermal envelope.

• Known limitations (e.g., “avoids TEE X due to backdoor Y; uses open core Z instead”).

When a Work Credit of type $(W, T)$ is minted, the receipt can say:

“This unit of work was performed on hardware profile $H$ under conditions $C$, with proof $P$ and VerifyPrice statistics $V$.”

Monetarily, that matters because:

• Profiling makes hardware risk priced instead of hidden. Credits from “sketchy profile $H'$” can trade at a discount.

• It lets different actors pick their risk tolerance: some will only hold Work Credits linked to fully open cores; others will accept mixed profiles in exchange for lower cost or higher performance.

Layer 0’s job is not to tell everyone what risk to take; it is to make the risk legible and instrumentable.

The Layer 0 Feasibility Ladder

A common objection to Layer 0 is: “Open silicon and sampled supply chains sound like moonshots. What can we actually do this decade given real-world fabs, opaque GPU stacks, and geopolitical constraints?”

The answer is a graded trust ladder. Layer 0 does not require perfection on day one; it requires measurable progress and falsifiable claims at each grade. Higher grades provide stronger guarantees; lower grades are acceptable for less sensitive workloads, with telemetry that detects when you’re relying on weaker grades.

Layer 0 Feasibility Ladder

Key principles:

1. Grades are explicit. Every hardware profile is tagged with its Layer 0 grade. Work Credits, VerifyPrice dashboards, and SLA tiers reference these grades so users know what trust assumptions they’re accepting.

2. Telemetry detects reliance on weaker grades. If 80% of proving capacity is L0-A (vendor-attested) and only 5% is L0-C (partial open), that concentration is visible in dashboards. Users can decide whether to hold Work Credits tied to such a distribution.

3. Higher grades earn lower risk premiums. Markets should price Work Credits from L0-D profiles more favorably than L0-A profiles, creating economic gravity toward openness as it becomes available.

4. Migration paths are first-class. When L0-B or L0-C options become viable, there are documented procedures to migrate workloads off L0-A profiles without catastrophic downtime.

5. Failure modes are bounded. If a specific grade is compromised (e.g., a TEE used in L0-A profiles is broken), the impact is contained to that grade. Higher-grade capacity continues to function; affected Work Credits are risk-flagged, receive collateral haircuts, or face prospective ineligibility.

Policy Hooks: Economic Treatment by Grade

The following table specifies how each L0 grade affects Work Credit eligibility, pricing, and collateral treatment. These are reference parameters; implementations may adjust within bounds.

Interpretation:

• Issuance weight: Higher grades earn more WC per unit of verified work, incentivizing investment in open hardware.

• Collateral haircut: When WC are used as collateral (e.g., for staking, LP positions, or DeFi), lower grades may face haircuts. L0-A collateral is discounted if a single vendor/TEE dominates.

• VerifyPrice tier: Dashboards stratify measurements by L0 grade. If most verification runs on L0-A hardware, this is flagged as concentration risk.

• Issuance cap (L0-A only): To prevent over-reliance on vendor-attested hardware, L0-A profiles are capped at 60% of new issuance. Excess work at L0-A earns priority for future slots but not extra tokens.

Quantitative Thresholds (Reference Design)

These thresholds are governance parameters, adjustable via protocol upgrade with supermajority. Changes are announced 90 days in advance and visible in dashboards.

Pragmatic Starting Point (L0-A)

Today’s stack can achieve L0-A by combining:

• Multi-vendor diversity: No single chip family or TEE dominates more than $X$% of critical capacity.

• Third-party attestation audits: Independent labs verify that attestation claims match device behavior.

• Reproducible firmware and benchmarks: All prover/router firmware is built reproducibly; benchmark results are publicly verifiable.

• Side-channel measurement: Known side-channel leakage is measured and published as a “leakage budget” per profile.

• Cryptographic agility: Profiles document which primitives can be upgraded via firmware vs. require hardware swap.

This is not trustless. It is trust-bounded and measured. The residual trust is explicit: “We trust these vendors, these auditors, and this sampling methodology, and here is the evidence.”

The Path Forward

• L0-A $\to$ L0-B: Fund independent lot-sampling programs. Publish inspection results. Build statistical models of detection confidence.

• L0-B $\to$ L0-C: Invest in open RISC-V cores, open RNG designs, open firmware stacks. Wrap proprietary accelerators with proof interfaces so their internal logic doesn’t need to be trusted.

• L0-C $\to$ L0-D: Support open PDK initiatives. Diversify fab sources across jurisdictions. Build ecosystem gravity so open designs become economically competitive.

Why This Prevents “Layer 0 Is Impossible, Therefore Thesis Fails”

The thesis does not require L0-D today. It requires:

1. Clear grading of what trust assumptions each profile carries.

2. Telemetry that makes those assumptions visible.

3. Economic and technical paths toward stronger grades over time.

4. Failure modes that degrade visibly, not silently.

If these four conditions hold, Layer 0 becomes a progress metric rather than a moonshot prerequisite. The stack can operate today at L0-A while building toward L0-C/D, and users can decide what risk they’re willing to accept at each stage.

Concrete Components of Layer 0

Layer 0 is not a single device. It is a bundle of practices and mechanisms that give higher layers a surface to stand on.

Open Designs Where Possible

The gold standard is open cores and toolchains: open RTL or microarchitectures for CPUs/accelerators, open PDKs where geopolitical conditions allow, and reproducible build infrastructure.

Where open options exist, they are first-class citizens in hardware profiles. On the margin, this creates economic gravity: as open hardware matures, Work Credits tied to open profiles should command a lower risk premium.

Attested Randomness and Entropy

Randomness is the hidden spine of consensus and proofs. A biased RNG can leak signing keys, predict leader election, and make PoUW “fairness” an illusion.

Layer 0 requires:

• Hardware RNG designs that are documented and testable.

• Attested entropy tests: periodic statistical test suites.

• Blended randomness: mixing hardware entropy with VRFs, commit-reveal, and cross-machine aggregation.

Attestation Without Priesthood

Modern hardware ecosystems push TEEs and attestation as the answer to everything. Used naively, they simply move “trust the vendor” into “trust the vendor’s signing key.”

Layer 0’s posture:

• TEEs and hardware attestation are useful tools, not root of trust.

• Attestations should be wrapped and sampled, not taken as gospel.

• Devices emit local attestations wrapped in SNARKs or STARKs where possible.

Lot Sampling and Destructive Audits

Because we cannot open every chip, Layer 0 leans on lot sampling:

• For each hardware profile, a fraction of units are randomly selected for deep inspection: decapping, imaging, side-channel probing.

• Results are published as part of the profile’s dossier.

• A protocol-level Layer 0 Assurance Fund (2% of fee revenue) finances sampling.

This is how Layer 0 turns “we hope the vendor is honest” into:

“We have inspected a statistically relevant sample of this profile, and here are the findings and residual risks.”

Sampling Economics and Sufficiency

Critics will ask: “How much sampling is enough? Who pays? What confidence do we actually get?”

Sample rate model (reference design):

Sample rate model by profile criticality.

Statistical sufficiency:

For a profile with $N$ deployed units, sampling $n$ units provides confidence that:

For Tier 1 profiles ($n=50$, $k=5\%$), detection probability is $\sim$92%. This is not certainty—it is bounded uncertainty, documented and priced.

The converse matters just as much and must be stated with equal care. With $n$ samples and zero findings, the 95% upper confidence bound on the prevalence of compromise is approximately $3/n$ (the rule of three). Fifty clean samples bound undetected compromise at $\sim$5.9%, not at zero. Lot sampling supports graded confidence, never exoneration, and no claim in this thesis should be read as the latter.

What “Gold tier” requires:

A profile achieves Gold tier (L0-B or higher) when:

1. $\geq$80% of production lots are sampled each quarter at or above the tier minimum rate, with the remaining lots covered by supply-chain attestation.

2. No critical findings (backdoors, RNG bias $>$threshold) in the last 4 quarters.

3. Side-channel leakage remains within published budget under independent testing.

4. At least 2 independent labs have conducted inspections.

Coverage is counted in lots, not deployed units. Inspections are destructive and expensive; the lot is the auditable unit a sampling program can afford to buy. “80% of deployed units” would describe a near-total destructive audit of the fleet, which no assurance budget can fund and no fleet can survive; the reference design does not propose it and this document should not be read as though it does.

Gold tier unlocks:

• Full WC eligibility (no issuance cap).

• Zero collateral haircut.

• Eligibility for “pristine collateral” designation in DeFi integrations.

Funding mechanism:

The protocol allocates 2% of fee revenue to a Layer 0 Assurance Fund. This fund:

• Contracts with independent hardware security labs.

• Publishes RFPs for sampling campaigns.

• Maintains a public registry of inspection results.

• Is governed by a multisig of hardware security researchers (not protocol developers).

Transparency:

All sampling results are published within 30 days. Raw data (images, test logs) is archived and available for independent verification. If a lab’s findings are disputed, a second lab can be commissioned for arbitration.

How This Opens New Economies

Verifiable machines don’t just make today’s cloud slightly less sketchy. They unlock whole categories of economic arrangement that aren’t viable when hardware is a black box.

Verifiable cloud and compute co-ops.

If you can spin up a rack of open-design TEEs or accelerators and have them produce attestations and ZK receipts that anyone can verify, then:

• A small data center in Nairobi or Reykjavík can sell the same class of “trusted inference” or “trusted proving” as a hyperscaler in Virginia.

• A co-op of households can pool “AI appliances” in their basements and earn by running verified work for others.

• Regulators and enterprises can enforce compliance through proofs and telemetry, not vendor logos.

Compute ceases to be a winner-takes-all brand game and becomes a commodity with open admission.

Civic infrastructure that doesn’t depend on one vendor’s conscience.

Voting machines, digital ID kiosks, public-health dashboards: today they are RFPs to a short list of contractors. With open hardware and proof-wrapped attestation, you can build ballot boxes and ID hardware whose entire stack is open to public inspection and require that each device emit public proofs of correct behavior. Democratic legitimacy becomes a property of math and sampling, not of which vendor’s logo sits on the plastic.

Tamper-evident telemetry.

As the physical world fills with sensors and actuators, the ability to sell tamper-evident telemetry becomes critical. An environmental sensor built on an open profile, with attested firmware and ZK-wrapped readings, can sell CO$_2$ or temperature data as evidence into climate, insurance, and industrial hedging markets—not just as numbers on a dashboard.

Hardware-native monetary instruments.

Once machines themselves are verifiable actors, we can imagine “miner-notes” backed by the future output of a specific open-design proving farm, or municipal bonds whose coupon is denominated in SLA-backed capacity: $X$ proofs per second, $Y$ verified FLOPs, $Z$ private swaps per month, all attested by open hardware meters. These become new kinds of collateral: claims on capacity the world must keep buying.

Open profiles manufactured at multiple fabs in multiple jurisdictions turn chip supply into a multi-polar fabric instead of a single chokepoint. Neutral money needs neutral hardware; verifiable machines produced on a diversified manufacturing base make that a reachable design goal rather than a slogan.

Verifiable Power: Energy as First-Class Input

If Work Credits are energy-anchored claims on triad work, then power is not just an environmental footnote; it is an input to service delivery. It does not back the base asset or make the credit monetary.

Layer 0 treats power in three ways:

1. Measurement. Prover farms track power draw, mapping between workloads and power, and local generation vs. grid intake. These feed into Work Credit metadata and VerifyPrice models.

2. Resilience. Micro-grids or backup generation for critical infrastructure; geographic and jurisdictional dispersion of power sources.

3. Policy hedging. Transparent power telemetry allows answering “how much of this is actually training/inference/proof that humans pay for?”

For Work Credits, this means credits can carry energy provenance tags and markets can price credits differently based on energy profile.

Facility Capacity Receipts: Beyond Energy

Facility Energy Receipts (FERs, Appendix A: Formal Model of Verification Asymmetry & VerifyPrice) make energy legible, but verified digital infrastructure depends on more than kWh. A facility can have cheap energy and still be fragile if it sits behind a congested interconnect, depends on a water-constrained cooling system, runs in a jurisdiction with curtailment risk, or relies on a single transformer, fuel source, cloud vendor, or hardware profile.

We therefore extend FERs into Facility Capacity Receipts. An FCR records the physical capacity envelope behind a unit of verified work: grid node, interconnection class, outage history, backup duration, cooling dependency, water intensity, transformer redundancy, fuel mix, curtailment exposure, jurisdictional power risk, hardware profile diversity, and physical security status.

Facility Capacity Receipt (FCR)

A signed, auditable receipt that extends Facility Energy Receipt data with infrastructure resilience, grid, cooling, jurisdictional, and hardware-diversity metrics.

Suggested FCR fields

A Work Credit backed by resilient, diversified, verifiable capacity is economically different from one backed by cheap but brittle compute. The market should be able to price that difference. The stack should not hide physical fragility behind cryptographic elegance. If FCR data is unavailable or unverifiable for a facility, credits from that facility should receive issuance caps or risk haircuts (§22: Layer 6: Governance & Telemetry); §19: Layer 4: Truth & Work formalizes the cost of auditing FCR claims as Physical VerifyPrice.

Sovereign Optionality: Aggregating FCR Into One Exposure

§14: Layer 0: Verifiable Machines & Energy gives an allocator ten fields per facility. That is the right raw material and the wrong interface. Nobody underwrites a monetary asset by reading ten columns across a thousand facilities, and a field-by-field presentation makes it easy to be locally reassuring while globally fragile: every facility can look acceptable while the network sits inside two balancing authorities and one jurisdiction.

We therefore define a single aggregate exposure over fields the stack already collects. This is deliberately not new telemetry. It imposes no additional reporting burden; it changes how existing FCR data is read.

Sovereign Optionality ($\mathcal{O}_s$)

A capacity-weighted index of the number of independent physical pathways by which verified work can continue under disruption, net of exposure to external coercion. Computed entirely from Facility Capacity Receipt fields.

Adaptation of Scale

The concept is borrowed from state-level energy strategy, where analysts assess how many independent ways a sovereign can obtain electricity, fuel, and industrial feedstock when ordinary market relationships fail. The transposition to a proving network is close but not exact. Earlier versions dropped industrial and logistical throughput on the ground that proving has no conversion analogue. That claim was wrong.

A proving facility has a measurable conversion chain:

It is not manufacturing throughput, but it is conversion throughput. Any edge can become the binding cut, and a weighted resilience score can conceal a zero-flow series bottleneck. Sovereign Optionality therefore remains the pathway-diversity measure; Delivered Verified Capacity below supplies the missing throughput measure.

Mapping to Existing FCR Fields

Sovereign optionality components and their FCR sources

Every input already exists. Note in particular that the jurisdictional risk score of §14: Layer 0: Verifiable Machines & Energy is already specified to capture “seizure, power rationing, sanctions risk.” The stack has been collecting the coercion term all along without aggregating or acting on it.

Facility and Network Form

For a facility $f$, with each component normalised to $[0,1]$:

The network-level figure is the capacity-weighted mean across facilities, less a concentration penalty. Let $\kappa_f$ be facility $f$’s share of verified capacity, and let $H$ denote a Herfindahl–Hirschman index computed over jurisdictions and balancing authorities:

The penalty term is what prevents the local-reassurance failure. A network of individually excellent facilities that all sit behind the same interconnect or inside the same legal regime has one pathway, not many, and the weighted mean alone would not say so.

Relationship to existing metrics.

$H$ overlaps deliberately with the dispersion metrics already used for verification monoculture and enclosure risk (§27: Risk Analysis & Failure Modes, Red Lines 3 and 11). $\mathcal{O}_s^{\text{net}}$ should consume those existing measurements rather than introduce a parallel concentration statistic. Where they disagree, that disagreement is itself a finding.

Governance of the Weights

The weights $w_i$ are judgement, not measurement, and an index whose weights can be quietly retuned is a marketing instrument. Three constraints follow:

• Published and versioned. Weights ship with the telemetry spec; changes are proposals with rationale, not silent parameter updates.

• Independently reproducible. A third party holding the same FCR data must be able to recompute $\mathcal{O}_s$ and obtain the same number.

• Subject to capture review. Weight-setting falls under the same telemetry-capture constraints as the rest of the scoreboard (§27: Risk Analysis & Failure Modes, Red Line 4). The party being scored must not set the scoring function.

Report $\mathcal{O}_s$ alongside its component vector, never as a bare scalar. A single number is what an allocator wants and also what conceals which pathway is missing; publishing both is the only honest form.

What $\mathcal{O}_s$ Is For

The index does real work in two places, and is otherwise decoration:

1. Risk haircuts. It extends issuance discipline from “we cannot see this facility” to “we can see it clearly and it is fragile” (§22: Layer 6: Governance & Telemetry).

2. Falsification. It supplies the measurable condition for the energy-sovereignty red line (§27: Risk Analysis & Failure Modes).

Absent those two hooks, $\mathcal{O}_s$ would be another dashboard number. With them, it is a constraint that can bind against issuance and a threshold that can retire the thesis.

Delivered Verified Capacity: Surviving Service Flow

Delivered Verified Capacity (DVC)

For canonical workload $W$, interval $t$, and disruption scenario $s$, Delivered Verified Capacity is the maximum usable service flow through the complete energy-to-settlement network after scenario-specific edge capacities, substitution latency, and common-cause failures are applied.

Let $G_{W,t,s}=(V,E)$ be a directed capacity graph whose source nodes are available energy and fuel and whose sink is usable settled service. Each edge $e$ carries surviving capacity $c_e(W,t,s)$ in a common workload-specific service unit. Then

and the corresponding minimum cut identifies the bottleneck that actually limits delivery. The unit is not a generic FLOP: it is a settled, independently verifiable unit of the canonical workload at the promised tier.

Scenario specificity.

A benign-state graph and a drought, fuel-shock, transformer-loss, chip-embargo, network-partition, stablecoin-depeg, or coordinated-policy graph are different objects. Scenario $s$ changes edge capacities and may remove nodes or entire dependency classes. Publishing only the expected or capacity-weighted average is insufficient because a series path fails at its narrowest edge.

Substitution latency.

Redundancy exists only when an alternative can enter before the service obligation expires. For each edge publish a substitution time $\ell_e(s)$ and the workload’s maximum tolerated interruption $L_W$. An alternative with $\ell_e(s)>L_W$ does not contribute to DVC in that scenario, even if it eventually restores capacity. Spare hardware in another jurisdiction is not current redundancy if export approval, installation, synchronization, or key rotation takes longer than the SLA permits.

Common-cause dependencies.

Nominally separate facilities may share a transformer vendor, firmware signer, cloud identity layer, cable, gas market, cooling basin, stablecoin, legal safe harbor, or market maker. Assign each edge one or more dependency groups $g$. A scenario can haircut or remove all edges in a group simultaneously. Geographic dispersion without dependency-group dispersion is not independent capacity.

Relationship to Sovereign Optionality.

Sovereign Optionality asks how many independently substitutable pathways exist and how exposed they are to coercion. DVC asks how much usable service reaches the sink after the scenario binds. A network can have high optionality and low DVC because all alternatives are small or slow; it can have high benign DVC and low optionality because one large path supplies nearly everything. Report both, with the active minimum cut and dependency groups, rather than combining them into a reassuring scalar.

Issuance discipline.

Work Credits, capacity vouchers, and any other forward service claim must be bounded by a conservative stress-adjusted quantity,

where $h_{W,t}$ is a published prudential haircut. FCR, FER, and PIDL artifacts supply evidence for edge capacities; they are not themselves capacity. Governance may not replace this bound with nameplate power, installed hardware, gross proof throughput, or a benign-state average.

Resilience Versus Affordability: The Layer 0 Cost Tension

The previous section asks for resilient, dispersed, fuel-diverse, backup-equipped capacity. The thesis elsewhere insists that verification must stay cheap: “anyone can verify” is the hinge, and §27: Risk Analysis & Failure Modes treats its failure as fatal.

These two demands pull against each other, and the tension should be stated rather than glossed.

Resilience is insurance. Insurance has a premium. A jurisdictionally dispersed, fuel-diverse, backup-equipped fleet costs more per verified unit than a single facility sitting on cheap interruptible power.

If hardening Layer 0 raises cost per verified unit, then hardening Layer 0 pushes the stack toward the very red line that hardening was supposed to protect. A thesis that demands both cheap verification and expensive redundancy without reconciling them has an open flank.

Two Different Exposures

The tension dissolves partially once we separate two things that “energy cost” conflates.

The verification side.

Checking a proof happens on reference hardware, at the edge, in small amounts. Its physical exposure is not bulk industrial power. It is:

• Reference hardware obtainability. Export controls, sanctions, or platform lockdown can make the reference verifier unavailable, or available only in attested-and-permissioned form.

• Edge power and connectivity cost relative to local income, which is what makes verification affordable in practice rather than in principle.

The proving side.

Generating proofs and running verified compute consumes bulk power. Its exposure is:

• Energy price and firmness at facility scale.

• Competition for the same electrons from industrial load and state-directed AI build-outs.

• Curtailment, rationing, and interconnection denial, which are policy instruments, not market outcomes.

Conflating these produces sloppy claims in both directions. Bulk electricity prices do not directly break “anyone can verify,” because verification is not a bulk-power activity. What breaks the hinge on the verification side is loss of access to unprivileged reference hardware. What bulk energy conditions threaten is the proving economy: Work Credit issuance, geographic concentration, and enclosure.

Scope of “Exogenous”

§19: Layer 4: Truth & Work describes Physical VerifyPrice SLOs as “constitutional” and “exogenous to token price.” That is correct and worth keeping: the SLOs must not be redefined because the market moved.

But exogenous to token price is not exogenous simpliciter. Physical VerifyPrice remains endogenous to the physical and jurisdictional conditions under which reference hardware and power are obtainable. Those conditions are partly set by states. The constitutional claim should be read with that scope, not as a claim that the metric floats free of politics.

Disruption-Adjusted VerifyPrice

For the proving side, comparing a resilient fleet against a brittle one at benign-state spot cost is the wrong comparison. It prices the premium and ignores what the premium buys.

Let $s$ index physical disruption states—normal operation, regional curtailment, extended outage, hardware supply interruption, jurisdictional exclusion—with probabilities $\pi_s$ and state-conditional cost $\text{VerifyPrice}_s(W)$ for workload $W$. Then:

Disruption-Adjusted VerifyPrice

The probability-weighted cost of verification across physical disruption states, rather than the observed cost under benign conditions.

A resilient fleet has higher $\text{VerifyPrice}_{\text{normal}}$ and lower $\text{VerifyPrice}_{\text{adj}}$ whenever the reduction in disruption-state cost outweighs the benign-state premium. A brittle fleet optimised purely for spot cost reports an attractive headline number and carries the tail.

The $\pi_s$ are estimates and should be published as such, with their basis, rather than presented as measurements. An operator who can move $\pi_s$ by assertion can make any fleet look resilient; disruption-state probabilities are therefore governance parameters subject to the telemetry-capture constraints of §27: Risk Analysis & Failure Modes.

The Decision Rule

Priority ordering matters here, because “resilience” is exactly the kind of word that can be used to excuse blowing through a constitutional target.

Accept a benign-state resilience premium only if it lowers disruption-adjusted VerifyPrice, and only if benign-state Physical VerifyPrice remains inside the constitutional SLO band.

The second clause is not negotiable. Resilience is subordinate to the hinge: a fleet so hardened that ordinary users can no longer afford to verify has defeated the purpose of hardening it. Redundancy that breaches the SLO band is not insurance; it is the failure mode wearing insurance as a costume.

This gives the thesis a definite position on “resilience over efficiency,” worth stating plainly because the slogan travels widely and is usually asserted rather than priced:

• A bounded, measurable premium that buys a large reduction in tail risk is acceptable, and should be visible in FCR data rather than hidden in operator margin.

• An unbounded premium, or one that cannot be shown to reduce disruption-state cost, is not resilience. It is capital misallocation with a security narrative attached.

The FCR fields of §14: Layer 0: Verifiable Machines & Energy, aggregated as the sovereign optionality index of §14: Layer 0: Verifiable Machines & Energy, are precisely the instrument that distinguishes the two cases. Without them, “we are building resilience” is unfalsifiable. With them, it is a number an allocator can check.

Where this sits in the energy-security literature.

The trade-off named here — redundancy and optionality priced against the cost of carrying idle capacity — is the central, long-standing question of energy systems reliability economics: the “resource adequacy” debate over how much excess capacity a grid should carry, and who pays for it. That literature (regulatory and academic, from NERC reliability standards through the capacity-market literature) has spent decades converging on the same conclusion this section reaches by a shorter route: resilience that is not metered becomes rent. The thesis does not import the literature’s models, and its FCR/DVC instruments are its own; but the position taken here is not contrarian, and the slogan it prices is the same slogan that literature prices. Analyst commentary used elsewhere in this Part (Doomberg, in Sources) supplies the scenario framing; the regulatory economics supplies the skepticism.

Operational Patterns: Profiles, Upgrades, and Failure Modes

Layer 0 is not static; hardware evolves, breaks, and gets deprecated. We need patterns for living with that churn.

Hardware Profiles and Workload Binding

Each canonical workload $W$ in Layer 4 is associated with one or more acceptable hardware profiles $(H_1, H_2, \ldots)$. Profiles define:

• Minimum performance characteristics (to keep VerifyPrice in target bands).

• Acceptable side-channel leakage budgets.

• Attestation/sampling histories.

• Known caveats (e.g., “avoid profile H3 for workloads with secret inputs; leaks are too strong”).

When PaL compiles a workload or the router assigns work, it can target specific profiles, diversify across profiles, or refuse high-sensitivity workloads to marginal profiles. This is how Layer 0 informs the market rather than hiding under it.

Upgrades and Deprecations

Hardware ages; bugs and backdoors are discovered; fabs change hands. Layer 0 needs clear life-cycle rules:

Onboarding:
New profiles go through a probation period with extra sampling and conservative Work Credit weights.

Deprecation:
When a profile is compromised or obsolete, higher layers stop accepting new Work Credits minted from it, risk-flag existing credits, apply collateral haircuts, or impose prospective ineligibility, and publish an incident report at Layer 6.

Migration:
Proof factories and corridor operators need technical paths to migrate workloads off deprecated profiles without massive downtime.

In monetary terms, this is the hardware analog of a bond downgrade: transparent, describable, and priced, rather than silently swept under the rug.

Non-Discretionary Downgrade Rules

To prevent “ex post discretionary default” critiques, deprecation and haircut decisions follow a predictable severity framework, not ad hoc governance.

Severity levels for hardware profile issues.

Process guarantees:

1. Evidence threshold: S1 requires independent lab confirmation; S2 requires reproducible demonstration; S3 requires active exploitation observed.

2. Multi-party decision: Severity escalation requires sign-off from $\geq$3 of 5 designated hardware security reviewers.

3. Appeal process: Profile sponsors can challenge findings within 14 days.

4. Sunset, not confiscation: Even at S3, existing credits remain eligible at 75% of protocol-recognized collateral value. This is a statement about the protocol’s own accounting, not a guarantee about market price: no protocol can promise what its asset trades for after a catastrophic hardware compromise, and this document makes no such promise.

5. Transparency: All severity determinations are published.

PQ and Cryptographic Agility

Some Layer-0 assumptions are about cryptography, not just silicon: signature schemes in ROMs, hash functions in hardware accelerators, and RNG primitives.

Layer 0 insists that hardware and firmware expose enough configurability to migrate to post-quantum or new primitives without throwing away entire fabs. Hardware profiles document cryptographic agility (e.g., “can switch hash from X to Y via firmware; signature scheme fixed”).

Stress Tests for Layer 0

Every claim in Layer 0 should map to a testable stress scenario:

Layer 0 stress tests.

If a stress test fails, Layer 0 degrades visibly: profiles are flagged, Work Credits tied to them are risk-flagged and may face prospective ineligibility, and Layer 6 publishes an incident report.

What Layer 0 Exports to Higher Layers

Higher layers consume a small set of artifacts and APIs:

1. Hardware profiles (HIDs). Compact identifiers + dossiers describing profile properties, sampling history, and current status.

2. Attestation receipts. Machine-level statements binding device $\to$ profile, firmware $\to$ hash, measurement $\to$ nonce/time.

3. Power and health telemetry. Streams of power usage, failure rates, and uptime patterns.

4. Incident and status flags. Signals like “Profile H3 compromised; do not accept new work.”

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