What Is a Crypto Bridge, and Why Are They Risky?

The Problem Bridges Solve

Blockchains are sovereign systems. Ethereum does not natively know what is happening on Solana. Bitcoin has no built-in mechanism to interact with smart contracts on Avalanche. Each chain maintains its own ledger, validates its own transactions, and follows its own rules. This isolation is a feature from a security standpoint — the failure of one chain cannot propagate to another — but it creates friction for users and developers who want to move value across ecosystems.

A crypto bridge is a protocol that enables the transfer of assets or data between two blockchains. The most common use case is moving a token from one chain to another: a user deposits an asset on the source chain, and the bridge issues a corresponding representation of that asset on the destination chain. When the user wants to return, the destination token is burned or locked, and the original is released.

Bridges have become essential infrastructure for decentralised finance. Without them, liquidity would remain siloed within individual chains, limiting the composability that makes multi-chain DeFi possible. Major bridges process billions of dollars in volume monthly.

How Bridges Work in Practice

The mechanics vary, but most bridges fall into a few broad categories. Lock-and-mint bridges hold the original asset in a smart contract on the source chain and issue a wrapped version on the destination chain. The wrapped token is a liability: it represents a claim on the locked original. The security of the entire system depends on the integrity of that locked pool.

Liquidity network bridges work differently. Instead of locking and minting, they maintain pools of native assets on multiple chains and use solvers or relayers to match transfers. The user deposits on one side and receives a native asset on the other side, funded by a liquidity provider. This approach avoids large centralised locked pools but introduces counterparty and liquidity risk.

Native or canonical bridges are built by the chain or rollup itself — the Arbitrum bridge and the Optimism bridge, for example, are canonical paths between Ethereum and their respective Layer 2 networks. These typically benefit from closer alignment with the underlying security model but may have longer withdrawal periods by design.

Bridges also differ in their trust assumptions. Some rely on centralised operators or multi-signature wallets controlled by a small group of parties. Others use cryptographic proofs — zero-knowledge or optimistic — to minimise the trust required. The spectrum from highly trusted to trustless is wide, and the distinction matters enormously for security.

Why Bridges Attract Exploits

Bridges represent concentrated targets. A lock-and-mint bridge that has processed significant volume holds a large pool of assets in one smart contract or set of contracts. If the contract logic has a vulnerability, or if the key management for a multi-signature wallet is compromised, an attacker can drain that pool entirely. The losses are not distributed across the network — they are concentrated at the point of failure.

Several of the largest losses in DeFi history have occurred at bridges. The Ronin bridge exploit in 2022 resulted in the loss of approximately $625 million. The Wormhole exploit in the same year cost around $320 million. The Nomad bridge was drained of approximately $190 million. In each case, the attack vector differed — compromised validator keys, a logic error in signature verification, an upgradeability flaw — but the structural vulnerability was the same: a large pool of assets guarded by code or key holders that proved fallible.

Cross-chain communication also introduces oracle and timing risks. Bridges must reliably observe events on one chain and act on another. If the mechanism for verifying those events can be spoofed, replayed, or front-run, the system can be manipulated. The complexity of coordinating two independent blockchains multiplies the attack surface compared with a single-chain application.

Evaluating Bridge Risk

Users and developers interacting with bridges should assess several factors. Audits: has the codebase been reviewed by multiple independent security firms, and how recently? Trust model: how many parties must be compromised for the bridge to fail — one key holder, a quorum of validators, or a cryptographic assumption? Track record: has the bridge operated without incident through periods of high volume and market stress?

Time locks and withdrawal delays, while inconvenient, provide a window for detecting and responding to anomalous transactions before funds leave the system. Some bridges have implemented circuit breakers that pause operation if outflows exceed a threshold within a given period. These are meaningful security features, not mere friction.

The bridge risk profile is also relevant when evaluating wrapped assets. A token labelled “wrapped ETH” on a given chain is only as secure as the bridge that issued it. If that bridge is exploited, the wrapped token may lose its peg. For a glossary of bridge-related and DeFi terminology, see the glossary.

Bridges are not inherently unsafe, but they operate at the hardest boundary in blockchain architecture. The industry has learned from costly failures, and newer designs with stronger cryptographic foundations represent meaningful progress — though no system that holds large pools of assets under adversarial conditions should be treated as risk-free.