Published on Sat Aug 22 2026 00:00:00 GMT+0000 (Coordinated Universal Time) by Jacob Cavazos

Base is an Ethereum L2 built by Coinbase. It uses the OP Stack and settles on Ethereum mainnet. To use Base you first have to get assets onto it. That means bridging.

This article covers every major route to bridge assets to Base. It compares them by cost, speed, safety, and asset quality. No single bridge is best for every situation. The right choice depends on what you are bridging, how fast you need it, and how much trust you are willing to place in third-party code.

What Bridging Actually Means

Bridging is the process of moving an asset from one chain to another. Because chains do not share state, a bridge has to create a representation of the asset on the destination chain. There are two broad ways this happens.

The first is lock-and-mint. The bridge locks the original asset in a contract on the source chain and mints a wrapped or synthetic version on the destination — for a deeper comparison of bridge architectures, see Bridge Architecture: Lock-Mint vs Burn-Mint vs Liquidity Pool. When you bridge back, the wrapped version is burned and the original is unlocked. Most older bridges work this way.

The second is burn-and-mint, used by assets that are natively issued on multiple chains. Circle’s USDC is the best example. When you bridge USDC through CCTP, the bridge burns USDC on the source chain and Circle mints an equivalent amount of native USDC on the destination. No wrapped token is involved.

The difference matters. Wrapped assets carry bridge risk. If the bridge is exploited, the wrapped token can become worthless. Native assets do not carry that risk because the issuer, not the bridge, controls minting.

The 7-Day Withdrawal Problem

Base is an optimistic rollup. Withdrawals from Base back to Ethereum mainnet take approximately seven days. This is not a bug. It is a property of the optimistic rollup security model. The sequencer posts state roots, and there is a challenge window during which anyone can submit a fraud proof. Only after that window closes does the withdrawal finalize on L1.

This seven-day delay applies to the official Base bridge and to any bridge that routes through the native rollup withdrawal path. Third-party bridges can shortcut this by fronting you liquidity on the destination chain. They take on the seven-day wait themselves and charge you a fee for the convenience.

If you need to move fast, use a third-party liquidity bridge. If you want maximum safety and lowest cost and can wait seven days, use the official bridge.

Method 1: The Official Base Bridge

The official bridge is hosted at bridge.base.org. It is the canonical way to move ETH and ERC-20 tokens between Ethereum and Base.

It works by locking assets on L1 and minting a corresponding amount on L2, or by initiating the standard rollup withdrawal flow for the reverse direction. Deposits from L1 to L2 typically finalize within a few minutes. Withdrawals from L2 to L1 take about seven days.

Cost is relatively low on the deposit side because you only pay L1 gas. The bridge itself does not charge a fee. You pay Ethereum mainnet gas to submit the deposit transaction, and Base gas to claim on L2. Withdrawals require several transactions across the seven-day window, each costing L1 gas.

Safety is the highest of any method. The official bridge is operated by Base and audited as part of the OP Stack. It does not rely on third-party validator sets or multi-sig committees. If you are moving large amounts and are not in a hurry, this is the default choice.

The downside is the seven-day withdrawal. There is no fast exit. If you need assets on L1 quickly, you need a different route.

Method 2: Across Protocol

Across is a cross-chain bridge that uses an optimistic relayer model. When you bridge from Ethereum to Base, a relayer fronts you the liquidity on Base immediately. The relayer then submits the proof to the Across protocol and gets reimbursed after the optimistic challenge window.

Deposits to Base through Across are fast, usually under a minute. Withdrawals from Base to Ethereum are also fast from the user’s perspective because the relayer fronts the liquidity. The relayer absorbs the seven-day wait.

Cost is competitive. Across charges a relayer fee that is typically a small percentage of the bridged amount plus gas. The fee varies with liquidity and demand. For small amounts the fee can be a meaningful percentage. For large amounts it is negligible.

Safety is good. Across uses UMA’s optimistic oracle for dispute resolution. The bridge contracts are audited. The main risk is a bug in the relayer contracts or the oracle. Across has been operating since 2022 without a major exploit.

Across is a strong choice when you want speed and reasonable safety. It is particularly good for ETH and stablecoin transfers between Ethereum and Base.

Method 3: Stargate

Stargate is a bridge built on LayerZero. It uses a shared liquidity pool model where each chain has access to a unified pool of assets. When you bridge USDC from Ethereum to Base, Stargate transfers from the Ethereum pool and credits you from the Base pool.

Stargate supports native asset transfers for USDC and several other tokens. This means you get native USDC on Base, not a wrapped version. That is a meaningful safety improvement over lock-and-mint bridges.

Speed is fast for deposits, typically under a minute. Withdrawals from Base to Ethereum depend on the LayerZero message delivery time, which is usually fast but can vary.

Cost includes gas on both chains plus a protocol fee. Stargate’s fees are generally competitive. The protocol fee goes to liquidity providers.

