What finality means
Getting a transaction included in a block is not quite the end of the story. Until enough follow-on blocks build on top of it, there is a small chance the chain could reorganize and drop it. Finality is the point where that chance is effectively gone and the transfer is settled for good.
This is why 'confirmed' and 'final' are not always the same instant. A block can include your transaction while the network still has a slim chance of replacing that block. Waiting for finality is waiting for that chance to fall to near zero.
Two ways networks reach it
Different networks treat finality differently, and the distinction matters when a swap has to decide it is safe to release the other side.
Probabilistic finality
Proof-of-work chains like Bitcoin never declare a transaction final in a single step. Each new block built on top makes reversing an earlier one exponentially harder, so safety grows with confirmations rather than arriving at once. Six confirmations on Bitcoin is a convention, not a hard switch, and the more value is at stake, the more confirmations people wait for.
Deterministic and economic finality
Many proof-of-stake networks reach finality in a defined way. Once validators representing enough stake attest to a block, reversing it would require destroying a large amount of staked value, which is economically irrational and often punished by the protocol. That gives a clearer, faster point of no return than the probabilistic model, though the exact timing depends on the chain's design.
Reorgs, the thing finality guards against
A reorg, short for reorganization, is when the network discards one version of recent history in favor of another that has more work or stake behind it. Transactions in the dropped blocks return to pending and may settle differently or not at all. Reorgs of a block or two happen normally on some chains and are usually harmless. Deep reorgs are rare and expensive to cause, which is exactly why more confirmations mean more safety.
Finality is the guarantee that your transaction sits deep enough that a reorg cannot reach it. Before that point, treating the transfer as done is a risk. After it, the transfer is permanent.
Why swaps wait for it
A single-chain swap settles in one transaction, so its finality is just that chain's finality. A cross-chain swap is different. Value leaves a source chain and is delivered on a destination chain, and those are two separate ledgers. If the destination released before the source was final, a reorg on the source could undo the incoming leg and leave value delivered on both sides.
So a cross-chain route waits for source finality before releasing the destination asset. The wait you see is not inefficiency. It is the route refusing to deliver on one chain until the other chain's transfer cannot be reversed.
- Probabilistic chains (e.g. Bitcoin): safety grows with each confirmation.
- Faster-finality chains: reach a defined settlement point sooner by design.
- Required confirmations vary by network and by the value at stake.
- Cross-chain routes wait for the source to finalize before delivering the destination.
What that means for timing
The honest expectation for a cross-chain swap is a range set by the slowest chain in the route, not a fixed number. A route that touches a probabilistic chain waits for its confirmations. A route between faster-finality chains settles sooner. No route can safely skip the wait, and any promise of instant cross-chain settlement is glossing over the finality it still depends on.
This is why a swap can sit as pending and still be perfectly healthy. It is doing the thing that keeps both sides safe: waiting for the source to become irreversible before the destination pays out.