Canonical dispute scenarios
Five reference scenarios covering the major dispute paths. Each links to a deterministic fixture record so the artifacts are stable across visits. Switch to live coordinator mode to render against real dispute records.
Honest commitment
Operator publishes a valid trace. Challenger independently recomputes, finds output matches, and never opens a challenge. Operator reclaims bond via the timeout leaf.
Fraud at early step
Operator injects a fault near the start of the trace. Bisection narrows to s_1 → s_2 in the first round. Settlement pending.
Fraud at midpoint
Canonical demo case. Fault injected at the trace midpoint. Three bisection rounds localize the fault. Operator cannot produce a valid preimage. Bond slashed.
Fraud at late step
Fault injected near the end of the trace. First two rounds confirm agreement in early segments; the third round identifies the disputed step. Bond slashed.
In-flight bisection
A dispute mid-flight. First round complete, two more pending. Useful for inspecting how the protocol looks during convergence rather than after.
Deterministic artifacts
All gallery hashes are real protocol outputs from seed 0x42…42. Anyone can reproduce them by running the coordinator locally.
Bisection convergence
For a trace of length n, bisection converges in exactly ⌈log₂ n⌉ rounds. Length 8 → 3 rounds. Verifiable on every detail page.
Bitcoin settlement
Resolution is enforced by Taproot script paths on Signet. Settlement transactions are fixtures here; live coordinator mode binds them to mempool.space.