← All disputes
Dispute
d-ba1826a5ebb32a73
Created 2026-05-25 16:14:08 UTC
mode · fraudphase · Resolvedoutcome · Slashed
Dispute lifecycle
d-ba1826a5ebb32a73
✓
Commitment
✓
Challenge
✓
Bisection
✓
Final Step
✕
Bitcoin Settlement
transition_root anchored · trace length 8
challenger opened dispute
3 rounds · log₂(8) max
disputed step s_4 → s_5
bond slashed on Signet
trace_id tr-ba1826a5ebb32a73commit 6e177c…261btrace_len 8max_rounds 3settlement taproot · 3-leafsig_scheme BIP-340chain signet
Bitcoin transactions
Signet · fixture data — txids shown are not on-chain
Commitment / bond
7af3b2c1…0c2b1e84fixture
Defense
pending broadcast
Slash
a91d4c7e…a4c61f5bfixture
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.