Safety depends on LayerZero’s oracle and DVN (decentralized verifier network) configuration. LayerZero has faced scrutiny over its security model, particularly around the default oracle configuration. Users can customize their DVN setup, but most use defaults. The contracts are audited and the protocol has not been exploited, but the trust model is more complex than the official bridge.

Stargate is a good choice for stablecoin transfers where you want native assets on the destination. It is less ideal for long-tail tokens that are not in the shared liquidity pool.

Method 4: Wormhole

Wormhole is a generalized message-passing bridge originally built for Solana and Ethereum. It now supports many chains including Base. Wormhole uses a guardian set of validators who sign messages attesting to events on the source chain.

For token transfers, Wormhole typically uses lock-and-mint. You lock the original asset and receive a Wormhole-wrapped version on Base. This means you carry bridge risk for the duration you hold the wrapped token.

Speed is fast. Wormhole messages are typically delivered within seconds. The guardian set signs and relays quickly.

Cost is low. You pay gas on both chains plus a small relayer fee. Wormhole does not charge a large protocol fee for standard transfers.

Safety is the main concern. Wormhole was exploited for over $300 million in 2022 in one of the largest bridge hacks in crypto history. The protocol was rebuilt and has operated since without another major exploit, but the history matters. The guardian set is a permissioned multi-sig of 19 validators. If a sufficient number of guardians are compromised, a false message could be attested.

Wormhole is best for fast transfers of assets where you plan to swap out of the wrapped version immediately on the destination chain. Do not hold Wormhole-wrapped tokens long-term if you can avoid it.

Method 5: deBridge

deBridge is a cross-chain messaging and bridging protocol that uses an off-chain oracle network. Validators sign events on the source chain and the signatures are verified on the destination.

deBridge supports native USDC transfers through its integration with CCTP. For other assets it uses a lock-and-mint model with deBridge-wrapped tokens.

Speed is fast, typically under a minute. deBridge uses a network of validators who sign quickly and a relayer who delivers the message.

Cost is competitive. deBridge charges a protocol fee plus gas. Fees are generally in line with Across and Stargate.

Safety is reasonable. deBridge uses a permissioned validator set. The protocol has not been exploited. The main risk is the validator set and the bridge contracts. deBridge has been audited and has been operating since 2022.

deBridge is a solid choice for fast transfers, particularly for USDC where it can route through CCTP for native delivery.

Method 6: LI.FI

LI.FI is not a single bridge. It is a bridge aggregator. When you use LI.FI, it queries multiple bridges and routes your transfer through the one that offers the best combination of cost, speed, and liquidity at that moment.

This means LI.FI might route your transfer through Across, Stargate, deBridge, or another bridge depending on conditions. You get the benefit of comparison shopping without doing it manually.

Speed depends on the underlying bridge LI.FI selects. Cost is generally as good or better than going direct because LI.FI can find the cheapest route. LI.FI charges a small fee on top of the underlying bridge fee.

Safety is a mixed question. LI.FI itself is an aggregator and does not custody funds for long. But the safety of your transfer depends on whichever bridge LI.FI selects. If it routes through a less secure bridge, you inherit that risk. LI.FI does filter for reputable bridges, but you are trusting LI.FI’s judgment.

LI.FI is a good choice when you want convenience and do not want to manually compare bridges. It is less ideal if you have a strong preference for a specific bridge’s security model.

Method 7: Socket

Socket is another bridge aggregator, similar to LI.FI. It queries multiple bridges and routing options and presents the best path. Socket also supports intent-based routing where solvers compete to fill your bridge request.

The intent-based model is worth understanding. Instead of specifying a bridge, you specify what you want: a certain amount of a certain token on a certain chain. Solvers then figure out how to deliver it. This can result in routes that combine multiple bridges, DEX swaps, and other operations.

Speed depends on the route selected. Cost is competitive because solvers compete. Safety depends on the underlying bridges and protocols in the route.

Socket is a good choice for complex transfers where you want the system to figure out the optimal path. Like LI.FI, it introduces a layer of abstraction that means you are trusting Socket’s routing logic.

Method 8: Coinbase Exchange Withdrawal

If you have an account on Coinbase’s centralized exchange, you can withdraw directly to Base. Coinbase supports Base as a withdrawal network for several assets including ETH and USDC.

This is not a bridge in the technical sense. You are withdrawing from a custodial exchange to a self-custody wallet on Base. But functionally it accomplishes the same thing: getting assets onto Base.

Speed is fast. Withdrawals from Coinbase to Base typically arrive within minutes. Cost is low. Coinbase does not charge a withdrawal fee for Base network withdrawals, and Base gas is negligible.

Safety is different from bridge safety. You are trusting Coinbase as a custodian while your assets are on the exchange. Once withdrawn to self-custody, the assets are on Base and carry no bridge risk. This is actually one of the safest ways to get assets onto Base because there is no bridge contract to exploit.

The limitation is that you need a Coinbase account and you need to have your assets on Coinbase. If your assets are in self-custody on Ethereum, you would first need to send them to Coinbase, which costs L1 gas and takes time.

