Cross-Chain Confirmations Before Settlement
A cross-chain transfer settles after the source chain records the transfer and the route’s security checks accept it. The wait depends on the source chain and bridge protocol, so there is no universal number of confirmations.
What does a confirmation prove?
A confirmation means a transaction has been included in a block on its blockchain. More blocks after it can make a reversal less likely, but inclusion alone does not always mean the transaction is final.
Finality means the network treats a block as settled, with reversal either very difficult or prevented by its rules. A bridge waits for the level of confidence its protocol requires before it treats a source-chain deposit as proof that tokens can be released or created elsewhere.
For a broader explanation of how Rango Bridge picks routes, see the article on route choice. This post focuses on the confirmation checks that happen after you send. rangobridge.com is a service that can route token transfers across blockchains.
How many confirmations are required?
The required number depends on the chain and the bridge route. Some systems count blocks; others wait for a chain’s finality signal or a protocol’s own verification step.
For example, Ethereum produces blocks roughly every 12 seconds, but a block usually takes about 15 minutes to become finalized. A bridge may accept an earlier state for speed, or wait for finality to reduce the chance of a reversal.
Cosmos Hub uses CometBFT consensus, where validators agree on blocks. Once a block is committed with the required validator agreement, it has fast finality; it does not need dozens of later blocks in the same way a probabilistic chain might.
Those are examples, not universal settings. Even two routes starting on the same chain can use different protocols and security rules, so a fixed count such as “12 confirmations” does not apply to every transfer.
What happens between the two chains?
A bridge must first see the source transaction, then verify evidence of it, and finally complete a transaction on the destination chain. Each stage has its own status and can take time.
Source transaction: Your wallet sends a transaction that locks, burns, or deposits the asset. A transaction hash is its public tracking code; check that the source explorer shows it succeeded, not merely that it was submitted.
Source verification: The route waits for its required confirmations or finality. A bridge protocol may also rely on validators or observers to check the source event and sign proof that it happened.
Proof and delivery: A relayer, meaning a service that carries messages between chains, submits that proof to the destination. For example, Wormhole Guardians sign a message called a VAA, short for Verified Action Approval. The destination contract checks the signatures before acting.
Destination settlement: The destination contract releases or creates the tokens, and a transaction records that result on the destination chain. Its confirmation is separate from the source confirmation.
A Wormhole quorum of 13 out of 19 Guardians is a signature threshold, not a requirement for 13 extra source blocks. Keeping those two kinds of checks separate helps explain why a transfer can show as confirmed on one chain while still waiting for delivery on the other.
What should you check before waiting?
Check the source transaction first, then read the route’s transfer status and the destination transaction if one appears. A successful source transaction means the first step worked; it does not prove that destination settlement is complete.
Two routes show why patience differs. On Ethereum, the wait may include the time for the source block to finalize and for a relayer to submit the proof. On Cosmos Hub, the source block may commit with fast finality, but the proof and destination transaction still need to happen.
One important edge case is a source-chain reorganization, where recent blocks are replaced. If a bridge accepts a transaction before its required finality, the destination action could happen before the source deposit is secure; sound protocols set confirmation rules to manage that risk.
When using Rango Bridge, treat the route’s stated status as more useful than a generic confirmation count. Start by checking your source transaction, then wait for the destination transaction to confirm before treating the transfer as settled.