Finality determines when a cross-chain swap can safely use the source funds, because the destination network must be able to trust that the source transaction will not be reversed. A transaction that appears in a wallet or has an initial confirmation may still be provisional, so a bridge often waits for a stronger settlement signal before acting.
What does finality mean for a wallet transfer?
Finality is the point at which a network treats a transaction as settled under its consensus rules. Before then, a block may be replaced during a chain reorganisation, or “reorg,” which can remove a transaction that looked successful a moment earlier.
A centralised exchange can credit an internal balance according to its own checks; with a wallet-based service such as super bridge, a source-chain transaction must be observed and accepted before a destination-chain action can rely on it. The bridge connects the two networks, but each network decides what counts as settled on its own ledger.
“Confirmed” and “finalized” do not always mean the same thing. A confirmation usually means a transaction has been included in a block; finality means the network’s consensus has reached a stronger threshold. The number of confirmations a bridge requires, or the finality signal it accepts, depends on its design and the source chain’s security model.
How does source finality enable the destination swap?
A cross-chain swap usually has several linked stages: the wallet submits a transaction on the source chain, a bridge system verifies the resulting event, and a destination transaction then releases or swaps the corresponding assets. That verification can involve validators, relayers, or other bridge components checking source-chain evidence. The destination action should not execute merely because someone has seen the source transaction.
For example, suppose you send ETH from Ethereum and want a different asset on another network. The source transaction may be included in a block first, but the bridge may wait for Ethereum’s proof-of-stake finality: validators representing at least two-thirds of staked ETH must support the relevant checkpoints. Ethereum’s slots last 12 seconds and its epochs contain 32 slots; under normal operation, finality takes around 13 minutes. The bridge then needs to verify the event and submit the destination transaction, which must also be included on that network.
That means “one flow” does not mean one atomic transaction spanning both chains. The source transfer and destination swap settle under separate rules, and the bridge coordinates them. Your wallet may show the source transaction as successful while the destination transaction is still waiting to execute.
Why can the wait differ between networks?
Finality is defined by each network’s consensus, so a bridge cannot apply one universal confirmation count or wait time. Ethereum’s checkpoint-based finality gives a clear settlement milestone but normally takes minutes. Solana uses a different process: a transaction is finalized when its block becomes a root after receiving supermajority support. A bridge’s verification policy and network conditions affect when it treats that evidence as sufficient.
There is a trade-off. A bridge that acts on an earlier, weaker signal can complete sooner, but it accepts more risk that the source transaction could be replaced or invalidated. Waiting for a stronger finality signal reduces that exposure but adds time. The practical criterion is the bridge’s source-chain acceptance rule, not the number of confirmations you are used to seeing at an exchange.
What should you check while the swap is pending?
Before signing, confirm that the source wallet has enough of the source asset for the transfer and its network transaction cost. Then keep the source transaction identifier. It lets you distinguish a transaction that is still awaiting inclusion from one that has been included but has not reached the bridge’s finality threshold.
Imagine the source transaction appears in your wallet, but the destination asset has not arrived. That can be normal if the source block is still provisional, the bridge is verifying it, or the destination transaction is waiting for inclusion. If the source transaction is dropped or replaced before finality, the bridge cannot safely treat its event as settled; you may need to check the transaction’s actual status before deciding what to do next.
After source finality, a destination delay is a separate stage: the bridge must submit its action, and the destination network must process it. So when estimating completion, think of the elapsed time as source settlement plus bridge verification and relaying plus destination inclusion. A source-side “success” is an important milestone, but it is not by itself proof that the cross-chain swap has finished.