Skip to main content

L2 Bridging Cost Comparison (Native vs Third-Party)

Third-party bridges (Across, Hop, Hyperlane, LayerZero) handle 78% of cross-rollup volume at 0.05 to 0.20% fees. Native bridges are cheaper for L1 to L2 deposits but slow on withdrawals.

Written by Eco


L2 bridging cost is the friction users feel most directly when moving assets between Ethereum L1 and rollups (covered in the Ethereum L2 comparison),, or between two L2s. The choice between native bridges (operated by each rollup) and third-party bridges (Across, Hop, Hyperlane, LayerZero) shapes both cost and confirmation time. Third-party bridges carry a large share of cross-rollup volume, as tracked in DefiLlama bridge data, despite native bridges existing for every major L2.
​

This guide compares the two paths across cost, latency, security model, and asset support. The headline: native bridges from L1 to L2 are cheaper for one-way deposits but slow for L2-to-L1 withdrawals (7 days for optimistic rollups). Third-party bridges complete in seconds for a percentage fee. CCTP, Circle's stablecoin-native rail, sits in a separate category, cheaper than third-party for native USDC, slower than third-party but faster than canonical.
​

What Is a Bridge?

A bridge is a protocol that moves assets between two blockchains. The underlying mechanism varies. Lock-and-mint bridges hold assets in a contract on the source chain and mint a wrapped representation on the destination. Burn-and-mint bridges (CCTP, native stablecoin rails) destroy the asset on the source and issue native tokens on the destination. Liquidity-pool bridges (Across, Hop, Stargate) maintain pools on each chain and pay relayers from those pools.
​

