Published snapshot — 2026-11-18. A static copy of the production endpoint page, published to stegverse.org so it stands independent of any single host. Values shown are record content as of 2026-11-18, not live state. For the live determination, see https://8374.stegverse.org/inspect.

0R10N15-8374 — test comparisons

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.

Reference result — 0R10N15-8374 (production)

Record 2026-11-18: outage battery 8/8, run twice, plus the production pair-first crossings. The Step 5 settlement evidence below is record content as of 2026-11-18.

stepresultevidence
1. Authorization obtainedPASSAuthorizations obtained for the battery runs and the production specimens (record)
2. Network cutPASSEgress blackholed in the battery (RPC at an unreachable address); production transport windows receipted as SETTLEMENT_RPC_UNREACHABLE (record)
3. Crossing presented offlinePASSCrossing completed offline; pair written PENDING — battery crossings ALLOW, and production PAIR-000049 and PAIR-000054 born PENDING on the pair-first path (record)
4. Same authorization re-presented offlinePASSRefused locally from the chain-derived nonce registry: 422 PAYMENT_NONCE_REUSED, no network read (record)
5. Network restored — settlementPASSSettled exactly once: PAIR-000049, tx 0x6fac4964f1a4d0e44e5189d6f8a6ac50eabd46b516d463da0d5eb07d00bd9b77, block 59302294, 16,702 µUSDC; PAIR-000054 → PAIR-000055 SETTLED, tx 0x9fda13264a261f00d5fe2aed00af86e15def11c4f3a13b06831575d91c445f40, block 59304079, 16,697 µUSDC (record, per the frozen test document)
5b. Full record replay/recomputePASSReplay MATCH including the outage pairs — verify live at /inspect

Report yours

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:

stepresult (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.

Submit your result

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