chain bitcoin · signetblock #196452state fixturepeers 5 (simulated)
--:--:-- UTC
Axion · Dispute Terminal
← Axion MainOpen Terminal
← All disputes
Dispute

d-7c2e9f4b1a3d5e80

Created 2026-05-26 09:15:33 UTC
mode · fraudphase · Settlementoutcome · Pending
Dispute lifecycle
d-7c2e9f4b1a3d5e80
✓
Commitment
✓
Challenge
✓
Bisection
✓
Final Step
5
Bitcoin Settlement
transition_root anchored · trace length 8
challenger opened dispute
3 rounds · log₂(8) max
disputed step s_1 → s_2
awaiting on-chain resolution
trace_id tr-7c2e9f4b1a3d5e80commit 4b5c6d…99aatrace_len 8max_rounds 3settlement taproot · 3-leafsig_scheme BIP-340chain signet
Replay dispute
Step through the lifecycle as it unfolded
step 1 of 7 · Commit
transition_root 4b5c6d7e…8899aa anchored · trace_len=8
Bisection rounds
Converged on step 1 after 3 rounds
log₂(8) = 3
s_0
✓
s_1
◆
s_2
◆
s_3
✓
s_4
✓
s_5
✓
s_6
✓
s_7
✓
s_8
✓
Fraud localizedstep 1 → 2
s_1 (agreed) c3d4e5f60718…6d7e8f90a1b2
s_2 (operator claim) b2c3d4e5f607…5c6d7e8f90a1
Operator must reveal preimage p with SHA256(p) = claimed s_2. If no such preimage exists, the Taproot defense leaf is unsatisfiable and the slash leaf wins after the defense window.
RoundIntervalMidOperator claimSignatureBranch
R1[0, 8]4a1b2c3d4…7e8f90a1a1a1a1…a1a1a1← fault left
R2[0, 4]2b2c3d4e5…8f90a1b2b2b2b2…b2b2b2← fault left
R3[0, 2]1c3d4e5f6…90a1b2c3c3c3c3…c3c3c3← fault left
Fixture intentionally pre-settlement

This fixture intentionally stops before settlement broadcast. Connect the live coordinator to advance the dispute into real Signet transaction flow.

Open resolved fixture scenario →
Bitcoin settlement pending
Block #196452 · awaiting tx
settlement transaction will spend the bond via the appropriate taproot script path once the defense window expires
Settlement progressionfixture · 6 states
Pending
Broadcasted
Seen in mempool
1 confirmation
3 confirmations
Finalized
mempool + confirmation events are simulated · live mode binds to coordinator chain feed
Settlement chain
Dispute lifecycle anchored to Bitcoin
signet
✓
Commitment
transition_root 4b5c6d7e…8899aa
✓
Challenge
challenger opened dispute
✓
Bisection
3 of 3 rounds · log₂(8)
Settlement
awaiting taproot spend
₿
Bitcoin block · #196452
awaiting settlement transaction
pending
block height · fixture
Bitcoin transactions
Signet · fixture data — txids shown are not on-chain
mock mode
Commitment / bond
3a4b5c6d…f6071829fixture
fixture
Defense
pending broadcast
pending
Slash
pending broadcast
pending
Verification
Cryptographic inspectability for every dispute artifact
deterministic · fixture
commitment_root
4b5c6d7e…8899aa
trace_length
8 steps
max_rounds
3 (log₂)
disputed_transition
s_1 → s_2
signed midpoint claims · BIP-340 schnorr3 of 3 verified
R1
claim a1b2c3d4…7e8f90
sig a1a1a1a1…a1a1a1
✓ verified
R2
claim b2c3d4e5…8f90a1
sig b2b2b2b2…b2b2b2
✓ verified
R3
claim c3d4e5f6…90a1b2
sig c3c3c3c3…c3c3c3
✓ verified
settlement: taproot · 3-leaf (timeout · defense · slash)internal key: NUMSseed: 0x42…42
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.