Cross-Chain Bridge Risk
Definition
A cross-chain bridge is a system of smart contracts, and usually off-chain validators or relayers, that lets a token's value move between blockchains that cannot read each other directly. In the lock-and-mint design, the original token is locked in a contract on the source chain and a wrapped token is minted on the destination; burning the wrapped token releases the original. In the burn-and-mint design, the original is destroyed on the source chain and a native token is created on the destination, which only the token's issuer can authorize. Liquidity-pool bridges swap the token for a version already sitting on the destination chain. Each design adds risk the original token does not carry: the contracts can contain bugs, the validators or keys that attest to deposits can be compromised, the destination token can lose its backing, and, for a tokenized security, the bridged version may not be recognized by the issuer, may escape its transfer restrictions, or may be redeemable only after bridging back.
Why it matters
Tokenized funds and notes increasingly live on many chains, and bridges are how value moves between them. Bridges have also been among the largest sources of loss in crypto markets, because a lock-and-mint bridge concentrates the backing for every wrapped token in one set of contracts and keys. The FSB names bridge developers and maintainers among the third parties whose performance can affect platform functioning and token valuation, and describes a wrapped token as a synthetic for a token on another blockchain. For tokenized securities the stakes include legal rights as well as value: a bridged copy may not be the issuer's security, may sit outside its transfer restrictions, and may not be redeemable. Before holding a tokenized asset on a chain other than its home chain, an investor should know whether the token there is the issuer's own or a bridge's claim.
Common misconceptions
- •A bridged token is not automatically the same asset. In lock-and-mint designs it is a claim on locked collateral.
- •One-for-one backing on paper is not security. The backing is only as safe as the bridge's contracts and keys.
- •Bridges are not neutral pipes. Their validators and administrators can approve, pause or misprocess transfers.
- •Compliance does not travel automatically. A wrapper on another chain may be freely transferable even when the original is not.
- •The issuer's guarantee does not extend to wrappers it did not issue. Redemption and distributions follow the issuer's own token.
Technical details
Worked example: following the collateral and the claim
Chain A: a holder sends 10,000 fund tokens to a bridge contract, which locks them.
Bridge validators attest to the deposit; the bridge mints 10,000 wrapped tokens on chain B to the holder.
Invariant: wrapped tokens on chain B must never exceed tokens locked on chain A.
Failure: if the validators' keys are compromised, an attacker can mint wrapped tokens on chain B without a deposit, or release locked tokens on chain A without burning wrapped ones; either breaks the invariant and leaves some wrapped tokens unbacked.
The issuer's view: its register still shows 10,000 tokens owned by the bridge contract on chain A; the holder's claim runs to the bridge, not the issuer.
Bridge designs
Lock-and-mint: original locked on the source chain, wrapped claim minted on the destination; backing concentrated in the lock contract.
Burn-and-mint (issuer-authorized): original burned on the source, native token minted on the destination; requires the issuer's minting authority, keeps one supply across chains.
Liquidity pools: the bridge pays out from a pool of tokens already on the destination chain; depends on pool depth and pricing.
Verification: by an external validator set or multisignature, by light clients that verify the source chain, or by optimistic schemes with challenge periods.
Checklist before bridging a tokenized asset
Is the destination token issued by the issuer and listed among its official contract addresses?
Who verifies cross-chain messages, how many keys are needed, and who holds them?
Does the destination token enforce the same allowlist, freezes and transfer restrictions?
Can the destination token be redeemed with the issuer directly, and does it receive distributions?
What happens to destination tokens if the bridge is paused or exploited?
How investors apply the term
Investors usually apply this term by tying the definition back to the controlling documents and then asking which cash flows, rights, restrictions, or valuation assumptions it changes. A useful review looks at the term alongside fees, leverage, liquidity, reporting frequency, and manager discretion rather than treating it as a standalone concept.
The practical diligence test is simple: identify who benefits if the assumption is wrong, who has control when conditions change, and what evidence the investor receives after closing. Terms that cannot be reconciled to documents, cash movements, and monitoring data should be treated as marketing shorthand until proven otherwise.
Frequently asked questions
- What extra risks arise when a tokenized asset is bridged?
- Four kinds. Security: the bridge's contracts and the validators or multisignature keys that approve messages become a single point of failure for every bridged token. Backing: a lock-and-mint wrapped token is only as good as the locked collateral, which can be stolen or never deposited if the bridge is fooled. Recognition: the issuer may not treat the bridged token as its security, so redemption, distributions and register entries may apply only to the original. Compliance: allowlists and freezes on the source chain may not carry over to the destination.
- How have bridges failed?
- Mostly through compromised keys and verification bugs. In 2022 attackers took about $625 million from the Ronin bridge after gaining control of enough validator keys to approve withdrawals; exploited a signature-verification flaw in Wormhole to mint 120,000 wrapped ether on Solana without collateral; and drained the Nomad bridge after a faulty update let anyone pass invalid messages. In each case the wrapped tokens on the destination lost their backing or had to be recapitalized by others.
- Is a token moved by the issuer's own bridge safer?
- Usually, because the issuer controls minting on both chains and recognizes the result as the same security. Ondo's bridge, for example, uses cross-chain mint and burn through LayerZero messaging, so supply is burned on one chain and minted on the other rather than locked behind a third party's wrapper. The messaging layer remains a dependency; a forged message could mint unbacked tokens.
- Can a bridged tokenized security be redeemed?
- Only if the issuer recognizes it. Many issuers redeem only their own token on chains they list, so a holder of a third-party wrapper must first bridge back and unwrap, and must still meet the issuer's eligibility rules.