Dispute

d-2d4f4f4bd5a7078e

Created 2026-05-25 16:20:05 UTC

mode · honestphase · Openedoutcome · No Fraud

Dispute lifecycle

d-2d4f4f4bd5a7078e

✓

Commitment

✓

Challenge

Bisection

Final Step

Bitcoin Settlement

transition_root anchored · trace length 8

no fraud detected by challenger

up to 3 rounds

single-step verification

timeout reclaim · no challenge

trace_id tr-2d4f4f4bd5a7078ecommit b420b5…9ab8trace_len 8max_rounds 3settlement taproot · 3-leafsig_scheme BIP-340chain signet

Replay dispute

Step through the lifecycle as it unfolded

step 1 of 3 · Commit

transition_root b420b504…6f9ab8 anchored · trace_len=8

Bisection rounds

Awaiting first round

log₂(8) = 3

s_0

s_1

s_2

s_3

s_4

s_5

s_6

s_7

s_8

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 b420b504…6f9ab8

✓

Challenge

no challenge raised

Bisection

0 of 3 rounds · log₂(8)

Settlement

timeout reclaim

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

c4d5e6a7…70819203fixture

fixture

Defense

pending broadcast

pending

Slash

pending broadcast

pending

Verification

Cryptographic inspectability for every dispute artifact

deterministic · fixture

commitment_root

b420b504…6f9ab8

trace_length

8 steps

max_rounds

3 (log₂)

disputed_transition

—

no signed claims · no challenge raised

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.