Status: implemented canonical protocol
A signed ProofBody fixes executable transformer logic, but its dynamic
arguments can become available only when a dispute is submitted. Positional
arguments must still refer to the exact signed state being finalized. Building
them from newer live Account state can shift swap, HTLC, or Pull positions and
apply valid evidence to the wrong signed program.
The protocol therefore commits two starter-owned argument blobs at dispute start:
starterInitialArguments belongs to the initial signed ProofBody;starterCounterArguments belongs to one exact newer signed ProofBody
identity committed as H(nonce, proposerIsLeft, proofbodyHash).There is one production ABI. There are no V2 structs, deprecated aliases, block-based deadlines, or compatibility readers.
InitialDisputeProof contains the full initial ProofBody, its hash and nonce,
the counterparty Hanko, the shared watch seed, and both starter argument blobs.
The full body is required at start so a signer cannot activate a body too large
to finalize within the contract limits.
FinalDisputeProof contains the exact final ProofBody, starterArguments
selected from the start commitment, otherArguments supplied by the finalizer,
and the signed final nonce when applicable. The transformer receives explicit
left/right arguments after the contract derives participant roles.
The stored dispute hash commits:
Argument commitments include the starter side and dispute start timestamp. This prevents replaying a blob across another role or dispute clock.
The Runtime builds arguments only from immutable snapshots indexed by exact
proofbodyHash. It may commit no newer blob or exactly one newer blob already
signed by the starter. Ambiguous or missing snapshots fail loudly; the Runtime
never rebuilds historical arguments from current Account state.
At finalization:
starterInitialArguments;starterCounterArguments;Pull evidence is not carried in either dynamic argument blob. Pull settlement reads the Account-scoped HashLadder registry for the signed Pull role and exact active dispute clock.
All jurisdiction deadlines are Unix seconds. The Runtime uses milliseconds only for scheduling and floors to seconds at the contract boundary.
S + leftResponseSeconds + rightResponseSeconds for either party.