Home / Wiki / T / Token Bridge Risk

Token Bridge Risk

Share

Token bridge risk is the risk that value is lost or frozen when tokens are moved from one blockchain to another through a token bridge. Because blockchains cannot directly read each other's state, a bridge holds or controls assets on one chain and issues a matching claim on another. That arrangement concentrates large pools of value in a small set of contracts and keys, which has made bridges among the most frequently attacked parts of the crypto industry.

The risk falls on several groups: users who send tokens across, holders of wrapped tokens issued by the bridge, protocols that accept those wrapped tokens as collateral, and the bridge operators themselves. It is a central concern in blockchain interoperability, where the goal is to connect chains without creating a single weak point.

01

How bridges create risk

Most bridges follow one of a few models. In lock-and-mint, the original tokens are locked in a contract on the source chain and wrapped versions are minted on the destination chain. In burn-and-mint, tokens are destroyed on one chain and created on the other, a method often used by issuers for their own tokens. Liquidity-network bridges instead hold pools of the token on each chain and pay out from the destination pool, so no wrapped asset is created.

Each model depends on some mechanism to confirm that an event really happened on the other chain. That mechanism may be a group of external validators or a multisignature committee that signs off transfers, an optimistic design that accepts messages unless someone submits a fraud proof within a challenge window, or a light-client or zero-knowledge proof system that verifies the other chain's state directly. The fewer and more centralised the parties that must be trusted, the greater the risk if they fail or are compromised.

02

Main types of bridge risk

  • Smart contract bugs. A flaw in the bridge contract can let an attacker mint tokens without a matching deposit or release locked funds. Code is usually reviewed through a smart contract audit, but audits do not catch every error.
  • Key and validator compromise. If attackers gain enough signing keys, they can approve fraudulent withdrawals that look valid to the contract.
  • Upgrade and administrative control. Many bridges can be changed by an admin key or governance vote, so a faulty upgrade or a stolen key can break the system. This is part of the wider question of smart contract upgradeability.
  • Wrapped-token depegs. If the locked assets are stolen, wrapped tokens on the other chain are no longer fully backed and may depeg, spreading losses to every protocol that holds them.
  • Liquidity and finality risk. Liquidity-network bridges can run short of funds on one side, and transfers from chains with weak finality can be reversed by a chain reorganisation after the destination has paid out.
03

Notable bridge hacks

Several of the largest thefts in crypto history have targeted bridges. In February 2022, an attacker exploited a signature verification flaw in the Wormhole bridge between Solana and Ethereum to mint about 120,000 wrapped ether without depositing the collateral, a loss then worth roughly USD 320 million that was later replaced by a backer of the project. In March 2022, attackers obtained five of the nine validator keys controlling the Ronin bridge used by the game Axie Infinity and withdrew assets worth more than USD 600 million; US authorities attributed the attack to North Korea's Lazarus Group. In August 2022, a routine upgrade to the Nomad bridge left a check misconfigured so that almost any message was accepted, and hundreds of addresses copied the original exploit to drain about USD 190 million.

These cases show the three main failure routes: a code bug, compromised keys and a faulty upgrade. In each, the loss fell first on the bridge's locked funds and then on holders of the wrapped tokens it had issued.

04

Managing and reducing the risk

Bridge designers try to reduce risk by spreading validation across more independent parties, using proof-based verification instead of trusted signers, adding rate limits that cap how much can leave in a given period, and building pause functions that halt transfers when anomalies appear. Many run bug bounty programmes and publish audits. Users and institutions manage their exposure by preferring tokens issued natively on each chain, limiting the amount held in wrapped form, checking how a bridge is secured before using it and treating bridged assets as carrying the credit risk of the bridge itself. Risk teams at exchanges and lending protocols often apply lower collateral values to bridged tokens than to native ones for this reason.

The risk cannot be removed entirely while chains remain separate systems. Every cross-chain transfer relies on some party or proof to vouch for what happened elsewhere, and the security of the transfer is only as strong as that link.

Last updated 17 Nov 2026
Share this entry

Ref 1070001020