How to Bridge Tokens Across Chains: A Complete Guide

If you've ever tried to move tokens from Ethereum to Arbitrum, or from Polygon to Optimism, you've encountered one of crypto's fundamental infrastructure challenges: blockchains don't natively talk to each other. Your ETH on Ethereum and your ETH on Arbitrum exist on entirely separate networks, and moving value between them requires a piece of infrastructure called a bridge.

Bridging is one of the most practically important and most misunderstood operations in DeFi. This guide explains what bridging actually does under the hood, the different types of bridges and how they work, major bridge protocols in the ecosystem, and the risks that have made bridges one of the most exploited categories of smart contracts in crypto history.

What Does "Bridging" Actually Mean?

At its core, bridging is the process of transferring value from one blockchain to another. But that description hides significant complexity, because blockchains are independent state machines, Ethereum doesn't know what's happening on Arbitrum, and Polygon doesn't know what's happening on Solana.

You can't literally move a token from one chain to another. What bridges actually do is one of the following:

Lock and Mint

The most common bridge design. You deposit (lock) your tokens in a smart contract on the source chain. The bridge then mints equivalent "wrapped" tokens on the destination chain. When you want to go back, you burn the wrapped tokens, and the bridge releases the original locked tokens.

Example: You lock 1 ETH on Ethereum → the bridge mints 1 WETH on Arbitrum. Your Ethereum ETH sits in the bridge contract, and you use the wrapped version on Arbitrum.

Burn and Mint

Some tokens are designed to exist natively on multiple chains. The bridge burns tokens on the source chain and mints new tokens on the destination chain, with the total supply across all chains staying constant. Circle's Cross-Chain Transfer Protocol (CCTP) for USDC works this way, it burns USDC on one chain and mints native USDC on another.

Liquidity Network (Pool-Based)

Instead of locking and minting, some bridges maintain liquidity pools on multiple chains. When you bridge, you deposit tokens into a pool on the source chain, and tokens are released from a pool on the destination chain. No wrapping or minting involved; you receive native assets on the other side. This is faster and simpler but requires the bridge to maintain sufficient liquidity on every chain.

Major Bridge Protocols and How They Differ

Canonical / Rollup Bridges

Every major rollup (Arbitrum, Optimism, Base, zkSync, etc.) has its own "official" bridge. These canonical bridges are the most trust-minimized option because they rely on the rollup's own security model. The tradeoff is speed: withdrawals from optimistic rollups (Arbitrum, Optimism) typically require a 7-day challenge period before funds are released on Ethereum.

Across Protocol

Across uses an optimistic verification model with an intent-based system. Relayers fill bridge requests on the destination chain using their own capital, and are reimbursed from the source chain after verification. This is fast (typically minutes) and capital-efficient, with UMA's optimistic oracle providing the verification layer.

Stargate (LayerZero)

Stargate is a liquidity-network bridge built on LayerZero's messaging protocol. It maintains unified liquidity pools across chains and guarantees instant finality on the destination chain. No wrapped tokens, you receive native assets. The tradeoff is that it depends on LayerZero's cross-chain messaging security.

Wormhole

Wormhole uses a guardian network, a set of 19 validators that observe transactions on the source chain and produce signed attestations that can be verified on the destination chain. It supports a wide range of chains, including Solana, Sui, and Aptos (not just EVM). However, Wormhole suffered a major exploit in 2022 ($320 million) due to a smart contract vulnerability.

Synapse, Hop, Celer, and Others

The bridge landscape includes many other protocols, each with different architectures: Synapse (AMM-based with cross-chain messaging), Hop Protocol (designed for rollup-to-rollup transfers using "bonders"), and Celer (message-based with an SGN validator network). Each makes different tradeoffs between speed, cost, trust assumptions, and chain coverage.

Bridge Aggregators

Because there are so many bridges with different strengths, bridge aggregators have emerged to compare routes and find the best option for a given transfer. Tools like LI.FI, Socket, and Bungee query multiple bridges simultaneously and present users with options sorted by speed, cost, and security model. These aggregators are often integrated into wallets and DeFi frontends, meaning users may be using a bridge without even knowing which specific protocol is handling their transfer.

What Affects Bridging Cost and Speed

