Skip to the article
Onchain Brief

News from across crypto

A confirmed bridge transfer can still be reversed

A bridge may act on a transfer before its source chain is final, so a reorganisation can leave the destination out of step with the original transaction.

The Onchain Brief Editors3 min read
A confirmed bridge transfer can still be reversed

A bridge transfer can show as confirmed and still be reversed if the source blockchain reorganises before the transfer is final. A reorganisation, or reorg, changes part of a chain’s recent history: blocks are replaced, and a transaction in the old version may disappear. The bridge may already have acted on it. That gap is why a confirmation is not always the same as finality.

Why can a confirmed transfer be reversed?

Many blockchains treat recent blocks as increasingly hard to change, rather than instantly permanent. Each new block after a transaction adds a confirmation. A competing version of the chain can still replace recent blocks if the network accepts it as the valid history. The transaction then needs to be included again, or it may no longer happen.

A bridge watches the source chain for a deposit or lock. To avoid making users wait too long, it may act after a set number of confirmations. That threshold lowers the chance of a reorg undoing the deposit, but it does not remove the chance. For a closer look at route choices and how they affect this wait, see our guide to the super bridge. The exact wait and protection depend on the bridge and the chain.

What happens if the bridge acts too soon?

If a reorg removes the source transaction after the bridge has released or created assets on the destination chain, the two chains no longer agree about what happened. The destination transfer may remain valid there, even though its source deposit is gone. That can leave the bridge short of backing, or lead it to pause transfers while it checks and repairs its records. The outcome depends on how the bridge is built; a reorg does not always mean a user loses funds.

Some bridges wait for a chain’s own finality signal. Finality means the network has accepted a block as settled under its rules, making reversal much harder than replacing a recent block. Other bridges use a confirmation count or a challenge period, during which activity can be disputed. These methods trade speed for confidence: a longer wait can reduce reorg risk, but delays access to funds.

How can you judge whether a transfer is final?

Check what the bridge means by “complete.” A destination balance may appear before the source transaction meets the bridge’s release threshold. The bridge’s status and the chain’s status can differ. Before using transferred funds, check:

  • Whether the source transaction is still present on the accepted chain.
  • How many confirmations the bridge requires, or whether it waits for finality.
  • Whether the bridge shows the transfer as settled, rather than pending or processing.
  • What the bridge says it does if a reorg occurs after it acts.

For most users, the better choice is to wait for the bridge’s stated completion point, especially before trading or sending the destination assets onward. A “confirmed” label is useful evidence that a transaction was seen. It is not, by itself, proof that the source chain can no longer change.