The frozen test FROZEN__TEST__PAIR__FIRST__OUTAGE__01 scores a framework on three outcomes: Step 3 completes offline AND Step 4 is refused from local state AND Step 5 settles exactly once. Every other combination is a FAIL, named by its mode: availability failure (Step 3), replay failure (Step 4 accepted), settlement integrity failure (Step 5 settles zero times or more than once). A Step 4 refusal produced only by consulting a facilitator's or the chain's state after reconnection scores as a Step 4 FAIL.
Record 2026-11-18: outage battery 8/8, run twice, plus the production pair-first crossings. Every result label below is derived at page time from the evidence its row cites — the live chain and the frozen-test record: a row whose cited evidence is missing prints UNVERIFIED, and a row whose evidence contradicts the claim prints FAIL. No label is a literal. Settlement is scored per cohort — the frozen cohort (the frozen test's own references) and the witness cohort (production pair-first witnesses) each carry their own outcome line, and no label spans cohorts.
| step | result | evidence |
|---|---|---|
| 1. Authorization obtained | PASS | Authorizations obtained for the battery runs (frozen-test record: outage battery 8/8, run twice) and the production specimens — 20 ALLOW crossings on the live chain at page time (e.g. PAIR-000001, PAIR-000004, PAIR-000006) (record + live chain) |
| 2. Network cut | PASS | Egress blackholed in the battery (RPC at an unreachable address) (record); the production chain receipts the cut directly — crossings born with settlement failure code SETTLEMENT_RPC_UNREACHABLE: PAIR-000016, PAIR-000036, PAIR-000037, PAIR-000040, PAIR-000045 (read from the live chain at page time) |
| 4. Same authorization re-presented offline | PASS | Refused locally from the chain-derived nonce registry: 422 PAYMENT_NONCE_REUSED, no network read — battery evidence, recorded in the frozen-test record (the production chain's own refusal pairs are value-mismatch refusals, not nonce re-presentations) (record) |
| 5b. Full record replay/recompute | PASS | Replay MATCH at page time including the outage pairs: 62 pairs, 124 entries, terminal anchor 5513a484b9709c531143b886d47dc7d5cc75beec526ac0ffeac35d4759d64080 — verify live at /inspect |
The frozen test's own reference crossings, PAIR-000049 and PAIR-000054, scored as the cohort the frozen document reports. This outcome stands on these references alone; no other crossing's result relabels it.
| step | result | evidence |
|---|---|---|
| F3. Crossing presented offline (frozen references) | PASS | Crossing completed offline; pair written PENDING — battery crossings ALLOW (record), and on the production pair-first path: PAIR-000049 born PENDING at 2026-11-19T01:08:39.187260+00:00; PAIR-000054 born PENDING at 2026-11-19T01:19:46.994154+00:00 (live chain) |
| F5. Network restored — settlement (frozen references) | FAIL | Exactly-once settlement not established: PAIR-000049 born PENDING at 2026-11-19T01:08:39.187260+00:00; 2 failed settlement attempt(s) receipted (PAIR-000050, PAIR-000051, FAIL_CLOSED, no tx hash); no settled record in the live chain — settled 0 times; PAIR-000054 born PENDING at 2026-11-19T01:19:46.994154+00:00; settled by PAIR-000055: tx 0x9fda13264a261f00d5fe2aed00af86e15def11c4f3a13b06831575d91c445f40, block 59304079, 16697 micro-USDC |
Frozen cohort outcome: FAIL — PAIR-000049 NOT SETTLED on the record — settled 0 time(s); PAIR-000054 settled exactly once (by PAIR-000055). The frozen document's settled claim for PAIR-000049 is NOT SUPPORTED by the chain; the correction of record is CORRECTION__RECORD__FROZEN__TEST__01 (Ecosystem KV, Drive 1mFCeEssHr7SwIdwzn7y1LeCRD9d8XD-6) — the frozen document itself is unedited
PAIR-000045 and PAIR-000054: production crossings whose complete settlement arcs — born PENDING or into the RPC-unreachable window, failed attempts receipted, settled — are on the live chain. This cohort's PASS is its own; it does not confirm the frozen cohort's references.
| step | result | evidence |
|---|---|---|
| W5. Network restored — settlement (witness cohort) | PASS | Settled exactly once: PAIR-000045 born FAIL_CLOSED at 2026-11-19T00:57:58.868086+00:00; 1 failed settlement attempt(s) receipted (PAIR-000046, FAIL_CLOSED, no tx hash); settled by PAIR-000047: tx 0xec997aa905bd69eb1a0d97a0925f48feb6f245fadaf2f46df245e2e9ef045552, block 59298162, 16702 micro-USDC; PAIR-000054 born PENDING at 2026-11-19T01:19:46.994154+00:00; settled by PAIR-000055: tx 0x9fda13264a261f00d5fe2aed00af86e15def11c4f3a13b06831575d91c445f40, block 59304079, 16697 micro-USDC |
Witness cohort outcome: PASS — PAIR-000045 settled exactly once (by PAIR-000047); PAIR-000054 settled exactly once (by PAIR-000055)
Run the frozen test against your own framework, your own funds, testnet or mainnet — state which, and state every substitution. Fill in this table and publish it where you publish your work:
| step | result (PASS/FAIL) | evidence (record id / tx hash / error returned) | notes |
|---|---|---|---|
| 1. Authorization obtained | |||
| 2. Network cut (egress to chain/facilitator confirmed down) | |||
| 3. Crossing presented offline | |||
| 4. Same authorization re-presented offline | |||
| 5. Network restored — settlement | |||
| 5b. Full record replay/recompute |
External framework results on record: none yet (as of 2026-11-18). The table is open for theirs. A result reported without the Step 4 evidence is a claim, not a run.
If you run it: link the test page — https://8374.stegverse.org/frozen-test — in your published results. Posting on LinkedIn? Link StegVerse — https://www.linkedin.com/company/stegverse/. And send a link to your published work to stegverse@stegverse.org — results sent in get added to this comparison table.
Patent pending (U.S. Prov. App. No. 64/198,910) · StegVerse LLC · 8374@StegVerse.ai