A crypto bridge lets you move value or information between blockchains that cannot directly process each other’s transactions. For a BTC or ETH holder, the move may introduce a new asset, contract, set of operators or pool of funds to depend on. A successful transfer does not mean those dependencies have gone away.
In October 2023, Chainlink’s security research reported an estimate of more than $2.6 billion lost to bridge exploits, citing DeFiLlama. That is a historical estimate, not a current total or a measure of the chance that any particular transfer will fail. The useful question is which failure points your proposed route introduces—and whether you need to bridge at all.
What happens when you use a bridge?
In a lock-and-mint design, an asset is locked on one chain and a representative token is issued on another. Redemption generally burns that representation before the original asset is released. Other designs burn an asset on one chain and mint it on another under their own issuance rules. In either case, check what you will receive: a token representing BTC or ETH is not the same thing as native BTC or ETH on its original chain.
A liquidity-pool bridge can pay you from funds already available on the destination chain, rather than issuing a wrapped token for that transfer. Its ability to complete a transfer depends in part on destination liquidity and its settlement rules. A message-passing bridge relays instructions between chains; those instructions may move tokens or trigger other contract actions. Chainlink’s bridge risk documentation explains the different trust assumptions behind bridge designs.
Before using any route, find out who or what verifies that the event on the source chain occurred. For a wrapped asset, backing also depends on sound contracts, control of keys, accurate verification and workable redemption rules—not just a stated reserve balance.
Where can a transfer go wrong?
- Keys and signers: An attacker who gains enough signing authority may approve a transfer or withdrawal that never had a valid source-chain event. Ask how many independent parties must sign and who can change that arrangement.
- Contracts and messages: A validation, replay-protection or accounting error can let an invalid message through or put funds at risk. An audit may identify some problems, but it cannot rule out every bug or prevent stolen keys.
- Off-chain services: Some designs rely on relayers, watchers or other services to carry or challenge messages. Understand what happens if those services fail or report incorrect information.
- Liquidity and redemption: A token may arrive but be difficult to redeem, or a pool may lack enough funds for the intended payout. Check the exit route as well as the deposit route.
- Timing and finality: A bridge must decide when to treat a source-chain event as sufficiently settled. If it acts on an event that is later reversed, its accounting may no longer match what happened on the source chain.
These risks sit on top of ordinary wallet risks. A fraudulent bridge website, wrong destination address or overly broad token approval can cause loss even if the bridge protocol itself works as designed.
How do verification models differ?
A light-client approach checks source-chain evidence on the destination chain, reducing reliance on a separate group’s assertion. It can be complex and costly to implement and still depends on correct code and sound assumptions about the chains involved. An external-validator or multisignature approach instead asks designated signers to attest to events; assess their independence, signing threshold and powers. In an optimistic approach, a message can proceed unless a valid challenge is raised within a dispute window, so the challenge process and active watchers matter.
Finality is another design-specific question. On a chain with probabilistic finality, additional confirmations generally reduce—but do not mathematically eliminate—the prospect of a reversal. Other chains have different finality rules, which a bridge must apply correctly. Imagine, for example, a bridge requiring approval from five external signers while also accepting deposits before a source chain reaches the confirmation level you expect: those are two separate assumptions to investigate, not evidence of an actual incident. For more detail on verification and related risks, see Cross-chain bridges and associated risks — Chainlink Docs.
A pre-transfer checklist for BTC and ETH holders
- Ask whether the move is necessary. If you only want to hold BTC or ETH, remaining on its native chain avoids adding a bridge. If a destination-chain activity is the goal, assess that activity’s risks separately.
- Identify the exact asset and route. Confirm the source and destination chains, token contract, recipient address, expected asset on arrival, fees and how you would move or redeem it later. Use trusted project documentation rather than a link sent in a message.
- Read the security model. Check who verifies transfers, who controls upgrades or emergency pauses, whether audits are public, and whether there have been incidents. If you cannot establish the route’s operating rules, consider waiting or not using it.
- Check the guardrails and their limits. Rate limits may restrict the scale of certain losses if correctly configured and enforced. A pause may stop further damage but can also delay your withdrawal. One provider’s monitoring and rate-limit design is described in Chainlink CCIP’s Defense-In-Depth Security and the Risk Management Network; it is an example, not a guarantee for other bridges.
- Secure the transaction you control. Verify the destination and transaction details in your wallet, protect signing keys, and review token approvals. Keeping a bridge-use address separate from long-term holdings can limit the funds exposed to a mistaken approval.
- Consider a small test and a complete exit test. Check that the expected asset arrives and, where practical, that redemption works. A test costs network and bridge fees and only checks the route at that moment; it does not establish that a later, larger transfer will be safe.
Do not let a promised yield make the bridge step disappear from your risk assessment. If capital is deployed after bridging, assess fees or other income alongside changes in position value, exit costs and every added dependency. Borrowing instead of bridging is not a risk-free shortcut: a crypto-backed loan adds interest, collateral and liquidation risk. The guide to crypto-backed loans explains that separate decision.
What do past failures tell us about wider risk?
A failure can affect more than the first bridge user: people holding a representative token or relying on a connected protocol may also be exposed. But an incident on one route does not establish the safety or failure probability of every other route.
A 2023 Federal Reserve Board staff working paper by Anton Badev and Cy Watsky reports an association between greater bridge exposure to Terra and a greater likelihood of declining TVL share during the Terra-collapse period. That observation is relevant to how stress may spread across connected ecosystems; it does not prove that a bridge failure caused each decline.
In a presentation to the Office of Financial Research Advisory Committee, Greg Hopper discussed possible DeFi contagion and proposed safeguards including audits, monitoring and withdrawal lockup periods tied to transaction size. The presentation is Hopper’s, not research authored by the Office of Financial Research. His November 2022 presentation, DeFi: New Risks Require New Regulation, is available here: DeFi: New risks require new regulatory and risk-management approaches — OFR/FRAC.
OverseasDeFi’s Hold → Borrow → Deploy → Earn framework is a way to examine decisions, not a reason to take every step. When a strategy involves a bridge, consider its exposure alongside any borrowing, position value and potential income. Portfolio tools and guidance can help frame the questions, but they cannot verify every route or prevent a loss. The learning library covers related DeFi decisions.
FAQ
Is a bridged version of BTC or ETH the original asset?
Usually not. A token issued on another chain may represent a claim tied to BTC or ETH, but its value and redemption depend on the particular bridge’s rules, reserves and security. Check the exact token and exit path before accepting it.
Does an audit make a bridge safe?
No. An audit examines a defined version and scope of code. It cannot guarantee that the code is bug-free, that signing keys will remain secure or that operators will handle an incident well.
Will a small test transfer protect a larger transfer?
A test can catch some address, routing or redemption mistakes at the time you make it. It cannot predict a later exploit, liquidity shortage, rule change or outage.
When should I choose not to bridge?
Consider staying on the original chain if you cannot identify what you will receive, how you will exit, who can authorize transfers or changes, and what loss you could bear. You do not need to bridge simply because a destination-chain opportunity is available.