Loading event history…
← All disputes
Dispute
d-f1a8b3c7e9d04621
Created 2026-06-07 22:32:38 UTC
mode · fraudphase · Resolvedoutcome · Slashed
Dispute lifecycle
d-f1a8b3c7e9d04621
✓
Commitment
✓
Challenge
✓
Bisection
✓
Final Step
✕
Bitcoin Settlement
transition_root anchored · trace length 8
challenger opened dispute
3 rounds · log₂(8) max
disputed step s_3 → s_4
slash leaf · pending broadcast
trace_id tr-f1a8b3c7e9d04621commit 2158c1…1777trace_len 8max_rounds 3settlement taproot · 3-leafsig_scheme BIP-340chain signet
Bitcoin transactions
Signet · click any txid to inspect on mempool.space
Commitment / bond
pending broadcast
Defense
pending broadcast
Slash
pending broadcast
Operator
79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798
Publishes the state commitment. Must defend the disputed step by revealing a valid preimage during the defense window.
Challenger
c6047f9441ed7d6d3045406e95c07cd85c778e4b8cef3ca7abac09b95c709ee5
Independently recomputes the trace and disputes the operator's claim. Sweeps the bond via the slash leaf if defense fails.
Disclaimer
This terminal demonstrates Axion's Bitcoin-anchored dispute lifecycle on Signet. Some contract timing is simplified for MVP purposes: the dispute contract is currently parameterized after bisection converges. Production BitVM-style enforcement will require pre-signed transaction trees and connector outputs to lock the bond at commitment time and carry the dispute through to settlement without operator coordination.