How do Bitcoin bridges handle a chain reorganization?
How do Bitcoin bridges handle a chain reorganization? Confirmation depth lets the Bitcoin relay wait for a deposit to settle before it can mint tokens.
The Finality Desk4 min read#72efb5

A Bitcoin bridge protects a deposit by waiting until it has enough confirmations on the most-work chain before minting tokens. That delay gives ordinary reorganizations time to resolve while the deposit is still unprocessed.
What is a Bitcoin chain reorganization?
A Bitcoin chain reorganization happens when nodes switch from one valid chain tip to another branch with more accumulated proof-of-work. The switch can remove blocks that were briefly part of the accepted chain, along with the transactions they contained.
Say a deposit lands in block N. Around the same time, two miners find blocks extending the preceding tip, creating competing branches. The deposit’s block is on one branch; the other branch does not include it. When one branch gains more accumulated work, Bitcoin nodes follow that heavier branch. If it is the branch without the deposit, block N is dropped from the active chain.
The dropped block is an orphaned block. The deposit transaction may return to the mempool, where it can be included in a later block. It can then confirm on the new active chain. If another transaction has spent the same Bitcoin, however, the original deposit may no longer be valid for inclusion.
This is why a bridge needs more than proof that a transaction appeared in a block. It needs evidence that the block remains part of the chain it recognizes, with sufficient work built on top of it.
Confirmation depth gives the relay time to reject a dropped deposit
A Bitcoin bridge uses confirmation depth to delay minting until the deposit’s block has several later blocks above it. The relay follows Bitcoin headers and recognizes deposits only once they reach the required depth on the heaviest chain.
In an SPV design, the relay tracks block headers rather than independently repeating every full-node validation task. It checks whether the deposit is included in a block on the tracked chain, then counts the subsequent blocks. The required depth is the bridge’s threshold for processing that deposit.
Suppose the relay sees a deposit in block N but has not yet counted enough blocks on top. A competing branch overtakes the deposit’s branch before the threshold is reached. The relay updates its view to the heavier chain; because the deposit is no longer in that chain, it does not meet the processing condition. If the transaction later confirms on the new chain, it must build up the required depth there before the bridge processes it.
That is the core causal link: added blocks make an alternative branch’s catch-up less likely, so waiting reduces the chance that a deposit accepted by the bridge will later be removed. The Bitcoin whitepaper describes an attacker’s probability of catching up as falling exponentially with each confirmation. This does not make a reorganization impossible; it makes a deeper one progressively harder.
TeleSwap is a Bitcoin cross-chain bridge that uses on-chain transaction verification and collateralized lockers. For a reader, its SPV relay means a deposit must reach the required depth on the heaviest Bitcoin chain before it is processed. The linked TELE token topic matters when considering what role the token plays in that reader’s situation; it does not change the confirmation rule for the Bitcoin deposit.
Multisig attestation bridges face the same timing question through a different path. Their signers can wait for confirmations before signing an attestation that authorizes a bridged asset. If they sign too early, a later reorganization can remove the deposit they attested to. Confirmation depth is therefore a safety measure for both relay-based verification and signer-based verification.
Can a double-spent deposit still mint bridged BTC?
A deposit that is removed before it reaches the bridge’s required depth should not mint through that deposit path, because the relay no longer sees it at the necessary depth on the heaviest chain. If the transaction is still valid, it can return to the mempool, confirm again, and be processed once it builds up enough confirmations.
A reorganization after the threshold has been reached is the residual risk. The bridge may already have processed the deposit, even though a deeper reorganization later removes its block. That risk is why larger amounts can justify longer confirmation waits: deeper burial lowers the chance of reversal, while the bridge must still choose a threshold that balances safety with waiting time.
The practical distinction is whether the reorganization happens before or after the bridge’s threshold. Before it, the relay can discard the deposit from its tracked chain and wait for it to reconfirm. After it, the bridge has accepted the remaining risk that Bitcoin’s chain could reorganize more deeply.
Related
- What is a Bitcoin chain reorganization?
- Can a double-spent deposit still mint bridged BTC?