Several factors determine the cost and time of a bridge transaction:

• Gas fees on both chains: You typically pay gas on the source chain to initiate the bridge, and the bridge may pass along destination chain gas costs as part of the fee.
• Bridge protocol fees: Most bridges charge a small fee (often 0.04% to 0.3% of the transfer amount).
• Slippage (for AMM-based bridges): Pool-based bridges that use AMMs may have price impact on larger transfers, similar to trading on a DEX.
• Speed vs. security tradeoff: Canonical rollup bridges are cheap and trust-minimized but slow (7 days for optimistic rollups). Third-party bridges are fast (minutes) but introduce additional trust assumptions.
• Transfer size: Large transfers may face higher slippage on pool-based bridges or may need to be split across multiple bridges for best execution.

Why Bridge Security Matters: A History of Exploits

Bridges have been the single most exploited category of smart contracts in DeFi history. The numbers are staggering: Ronin Bridge ($625M), Wormhole ($320M), Nomad ($190M), Harmony Horizon ($100M), and many others. Combined, bridge exploits account for billions of dollars in losses.

Why are bridges such attractive targets? Several reasons:

• They hold enormous amounts of locked funds: Lock-and-mint bridges have smart contracts sitting on one chain holding all the collateral backing wrapped tokens on other chains. Compromise that contract, and you drain the entire bridge.
• Cross-chain verification is hard: Verifying that something happened on one chain from another chain is a fundamental computer science problem. Bridges use various approximations (validator sets, optimistic assumptions, light clients) that each introduce potential failure modes.
• Complex attack surface: Bridges involve smart contracts on multiple chains, off-chain relayers or validators, and cross-chain messaging protocols. Each component is a potential entry point.

Key Risks to Understand

• Smart contract risk: Bridge contracts are complex multi-chain systems. Bugs in any component (source chain, destination chain, relayer, verifier) can result in loss of funds.
• Validator/guardian risk: Many bridges rely on a trusted set of validators. If enough validators are compromised, the bridge can be drained.
• Wrapped asset risk: If a lock-and-mint bridge is exploited, the wrapped tokens on the destination chain lose their backing, effectively going to zero. This affects everyone holding those wrapped tokens, not just the attacker's victims.
• Liquidity risk: Pool-based bridges can run out of liquidity on the destination chain, causing delays or preventing transfers.
• Finality risk: Some bridges release funds before the source chain transaction is truly final. Chain reorganizations could potentially create double-spend situations.

Best Practices When Bridging

When bridging tokens between chains, there are some general principles worth considering:

• Prefer canonical/official rollup bridges for large amounts where the time delay is acceptable; they have the fewest trust assumptions.
• Use bridge aggregators to compare options across multiple protocols for the best combination of speed, cost, and security.
• Be cautious with very large transfers through any single bridge. Splitting across multiple bridges or multiple transactions can reduce exposure to any single bridge failure.
• Check that the bridge has been audited and has a track record. Newer bridges with less TVL history carry more uncertainty.
• Verify the destination token is the version you expect, some bridges deliver wrapped tokens, while others deliver native assets. Using the wrong version can cause issues in downstream DeFi protocols.

The Bottom Line

Bridging is essential infrastructure for a multi-chain crypto ecosystem. Without bridges, each blockchain would be an island, and the composability that makes DeFi powerful would stop at chain boundaries. But bridges also represent one of the most significant risk categories in the space, the combination of large locked-value targets and complex cross-chain verification creates a persistent security challenge.

Understanding how different bridges work, what trust assumptions they make, and what their track records look like is practical knowledge for anyone operating across multiple chains. The bridge landscape continues to evolve, with newer approaches (like intent-based bridging and native issuance protocols like CCTP) gradually improving the speed, cost, and security of cross-chain transfers.

About Portals.fi: Portals.fi is the DeFi Super App. A one-click gateway to the entire on-chain economy. Powered by real-time data and seamless execution, Portals.fi connects traders to over 20 million assets, thousands of protocols, and every major blockchain.

This article is for informational purposes only and does not constitute financial advice. DeFi protocols carry inherent risks including smart contract vulnerabilities, liquidation risk, and market volatility. Always conduct your own research before interacting with any protocol. For our full disclaimer, please visit here.