Where the v2.0 soak stands.
ReserveGrid OS v2.0 Invariant Shield is in staged validation. This page tracks the soak in motion, what has cleared, and what remains gated on a real-bitcoind run or a pool-side design partner. Numbers update as each checkpoint lands.
Setup A · Shadow soak
○ PendingSynthetic mempool feed against a docker-compose mirror of the verifier stack. The intended pass criterion was zero Class M tolerance breaches across the full window. Forensics on 2026-07-22 found the Invariant Shield skipped every template, so the criterion never ran: this window yields no evidence about v2_invariant_mempool_tolerance_exceeded either way.
Setup B · Real-bitcoind soak
○ PendingClass S and Class D check chain against a real mainnet bitcoind under live template flow. A hardened re-soak is running: T+0 2026-07-22, T+7 wrap 2026-07-29, with evidence written outside the soaked process so it survives container death. It exercises mempool-view infrastructure and Phase 1 policy only. The Class M criterion stays unexercised until the template sender ships raw_block_hex, so no Class M evidence exists yet.
Setup C · Pool-side design partner soak
○ PendingLive template stream from a participating Stratum V2 pool, mirrored into the verifier in shadow mode. Treats the pool as the source of truth and the verifier as a second pair of eyes; the only path to evidence on real-world template traffic.
Phase 1.5 · Tier 3 invariant wiring
○ PendingWired 2026-07-22. All seven Tier 3 invariants (coinbase_script_length, coinbase_output_count, weight_exceeds_max, sigops_exceed_max, nontcb_null_prevout, header_version_low, duplicate_tx) are implemented and tested behind the shield facade, bringing the Invariant Shield to 18 of 18 ADR-002 invariants running. Wired is not validated and not yet merged: the change sits on branch, and the merge to main is sequenced after the in-flight re-soak wraps.
Setup B and Setup C are open.
If you operate a Stratum V2 pool and want a second pair of eyes on your template stream, the design-partner slots for Setup B and Setup C are open. Shadow mode first, no enforcement on the wire, full evidence trail in your own observability stack. The output of this work is a public soak report and the operator keeps everything that runs in their own infrastructure.
Mention "design partner" in the message and one of us replies within two business days.