Swap settlement means the execution has applied the trade's state changes in a block. Confirmation describes acceptance of that transaction in the chain, often with additional blocks or consensus evidence. Finality is a stronger chain-specific concept about how difficult or impossible reversal is under its rules.
Three questions, not one status
- Did execution succeed? The transaction or settlement must have completed the required contract operations.
- Where is it included? Identify the block and current canonical chain view.
- How final is that inclusion? Apply the network's consensus and finality rules.
Ethereum's transaction lifecycle separates submission, block inclusion and later finalization. Its proof-of-stake documentation explains consensus finality. Other chains use their own mechanisms, so Ethereum timings or thresholds should not be copied into a universal swap rule.
Included does not necessarily mean swapped
A failed transaction can still appear in a block. The network has processed the transaction, but the swap did not commit its intended state changes. Counting confirmations without checking execution status can therefore produce the wrong conclusion.
Likewise, a submitted hash does not prove inclusion. It identifies a transaction that may still be pending or may not appear in the current chain.
Intent orders add another identifier
An intent system can issue an order identifier before any settlement transaction exists. The order may later be fulfilled through an executor's transaction. An order ID and a transaction hash answer different tracking questions.
CoW's order-flow documentation illustrates this separation.
For a clear completion record, connect the order or user request to the successful settlement and then apply the relevant chain confirmation policy. A front-end label such as “done” is a convenient summary; the underlying execution and inclusion facts give it meaning.
This distinction is particularly useful when another application requires a settled asset before proceeding. Its acceptance policy may wait beyond the first visible balance update.
Sources & verification (3)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Transactions | ethereum.org
Transaction fields, native value versus calldata, inclusion and finality.
https://ethereum.org/developers/docs/transactions/ - Proof-of-stake (PoS) | ethereum.org
Inclusion, consensus and finality are separate stages; no chain timing extrapolation.
https://ethereum.org/developers/docs/consensus-mechanisms/pos/ - Flow of an order
Intent submission, auction, solver execution and settlement lifecycle.
https://docs.cow.fi/cow-protocol/concepts/how-it-works/flow-of-an-order