Settlement

SETTLEDSETTLED_FINALgen 1role unknown until a wallet connects
Outcome
Settled.

The terms of this trade were not recovered, so amounts are not stated. An independent verifier read both chains and confirmed both legs were delivered.

Next action

This panel reads the coordinator on Monad and the token and adapter on Base directly from your browser, and decides what this settlement needs next. The projection below is a convenience and is never the authority.

Terms were not recovered

No artifact carries this settlement’s intent, so amounts and parties are unknown rather than zero. The outcomes below are still read from chain state and are accurate.

The trade

Monad Testnet
Cash leg
not recovered
—
RELEASED
authenticated state
COMMIT
Base Sepolia
Asset leg
not recovered
—
RELEASED
Neither asset crosses a chain. What crosses is authenticated settlement state, and the two contracts that carry it share the same twenty bytes on different chains — which is why every address on this page is chain-qualified.

Legs

Cash leg
RELEASED
ChainMonad Testnet
Asset—
Amountnot recovered
Counterparty10143
OutcomeRELEASED
Asset leg
RELEASED
ChainBase Sepolia
Asset—
Amountnot recovered
Counterparty84532
OutcomeRELEASED

What the state means

SETTLEDcanonical, read from the coordinator

Both legs executed. The trade is complete.


SETTLED_FINALderived by the verifier, not an on-chain value

Independently verified: both legs delivered to the parties the intent named.

Proof behind this outcome

Lifecycle

Both legs prepared
Cash escrowed, asset reserved
Economic finality
The remote state a commit rests on
Fresh compliance
Answered again at commit time
Commit
Irreversible. No refund exists after this point
Delivery
Both legs execute, or the value is held

Compliance

The projection stores no Cleanverse answers for this settlement. That does not mean none were asked: the coordinator refuses a COMMIT without a valid compliance attestation, and the verifier checks the outcome from chain state.

Conservation

The projection stores no conservation snapshot for this settlement. The verifier recomputes it from chain state: the escrow must account for exactly what it holds, and no reservation may stay open.

Cross-chain messages

TypeSeqEmitterFinalityGuardians signed afterConsumptionPublished in
ASSET_PREPARED 0 845320x00000000…7f45be FINALIZED
no signature timing stored
consumed once not captured by the loader
ASSET_RELEASED 1 845320x00000000…7f45be FINALIZED
no signature timing stored
consumed once not captured by the loader
COMMIT 0 101430x00000000…7f45be FINALIZED
no signature timing stored
consumed once not captured by the loader
CASH_PREPARED 0 101430x00000000…a601eb FINALIZED
no signature timing stored
consumed once not captured by the loader
Finality is classified, never compared as a number. Wormhole encodes 200 as instant and 201 as safe; everything else is finalized. Ranking the raw byte would place instant above finalized, which is the substitution a settlement layer cannot afford.