Crypto Bridges Explained: How Cross-Chain Transfers Work, and Why They're a Top Hacking Target

Blockchains are, by design, isolated systems. Bitcoin's ledger does not know what happened on Ethereum, and Ethereum has no native awareness of activity on Solana, Avalanche, or any of the dozens of layer-2 networks built on top of it. That isolation is good for security and decentralization, but it creates a practical problem: crypto users increasingly want to move value and data between these separate systems. A blockchain bridge is the piece of infrastructure built to solve that problem.

What a bridge actually does

In most cases, a bridge does not literally teleport a token from Chain A to Chain B. Instead, it uses one of two common mechanisms. The first is lock-and-mint: a user deposits an asset, say ETH, into a smart contract on the source chain, where it is locked up. The bridge then instructs a corresponding smart contract on the destination chain to mint a new, wrapped token, such as a wrapped ETH, that represents a claim on the locked original. The second is burn-and-mint: instead of locking the asset, the bridge destroys, or burns, the token on the source chain and mints an equivalent amount on the destination chain. A smaller category, liquidity network bridges, skips wrapping entirely by pairing users who want to swap assets across chains with liquidity pools that hold native tokens on both sides, similar to how a decentralized exchange matches trades.

The practical effect for a user is usually the same: assets that started on one network show up, in some form, on another. What differs underneath is who, or what, is responsible for verifying that the lock, burn, or mint actually happened correctly, and that is where the risk profile of different bridges diverges sharply.

Trusted versus trustless designs

• Custodial or federated bridges rely on a company, consortium, or a small, permissioned set of validators to watch the source chain and authorize minting on the destination chain. Users must trust that this group is honest and that its signing keys are secure.
• Light-client or trustless bridges attempt to verify cross-chain events using cryptographic proofs that can be checked on-chain, without relying on a trusted third party, though these designs are more complex to build and audit.
• Optimistic bridges post a bond and allow a challenge window during which anyone can dispute a fraudulent transfer, borrowing the fraud-proof model used by some layer-2 rollups.
• Liquidity network bridges reduce custody risk because no large pool of locked assets sits in a single contract, but they depend on sufficient liquidity being available on both sides of a transfer.

Why bridges keep getting hacked

The lock-and-mint and burn-and-mint models both require a large pool of locked value, or a validator set with authority to approve minting, to sit in one place. That concentration makes bridges an attractive target. A flaw in the smart contract code, a compromised validator key, or a manipulated oracle feeding bad data into the bridge can let an attacker mint wrapped assets without ever depositing the real underlying collateral, or drain the locked reserve outright. The US Cybersecurity and Infrastructure Security Agency, the FBI, and the Treasury Department have jointly warned that state-linked hacking groups have specifically targeted blockchain bridges and related infrastructure, citing the sector's technical complexity and the scale of funds often held in a single contract. Chainalysis, a blockchain analytics firm that publishes an annual crypto crime report, has similarly tracked cross-chain bridge exploits as a recurring category of large-scale hacks in the broader digital asset ecosystem.

What this means for everyday users

Most retail investors encounter bridges indirectly, for example when moving stablecoins to a layer-2 network to pay lower transaction fees, or when acquiring a token that only exists on a chain different from the one they are using. The wrapped asset received at the end of a bridge transaction is only as reliable as the bridge that issued it; if the bridge's reserves are compromised, the wrapped token can lose its backing even if the original underlying asset elsewhere is untouched.

• Check whether the bridge has undergone independent smart-contract audits, and whether those audits are recent and publicly available.
• Look at how long the bridge has operated without a halted withdrawal, exploit, or governance emergency.
• Understand whether you are using a trusted, federated bridge or a more decentralized, proof-based design, since the risk model differs.
• Avoid moving funds through a bridge, or holding a wrapped asset, in amounts larger than you would be comfortable losing entirely, given that bridge exploits have historically been difficult or impossible to reverse.