For users who already use Coinbase, direct withdrawal to Base is the simplest and cheapest method. For users in self-custody, it is less practical.

Method 9: Circle CCTP

Circle’s Cross-Chain Transfer Protocol is the best way to bridge USDC specifically. CCTP is not a general-purpose bridge. It only works for USDC, and it works by burning USDC on the source chain and minting native USDC on the destination.

This is the burn-and-mint model. No wrapped token is involved. The USDC you receive on Base is the same native USDC issued by Circle. It carries no bridge risk.

Speed is fast. CCTP transfers typically complete in under five minutes. The process involves burning on the source chain, attesting the burn through Circle’s attestation service, and minting on the destination.

Cost is low. You pay gas on both chains. There is no protocol fee from Circle. The main cost is gas.

Safety is excellent. There is no bridge contract holding USDC. Circle controls minting. The only risk is a bug in the CCTP contracts or Circle’s attestation service. Circle is a regulated entity and the contracts are audited.

CCTP is the clear best choice for bridging USDC to Base. If you are moving stablecoins, use CCTP. Many of the bridges above (Stargate, deBridge, LI.FI) can route through CCTP under the hood. You can also use CCTP directly through Circle’s interface.

Native vs Wrapped USDC on Base

This deserves emphasis because it is a common source of confusion. Base has both native USDC and bridged USDC.

Native USDC is issued by Circle directly on Base. It is the same USDC that exists on Ethereum, Solana, and other chains. It is fully backed by Circle’s reserves. It carries no bridge risk.

Bridged USDC, sometimes called USDbC or Base-bridged USDC, is the version that came through the official Base bridge using lock-and-mint. It is backed by USDC locked in the bridge contract on Ethereum. It carries bridge risk. If the bridge contract is exploited, bridged USDC could become unredeemable.

Most Base applications accept both, but native USDC is preferred. Circle’s CCTP exists specifically to let users get native USDC on Base without going through the lock-and-mint bridge.

If you are bridging USDC to Base, use CCTP. Once your assets are on Base, see our beginner’s guide to swapping tokens on Base. If you already have bridged USDC on Base, you can swap it for native USDC through several DEXs on Base.

How to Choose

For ETH and ERC-20 tokens where you can wait seven days, use the official Base bridge. It is the safest and cheapest option.

For fast transfers of ETH and stablecoins, use Across. It has a strong safety record and competitive fees.

For native USDC specifically, use CCTP directly or through a bridge that routes through CCTP. Never use lock-and-mint for USDC if you can avoid it.

For convenience and automatic route selection, use LI.FI or Socket. Accept that you are trusting their routing logic.

For assets already on Coinbase, withdraw directly to Base. It is the cheapest and simplest method.

Avoid holding wrapped tokens from any bridge longer than necessary. Bridge in, swap to native assets, and move on.

Final Notes on Safety

Bridge risk is real. Over $2 billion has been stolen from bridges since 2020 — our guide on cross-chain bridge security models breaks down how each model fails. The exploits have ranged from signature verification bugs to private key compromises of validator sets.

When you bridge, you are temporarily trusting a third-party system with your assets. Minimize the time and amount exposed. Use native asset routes where possible. Use the official bridge for large transfers when speed is not critical.

Check the bridge’s audit history. Check how long it has been operating. Check whether it has been exploited before. Check what security model it uses. A bridge that has been operating for three years without an exploit is not guaranteed to be safe, but it is a better signal than a bridge that launched last month.

No bridge is risk-free. The goal is not to eliminate risk but to choose the route with the best risk-reward tradeoff for your specific transfer — and understanding ISO 20022 and blockchain settlement matters if you are bridging for institutional use cases.

Frequently Asked Questions

How long does it take to bridge to Base?

Bridging time depends on the method used. The official Base bridge typically takes around 7 days for withdrawals from Base to Ethereum, while deposits to Base usually complete within minutes. Third-party bridges can be faster, often settling in minutes to a few hours, but vary by provider and network congestion.

What is the cheapest way to bridge to Base?

The cheapest method depends on the asset and amount. The native Coinbase-backed bridge has no additional bridging fee but requires gas on Ethereum. Third-party bridges may offer lower total costs for smaller amounts by optimizing gas, but may charge their own fees. Comparing total cost including gas and bridge fees is recommended.

Is bridging to Base safe?

Bridging carries inherent risk because you are trusting a bridge protocol with your assets during the transfer. The official Base bridge is considered the most secure since it is backed by the same security model as the OP Stack. Third-party bridges vary in security, and users should research audit history and track records before using them.

What assets can you bridge to Base?

You can bridge ETH and most popular ERC-20 tokens to Base, including USDC, USDT, DAI, WBTC, and many others. The availability of specific tokens depends on the bridge you use. The native bridge supports ETH and a growing list of approved tokens, while third-party bridges may support additional assets.

Written by Jacob Cavazos