Blockchain bridges are protocols that enable transferring assets and data between different blockchain networks. Since Ethereum, Solana, Arbitrum, and other chains are independent networks that can't natively communicate, bridges serve as the connective tissue of the multi-chain ecosystem. When you bridge ETH from Ethereum to Arbitrum, a bridge locks your ETH on Ethereum and mints an equivalent wrapped version on Arbitrum — creating a cross-chain representation of your assets.
Lock-and-mint bridges (most common) lock assets on the source chain and mint wrapped tokens on the destination chain. Burn-and-mint bridges destroy tokens on one chain and create them on another. Liquidity network bridges (like Across and Stargate) use pools of native assets on each chain, avoiding wrapped tokens entirely — providing better execution but requiring liquidity on both sides. Messaging protocols (Wormhole, LayerZero) enable general cross-chain communication beyond just token transfers.
Bridges have been the most exploited category in crypto — the Ronin Bridge hack ($625M), Wormhole hack ($320M), and Nomad hack ($190M) collectively lost over $1 billion. Bridges are attractive targets because they hold large pools of locked assets and their security depends on complex cross-chain verification that's difficult to audit comprehensively. When using bridges, stick to official chain bridges (Arbitrum Bridge, Optimism Bridge) or well-established third-party bridges with strong security track records.
Always use official bridge interfaces and verify URLs carefully. Compare bridge fees and speed using aggregators like Bungee or Socket. For small amounts, centralized exchanges can serve as bridges — withdraw from one chain, deposit to another. Keep some native gas tokens on each chain you use (ETH for Ethereum, AVAX for Avalanche, etc.) to pay transaction fees. And never bridge more than you can afford to lose to any single bridge — spread large transfers across multiple bridges or time periods to manage risk.
Bridges use different architectural approaches with very different security profiles. Lock-and-mint bridges hold the source asset on the original chain and mint a wrapped representation on the destination — the wrapped token's value depends on the bridge contract holding the original. Burn-and-mint works similarly but destroys tokens on the source chain. Liquidity network bridges (Across, Stargate) use pools of tokens on both chains and enable swaps without minting wrapped versions. Native bridges (Arbitrum's, Optimism's) inherit the security of the underlying L2's settlement to L1, generally the most secure option for assets moving between specific networks. Light client bridges verify state across chains using cryptographic proofs without trusted intermediaries — the most secure but most expensive.
Bridges have been crypto's worst-hit infrastructure category. The 2022 Ronin bridge hack drained $625 million through compromised validator keys — only 5 of 9 validators were needed for approval, and 5 keys were compromised. Wormhole lost $325 million to a signature verification flaw (later refunded by Jump Trading). Nomad lost $190 million in a chaotic exploit where users rushed to copy the original attacker's transaction format. Poly Network lost $611 million (mostly returned). Multichain collapsed in 2023 amid CEO disappearance and stranded user funds. The pattern: bridges hold massive value in high-attack-surface contracts. Best practices that emerged: minimize bridge exposure, prefer canonical L1↔L2 bridges, watch for warning signs.
Practical bridge use rules can substantially reduce risk. For ETH between Ethereum mainnet and major L2s (Arbitrum, Optimism, Base), use the official native bridges — they offer the highest security guarantees. For speed, third-party fast bridges (Across, Hop) are generally well-audited and used by hundreds of thousands of users, though slower native exits to mainnet take 7 days. Minimize amounts in transit — bridge what you need now, not everything. Prefer bridges where you can verify the path over those using opaque off-chain validators. Diversify across bridges for very large transfers. Always check transaction details carefully — bridge UIs sometimes display misleading information.
For Ethereum L2s, use native bridges (the official Arbitrum, Optimism, or Base bridges) for maximum security. For speed and convenience with reasonable security, established third-party bridges (Across, Stargate, Hop) work well. Avoid newer bridges with unaudited code or limited usage history. For very large amounts ($100k+), split across multiple bridge transactions or use OTC routing instead.
In theory yes, in practice usually yes. The risk is bridge solvency — if a bridge gets exploited, wrapped tokens may trade at significant discounts to underlying. WBTC has historically traded near parity with BTC, but during stress events it briefly traded at meaningful discounts. The wrapped version is only as good as the bridge backing it.
Bridges hold large pools of value (high incentive for attackers), require complex code spanning multiple chains, often rely on multisig or off-chain validators (creating attack surfaces), and are difficult to thoroughly audit. The combination makes bridges among the most attacked infrastructure in crypto. The industry is moving toward more secure designs (light clients, ZK bridges) but legacy bridges remain risky.