This space is available Advertise with CryptoOverlook → 160 × 600
This space is available Advertise with CryptoOverlook → 160 × 600
This space is available Advertise with CryptoOverlook → 728 × 90

Foundations

Crypto Bridges Explained (and Why They Keep Getting Hacked)

How cross-chain bridges move assets between blockchains, why they've become one of crypto's most attacked pieces of infrastructure, and what to check before using one.

Why bridges exist at all

Most blockchains can’t natively talk to each other. Bitcoin’s network has no built-in way to know what’s happening on Ethereum, and Ethereum has no built-in way to know what’s happening on Solana; each is its own self-contained ledger with its own rules and validators. But plenty of people want to move value between them, take an asset that lives on one chain and use it on another, whether that’s to access a DeFi protocol, chase lower fees, or reach an app that only exists on a different network. A cross-chain bridge is the infrastructure that makes that possible.

How a bridge actually works

Bridges vary in mechanism, but the common designs fall into a few categories.

Lock-and-mint bridges lock your original asset in a smart contract on the source chain, then mint a corresponding “wrapped” version of that asset on the destination chain. That wrapped token is meant to be redeemable for the original, one-to-one, and the bridge’s job is to guarantee that redemption always works. When you move it back, the wrapped token is burned and the original is unlocked.

Burn-and-mint bridges destroy (burn) the asset on the source chain entirely and mint a native equivalent on the destination chain, rather than locking it. This is more common for assets natively designed with a specific bridge in mind.

Liquidity-pool-based bridges skip locking and minting altogether. Instead, they maintain pools of the same asset on both chains, and moving your asset across is really a swap: you deposit into the source-chain pool and withdraw from the destination-chain pool, similar in spirit to the AMM mechanism covered in What DeFi and a DEX Actually Are.

Across all of these, someone or something has to verify that a deposit actually happened on the source chain before releasing funds on the destination chain. That verification might be done by a small set of trusted validators (a “federated” or “trusted” bridge), a broader decentralized validator set, or, on Layer 2 networks specifically, cryptographic proofs tied to the underlying chain itself, a mechanism covered in What Are Layer 2s.

Why bridges are such a common attack target

Bridges have an unusually dangerous property: they concentrate enormous value in one place. To let assets move freely between chains, a bridge typically has to hold a large pool of locked funds, or grant a validator set the authority to mint or release assets on demand. That combination, a lot of value plus a relatively small, well-defined set of contracts or keys controlling it, makes a bridge an unusually attractive target compared to, say, a single user’s wallet or even a typical DeFi protocol. An attacker doesn’t need to compromise thousands of individual users; compromising one bridge’s validator set or exploiting one flaw in its verification logic can be worth hundreds of millions of dollars in a single event.

Several of the largest hacks in crypto’s history have been bridge exploits specifically for this reason:

  • Ronin Bridge (March 2022): attackers compromised enough of the bridge’s validator keys, five out of nine, to forge withdrawal approvals, draining approximately $625 million. Ronin was the bridge underlying Axie Infinity, the blockchain game discussed in Web3 Gaming and GameFi; the attack has since been publicly attributed by the FBI to North Korean state-linked hackers.
  • Wormhole (February 2022): an attacker exploited a signature-verification flaw to mint wrapped ETH on Solana without actually depositing the corresponding ETH, resulting in a loss of roughly $325 million. Wormhole’s backer covered the shortfall to make users whole, which isn’t the outcome of most bridge hacks.
  • Poly Network (August 2021): an attacker exploited a contract vulnerability to drain around $611 million across multiple chains, making it one of the largest crypto hacks ever recorded at the time. Unusually, the attacker returned nearly all of the funds afterward, in a case that’s still cited as one of the rare instances of a large-scale hack ending without lasting losses.

Most bridge hacks don’t end that way. The common thread across nearly all of them isn’t sloppy branding or an obviously untrustworthy team; several of these bridges were well-known, widely used infrastructure at the time they were exploited.

What to check before using a bridge

Bridges aren’t uniformly risky, but the practical questions are similar to evaluating any other piece of DeFi infrastructure, discussed more generally in How to Evaluate a DeFi Protocol Before Depositing Funds:

  • Audit history: has the bridge’s contract code and validator logic been reviewed by a reputable security firm, and are those audits current for the deployed version?
  • Track record: how long has the bridge processed real volume without a major incident? A bridge that’s moved billions of dollars over years without an exploit has meaningfully more evidence behind it than one that launched recently, however well it’s marketed.
  • Trust model: is it a federated bridge relying on a small set of known validators (faster, but a smaller attack surface to compromise, as Ronin demonstrated), or a more decentralized design with a larger, more distributed validator or proof system? Neither model is automatically safer; each has different failure modes worth understanding before moving meaningful funds through it.
  • How much value it secures relative to its security budget: a bridge holding far more value than its own team or backers could realistically make whole in a worst-case scenario is a specific, checkable risk factor, not just a hypothetical one.

None of this guarantees safety. It reduces the odds of using a bridge with an obviously avoidable weakness, which is the most any due-diligence checklist can honestly claim.

Frequently asked questions

Is it safer to just avoid bridges entirely? For most casual users, minimizing how often you bridge assets, and how much value you move at once, is a reasonable practical habit, similar to not leaving large amounts on an exchange you don’t need to actively use. But bridges are also genuinely necessary infrastructure for a lot of legitimate activity across chains, so “avoid entirely” isn’t realistic advice for anyone actively using multiple networks.

Are wrapped tokens the same as the original asset? Not exactly. A wrapped token is a claim on the original asset, backed by whatever the bridge is holding in reserve. Its value depends entirely on the bridge’s ability to honor redemptions; if a bridge is hacked or insolvent, wrapped tokens issued through it can become worth significantly less than the original asset, even if the original asset’s price hasn’t moved at all.

Why don’t bridges just get more decentralized to fix this? Some do move in that direction over time, but decentralizing a bridge’s validator set doesn’t automatically make it safer; a poorly designed decentralized system can still have exploitable logic, and a federated one with careful key management and monitoring can operate for years without incident. Trust model is one factor among several, not a single fix.

Is a Layer 2’s native bridge to its underlying chain the same kind of risk as a third-party cross-chain bridge? Not exactly the same. A rollup’s canonical bridge back to its base chain typically relies on the base chain’s own security and cryptographic proofs rather than a separate validator set, which is a different (often stronger) trust model than many third-party bridges. The mechanics are covered in What Are Layer 2s.

Risk

Nothing on this page is financial advice, and it is not a complete or current statement of any specific bridge’s security or audit status. Bridges have historically been a common target for large-scale hacks, and using one carries the risk of partial or total loss of the funds being moved. Do your own research before making any decisions based on this page.

This space is available Advertise with CryptoOverlook → 728 × 90