Each model has trade-offs. Lock-and-mint creates wrapped tokens that are not fungible with native versions on the destination. Burn-and-mint preserves fungibility but requires issuer support, only a few stablecoins (USDC via CCTP, USDT via LayerZero's OFT, PYUSD) operate this way today. Liquidity-pool bridges trade speed and fungibility for paying liquidity providers a fee.
​

Native L2 Bridges

Every L2 ships with a canonical bridge that moves assets between Ethereum L1 and the L2. Examples: Arbitrum's Arbitrum Bridge, Optimism's Standard Bridge, Base's Base Bridge, zkSync's Portal, Linea's bridge, Scroll's bridge. These are operated by the rollup teams (or governance) and are part of the chain's security model.
​

How they work. Depositing from L1 to L2: the user sends ETH or an ERC-20 to the bridge contract on L1; the rollup's sequencer credits an equivalent amount to the user's address on L2 within 1-15 minutes. Withdrawing from L2 to L1: the user submits a withdrawal transaction on L2; the rollup posts the state root including this withdrawal to L1; for optimistic rollups, the user must wait the 7-day fraud-proof challenge window before claiming on L1; for ZK rollups, the user waits 30-90 minutes for the validity proof to verify, then claims.
​

Cost. The L1 deposit transaction pays mainnet gas, which varies with L1 conditions. The L2 deposit credit costs little. The L2-to-L1 withdrawal pays L2 gas, and the L1 claim transaction (after the wait period) pays mainnet gas again, so a deposit-and-withdraw round trip pays L1 gas twice before any fees.
​

Trust model. Native bridges inherit the rollup's security. For Stage 0 chains (most rollups today), the rollup's security council can pause the bridge or override withdrawals via emergency upgrade. For Arbitrum One (Stage 1), withdrawals are permissionless once finalized.
​

Third-Party Bridges

Third-party bridges connect any-to-any chains via liquidity pools or messaging-layer protocols. The dominant systems by 2026 volume:

  • Across Protocol, relayer-fronted liquidity with optimistic verification via UMA. Fast completion, with a percentage fee quoted per transfer.

  • Hop Protocol, AMM-based liquidity pools, strong on Ethereum-to-L2 stablecoin transfers. Completion in minutes, with a percentage fee.

  • Stargate, built on LayerZero's messaging layer, supports unified liquidity across many chains, with a base fee plus a percentage fee. Dominant on cross-VM routes (Ethereum ↔ Solana, EVM ↔ Aptos).

  • Hyperlane, permissionless interoperability with custom security per route. Used heavily for warp routes (cross-chain ERC-20 deployments) by app teams.

  • LayerZero, messaging-layer protocol that other apps build bridges on top of. Notable for OFT (Omnichain Fungible Token) standard used by USDT, ENA, and many newer assets.

  • Synapse, multi-chain AMM. Slightly higher fees but supports a long tail of less-trafficked tokens.

Cost Comparison: Native vs Third-Party

The comparison below shows what each path pays for a USDC bridge between Ethereum L1 and Arbitrum.

Path
​

L1 → L2 (deposit)
​

L2 → L1 (withdraw)
​

Total time
​

Arbitrum native bridge
​

L1 gas
​

L2 gas + L1 claim gas (after 7d)
​

7+ days
​

Across Protocol
​

L1 gas + bridge charge
​

L2 gas + bridge charge
​

~30 sec each way
​

CCTP (native USDC)
​

L1 gas, plus a Fast Transfer fee if used (Circle)
​

L2 gas, plus a Fast Transfer fee if used (Circle)
​

15-25 min each way
​

Hop Protocol
​

L1 gas + bridge charge
​

L2 gas + bridge charge
​

~5 min each way
​

Stargate
​

L1 gas + bridge charge
​

L2 gas + bridge charge
​

~3 min each way
​

For one-way L1-to-L2 deposits, the native bridge is competitive, since third-party bridges add their own charge on top of the same L1 gas cost. For L2-to-L1 withdrawals, third-party bridges win on time (seconds to minutes versus 7 days for optimistic rollups). The 7-day delay is the single largest reason third-party bridges dominate withdrawal volume.
​

L2-to-L2 Bridging

For moving between two L2s (Arbitrum to Base, Optimism to Linea, etc.), native bridges are not a direct option. The canonical path is L2 → L1 → L2, which pays L1 gas twice and waits out the 7-day delay for optimistic rollups. Third-party bridges or stablecoin-native rails are essentially mandatory.
​

For a USDC transfer from Arbitrum to Base:

  • Across Protocol: a quoted relayer fee, completion in seconds

  • CCTP (Circle's native rail): no protocol fee on Standard Transfers and 0 to 13 basis points on Fast Transfers, per Circle

  • Stargate: a base fee plus a percentage fee, completion in minutes

  • Canonical L2 → L1 → L2: L1 gas twice plus 7 days

The economics make canonical L2-to-L2 bridging impractical for any user-facing flow. For protocols moving stablecoins as part of treasury operations or trading, the choice is between speed (Across, Stargate) and cost (CCTP for USDC).
​

Stablecoin-Native Rails

Burn-and-mint stablecoin protocols are a separate category. They preserve native stablecoin issuance, no wrapped tokens, full fungibility on the destination chain.
​

Circle's CCTP burns USDC on the source chain and mints fresh USDC on the destination. Circle lists supported chains in its CCTP documentation. Per Circle, Standard Transfers carry no protocol fee and Fast Transfers carry a fee of 0 to 13 basis points, plus origin and destination gas.
​

Tether's USDT0 uses LayerZero's OFT standard for omnichain USDT issuance. Transfers pay LayerZero's messaging fee.
​

PYUSD via LayerZero covers PayPal's USD stablecoin across multiple chains using the same OFT mechanism.
​

For applications transferring native stablecoins specifically (the stablecoin liquidity guide ranks chains by depth),, these rails are usually cheapest and preserve issuer-issued tokens on every chain. The trade-off is they only work for the specific stablecoins integrated.
​

Bridge Aggregators

Bridge aggregators sit on top of multiple bridges and route to the cheapest or fastest option per transaction. The major ones in 2026 are LI.FI aggregator, Socket, Bungee, and Rango. Aggregators query bridge APIs in real time and quote the best price for a given source-destination-amount combination.
​

Most aggregators charge no protocol fee, they earn through bridge integration kickbacks. The user sees the underlying bridge fee plus any platform margin. For applications that need to support many bridge paths without integrating each separately, aggregator SDKs are the common solution.
​

The trade-off with aggregators: they add an extra latency hop for routing decisions and the bridge selection logic is opaque. Some aggregators have been criticized for routing to bridges that pay higher kickbacks rather than the best user-side price.
​

Security Models Compared

Bridge security is where the comparison gets technical. The three primary models:
​

Lock-and-mint with rollup security (native bridges): Inherits the rollup's security model. Stage 1 chains like Arbitrum One have permissionless withdrawals; Stage 0 chains have multisig override. The trust assumption is the rollup's proof system plus its operator multisig.
​

Optimistic verification with bonded relayers (Across, UMA-secured bridges): Relayers post bonds to front liquidity. If a relayer is fraudulent, the bond is slashed via UMA's optimistic oracle. Trust assumption is at least one honest watcher during the dispute window.
​

Multi-validator messaging (LayerZero, Wormhole, Hyperlane): A set of validators or oracles attest to message validity. Trust assumption is the validator set's honesty threshold (typically 2/3 or majority).
​

Bridge hacks have hit all three models historically. Ronin ($625M, 2022), Wormhole ($325M, 2022), Nomad ($190M, 2022), Multichain ($230M, 2023). The total bridge-hack loss exceeds $2.8B per Leaderboard (rekt.news)'s leaderboard. Most losses came from configuration errors or compromised validator keys, not the underlying cryptographic protocols.
​

Eco's Role in L2 Bridging

Eco Routes is a stablecoin transfer API that spares an integrator from picking a bridge. Eco Routes (CLI and API) returns a quote for a stablecoin transfer; a solver supplies the destination funds from its inventory, Hyperlane proves the fill, and large USDC transfers can use CCTP as the transport leg. Supported chains, including Solana, are listed live through the Routes API. Teams running stablecoin payments or treasury operations across multiple L2s can use Routes instead of maintaining separate bridge integrations.
​

FAQ

Are third-party bridges safer than native bridges?

Neither is categorically safer. Native bridges inherit rollup security, which depends on the rollup's stage and operator multisig. Third-party bridges have specific security models (optimistic, multi-validator, liquidity-bonded) and have suffered larger historical hacks but more often via operational errors than protocol breaks. Use native for L1↔L2 deposits where speed isn't critical; use third-party for fast L2↔L2 or fast withdrawals.
​

Why is canonical L2-to-L1 withdrawal so slow?

Optimistic rollups require a 7-day fraud-proof challenge window before withdrawals finalize on L1. ZK rollups don't have this delay but still need 30-90 minutes for the validity proof to verify on L1. Third-party bridges sidestep both by fronting liquidity on L1 and waiting for the canonical settlement themselves.
​

What is the cheapest way to bridge USDC between L2s?

CCTP if both chains are CCTP-supported. Circle lists the supported chains in its CCTP documentation. Per Circle, Standard Transfers carry no protocol fee and Fast Transfers carry 0 to 13 basis points, plus gas. Across Protocol is the next-cheapest option for any USDC route, including pairs CCTP doesn't yet cover.
​

How long do third-party bridges actually take?

Across completes in 15-30 seconds. Stargate completes in 2-4 minutes. Hop completes in 3-6 minutes. CCTP takes 15-25 minutes due to Circle's attestation step. Hyperlane and LayerZero vary by route configuration. Cross-VM routes (e.g., Ethereum to Solana) typically take longer than EVM-to-EVM.
​

Should I use a bridge or a CEX to move assets between L2s?

For everyday amounts, a third-party bridge is usually faster and cheaper. CEX deposit-and-withdraw routes work but require trust in the exchange and incur withdrawal fees that can exceed bridge fees. For very large amounts, OTC desks and stablecoin routing services can compete with both bridges and CEXs.
​

What happens if a bridge gets hacked?

Recovery depends on the bridge. Native bridge hacks usually result in protocol governance action (in some cases full reimbursement from the rollup treasury). Third-party bridge hacks have varied, Wormhole was reimbursed by Jump Crypto, Nomad recovered some funds via whitehat appeals, others have not been made whole. For large flows, treat bridge risk like counterparty risk: limit exposure per bridge.
​

Do bridge fees scale with transfer size?

Most third-party bridges charge a percentage of notional plus a flat gas component. CCTP Standard Transfers carry no protocol fee, while Fast Transfers carry 0 to 13 basis points, per Circle. Native bridges charge only gas. For very small transfers, the flat gas component dominates; for large transfers, percentage fees become material.
​

Which L2s have the cheapest deposits from L1?

Every L2 native bridge deposit pays mainnet gas, which depends on L1 conditions. The marginal differences come from each rollup's deposit gas overhead. Base, Optimism, and Arbitrum tend to have the lowest L1 deposit costs in practice; ZK rollups like zkSync sometimes cost slightly more due to additional state-init overhead.
​

Related Reading

Did this answer your question?