Moving crypto between blockchains sounds straightforward but involves some of the highest-risk operations in DeFi. Bridges have been responsible for some of the largest hacks in crypto history, and yet bridging is increasingly necessary as the multi-chain ecosystem grows. Understanding the tradeoffs helps you bridge smarter and safer.
The fundamental challenge is that blockchains cannot natively communicate with each other. Bitcoin does not know what is happening on Ethereum, and Ethereum does not know what is happening on Solana. Bridges create synthetic connections between these isolated systems, and the security model of that connection varies enormously.
Lock-and-mint bridges work by locking your asset on the source chain and minting a wrapped version on the destination chain. When you bridge ETH to Arbitrum using the native bridge, your ETH is locked in a contract on mainnet and you receive ETH on Arbitrum. The security depends entirely on the integrity of the locking contract and the bridge operators.
The Ronin bridge hack ($600M), Wormhole hack ($320M), and Nomad hack ($190M) all exploited different vulnerabilities in bridge infrastructure. Ronin's validators were compromised. Wormhole had a smart contract bug. Nomad had a verification flaw that anyone could exploit. The variety of attack vectors shows that bridge security is a hard, unsolved problem.
Native rollup bridges (for L2s like Arbitrum and Optimism) are generally the safest option because they inherit Ethereum's security model. The tradeoff is speed. Withdrawing from Optimistic Rollups to Ethereum L1 requires a 7-day challenge period. This delay is a feature, not a bug, as it allows time to detect fraud. But it makes native bridges impractical for traders who need fast execution.
Third-party bridges like Across, Stargate, and others offer faster bridging by using liquidity pools or relay networks. These are faster because they settle against their own liquidity rather than waiting for L1 finality. The risk shifts from L1 security to the bridge protocol's own security model and liquidity.
Bridge aggregators like LI.FI and Socket route across multiple bridges to find the best rate, similar to how DEX aggregators route across liquidity pools. Using an aggregator can save on fees and find optimal routes, but it adds another layer of smart contract risk since the aggregator contract itself becomes a potential attack surface.
The cost of bridging goes beyond transaction fees. Slippage on bridge liquidity pools, potential for wrapped token depegging, and the opportunity cost of locked capital during bridge delays all contribute to the real cost. For small amounts, bridge fees can be a significant percentage of the transfer.
Wrapped token risk deserves specific attention. When you hold WETH on a chain other than Ethereum, you hold a claim on ETH locked in a bridge contract. If that contract is compromised, your WETH could become worthless even though "real" ETH still exists. This is why native assets are always safer than wrapped versions, and why checking the backing of wrapped assets on new or smaller chains is important.
The opportunity side of bridging comes from capital efficiency across chains. Yield opportunities, token launches, and airdrops often appear on specific chains. Being able to move capital to where the opportunity is creates an advantage. Some of the best DeFi yields historically appeared on newer chains with bridge incentives, rewarding early movers who were willing to accept bridge risk.
Best practices for bridging include using native bridges for large amounts when speed is not critical, using established third-party bridges for smaller amounts that need speed, avoiding new or unaudited bridges, keeping only working capital on non-native chains, and checking bridge TVL and audit status before using a new service.