Where are your coins while they cross the bridge?
When you bridge assets, coins leave the source chain and, minutes or hours later, a token with the same name appears on the destination chain. Where are the assets in between, and who checks what before the destination chain issues the token?
This guide follows a bridge transfer step by step, explaining what each stage waits for and what can go wrong. It then looks at how canonical bridges run by rollups differ from third-party bridges, how to check withdrawals and liquidity, and why funds are so hard to recover after an incident.
What a bridge connects
Blockchains cannot read each other's state directly. A bridge carries a message from the source chain saying that something happened, and a contract on the destination chain acts on that message. Ethereum.org's documentation on bridges describes them as the means of moving assets and information between different blockchains.
In the common lock-and-mint design, the original asset is locked in a bridge contract on the source chain, and a wrapped token backed by it is minted on the destination. The wrapped token's value therefore depends on the assets locked on the source chain and on whoever verified the message in between.
A hypothetical transfer route
The table follows a hypothetical transfer of 1 ETH from Ethereum to another chain through a third-party lock-and-mint bridge.
| Stage | Time (assumed) | What happens | Main risk at this stage |
|---|---|---|---|
| 1. Deposit on source chain | Tens of seconds | 1 ETH locked in the bridge contract | Fake bridge site, wrong network selected |
| 2. Wait for source finality | About 13 minutes | Wait until the deposit cannot be reversed | Reorganization before finality |
| 3. Message observed and relayed | A few minutes | Relayers pass the deposit record to the destination | Delays, operator outage |
| 4. Validator signatures | A few minutes | A threshold of validators (e.g., 3 of 5) approves | Stolen validator keys, signature-verification bugs |
| 5. Mint on destination | Tens of seconds | 1 wrapped ETH minted | Minting-contract bugs, abuse of admin powers |
The whole transfer takes about 20 to 30 minutes, mostly waiting for source-chain finality. The largest historical incidents happened at stages 4 and 5, verification and minting.
Locking, burning, and verifying messages
Bridges wait for source-chain finality because if a deposit were reversed after tokens were minted on the destination, those tokens would have no backing. As Ethereum.org's FAQ on finality explains, Ethereum usually finalizes in about two epochs, roughly 13 minutes, but other chains differ.
Who verifies the message is the heart of a bridge. A small validator set is fast and simple, but if enough keys to meet the threshold are compromised, an attacker can approve a fake deposit message and mint unbacked tokens. Designs that prove the source chain's state cryptographically require trusting fewer parties but are complex to build.
Canonical versus third-party bridges
Networks that settle to Ethereum, such as rollups, usually run their own canonical bridge. It shares the rollup's security model, but for an optimistic rollup, returning to Ethereum means waiting out a challenge period of roughly seven days.
Third-party bridges are faster and connect many chains, but they require trusting a separate validator set or liquidity providers. Take a hypothetical example: choosing a third-party bridge that takes 20 minutes over a canonical one that takes seven days means taking on another party's risk in exchange for the time saved.
Checking withdrawals and liquidity
Returning a wrapped token to the original chain means going through the reverse process. Check in advance that the bridge contract holds enough of the original asset, and whether there are withdrawal limits or pause conditions.
Liquidity-network bridges may be unable to move large amounts, or may charge much more, when liquidity on the destination side runs low. If you plan to move a large sum, check the bridge's liquidity and per-transfer limits first.
Why recovery is so hard
Stolen bridge funds are very hard to recover. Attackers move assets quickly across chains and through mixers, and blockchain transactions cannot be reversed. Some projects announce compensation plans, but full repayment is rare and legal claims are complex. The CFTC warns that virtual currency platforms can be exposed to hacking and operational disruption.
Bridge risk is therefore better managed by limiting exposure beforehand than by planning for recovery afterward. Bridge only what you need for as long as you need, and consider swapping wrapped tokens for native assets or issuer-minted tokens on the destination chain rather than holding the wrapped version for long.
Before you transfer
Work through these checks before bridging assets.
- Check whether a canonical bridge exists and how long its withdrawals take.
- For a third-party bridge, read the official documentation on how messages are verified (signer count and threshold, or proof system) and who holds admin powers.
- Confirm the bridge site through an official channel, and match the source network, destination network, and contract address of the token you will receive.
- Check the bridge's liquidity, per-transfer limits, and pause conditions.
- Start with a small transfer, confirm it arrives, and decide separately whether to keep holding the wrapped token afterward.