Skip to main content
BitCurrent

Crypto markets, protocols and policy

When Is a Cross-Chain Swap Really Final?

A cross-chain swap is final only after the destination transaction meets that chain’s confirmation standard; a source-side receipt or app status alone is not enough.

BitCurrent Newsroom2 min read

When Is a Cross-Chain Swap Really Final?

A cross-chain swap is final when the destination chain has recorded the received asset with the required confirmations. The source transaction getting mined starts the process; it does not prove the swap has finished.

How does a cross-chain swap move?

A swap usually has at least two on-chain steps: funds leave the source chain, then a bridge or protocol arranges a transfer or swap on the destination chain. Some routes add an intermediate chain or several transactions.

Each step has its own transaction record and confirmation process. For a closer look at how routes differ, the thor swap overview explains the trade-offs the route choice can introduce.

What counts as final?

Finality means the transaction is sufficiently settled under the destination chain’s consensus rules that it is unlikely, or in some systems effectively impossible, to be reversed. The standard varies by chain and by the bridge or protocol handling the transfer.

A transaction marked “confirmed” may still be reversible if the chain can reorganize recent blocks. Some protocols wait for a set number of confirmations; others rely on a stronger finalized status or a separate verification process. The app’s label is useful, but the underlying chain record and the protocol’s stated threshold are better evidence.

Confirmed: the source transaction was accepted, and the destination transaction appears on its chain. Still open: whether the destination has reached the finality threshold required for this route.

How can you check a swap?

Start with the source transaction ID and confirm that it is on the expected network and sent to the intended address. Then use the swap’s status page or protocol tracker to find the destination transaction ID, and check that transaction in an explorer for the destination chain.

Check the receiving address and token as well as the status. A protocol may show that it has observed the deposit or scheduled an outbound transfer before the destination transaction is confirmed. On THORChain, for example, status can pass through inbound observation, swap execution and outbound scheduling; the outbound transaction’s confirmation is the practical completion check.

For a large transfer, wait for the route’s stated destination threshold before treating funds as settled or spending them again. If no destination transaction appears, use the protocol’s official tracker or support process with the transaction IDs; do not send a second payment just because the first is delayed.