How to Bridge to Base (Without Losing Money to Bad Bridges)
Coinbase's official Base bridge was deprecated. Here's how to safely bridge to Base in 2026 using Superbridge, CCTP, and the routes that actually still work.
Shiloh
Dispatches from the trenches — builder-first crypto coverage.

- Coinbase deprecated the official bridge.base.org, it now redirects to documentation
- Base directs users to third-party providers: Superbridge and Brid.gg for Ethereum, a dedicated bridge for Solana, and Garden for Bitcoin
- Circle CCTP moves USDC natively (burn-and-mint) with no wrapped asset, V2 Fast Transfer settles in 8-20 seconds
- Withdrawing directly from Coinbase Exchange to a Base address avoids bridge risk entirely when available
- Major bridge hacks (Wormhole, Nomad, Multichain, Ronin) all trace back to broken trust assumptions, not user error
- Phishing and fake bridge websites are the realistic personal risk, not protocol-level exploits
If you're trying to bridge to Base for the first time, the first thing you'll notice is that the official bridge doesn't actually exist anymore. That trips up a lot of people, and it's exactly the kind of confusion that scammers exploit with fake lookalike sites.
Bridging is also where crypto users lose the most money to mistakes that have nothing to do with market volatility. Wrong contract address, fake site, unlimited token approval signed without reading it, funds gone. None of that requires a hack of Base itself, just one bad click.
Here's how to actually bridge to Base in 2026, which routes are safest for which asset, and how to avoid the traps that have drained wallets on every other chain's bridging story too.
The Official Base Bridge Doesn't Exist Anymore
For a long time, bridge.base.org was the default answer to "how do I bridge to Base." That's no longer true. Coinbase deprecated the official Coinbase-operated bridge as part of Base's broader shift toward decentralization and the Superchain vision.
Visit bridge.base.org today and it redirects straight to Base's documentation instead of a bridging interface. Base now points users to a short list of independent third-party providers, and is explicit that Coinbase "assumes no responsibility for their operations."
That single fact is why this guide exists. If you learned to bridge to Base a year or two ago, the instructions you remember are already outdated, and outdated instructions are exactly what phishing sites are counting on you to follow blindly.
The Safest Way to Get Funds to Base (If You Can Use It)
Before touching any bridge at all, check whether you even need one. If your funds sit on Coinbase Exchange, you can withdraw ETH, USDC, and several other assets straight to a Base address with no bridge, no L1 settlement wait, and no withdrawal fee.
This route carries essentially none of the risk described later in this guide, since there's no third-party smart contract in the middle and no fake-website risk beyond the exchange itself. If this option is available to you, it's the one to use.
Most people reading a guide titled "how to bridge to Base" don't have that option, though, usually because their funds are already on Ethereum mainnet, Solana, or another chain. That's what the rest of this guide covers.
Bridging From Ethereum: Superbridge and Brid.gg
For moving ETH and other supported assets from Ethereum mainnet to Base, Base's own documentation currently lists two providers: Superbridge (superbridge.app) and Brid.gg (brid.gg). Both support mainnet and testnet transfers.
Functionally, the two work the same way. You connect a wallet, pick the asset and amount, and the bridge locks it on Ethereum while minting the equivalent on Base. Withdrawals back to Ethereum go through the standard optimistic rollup challenge period, which typically takes about a week, a detail that catches people off guard if they need funds back on mainnet quickly.
Whichever one you use, go directly to the URL rather than clicking a link from a search ad, a DM, or a tweet reply. Bridge phishing pages consistently rank as paid search ads and get posted as "helpful" replies under real crypto accounts' tweets.

Bridging USDC the Native Way: Circle's CCTP
If the asset you're moving is USDC, there's a route that sidesteps most bridge risk entirely: Circle's Cross-Chain Transfer Protocol, or CCTP. Base has been a supported CCTP chain since 2025, including the faster CCTP V2 route.
CCTP doesn't lock and mint a wrapped token the way most bridges do. It burns your USDC on the source chain, waits for Circle's attestation service to confirm the burn, then mints fresh native USDC directly on Base. There's no wrapped-USDC middleman asset and no bridge liquidity pool that can be drained.
CCTP V2's Fast Transfer route settles in roughly 8 to 20 seconds on supported chains, which is dramatically quicker than the minutes-to-a-week range most other routes fall into. Most major wallet interfaces, including Coinbase Wallet and several bridge aggregators, use CCTP under the hood automatically when you're moving USDC, so you may already be using it without realizing.
If you're bridging USDC specifically, this is the route to prefer over a generic Ethereum bridge whenever it's available.

Bridging From Solana or Bitcoin
Base also has direct paths from two of the largest non-Ethereum ecosystems.
A dedicated Base-Solana Bridge moves SOL and SPL tokens bidirectionally between the two chains, using cross-chain messaging rather than a simple lock-and-mint model.
For Bitcoin, Garden (app.garden.finance) offers a non-custodial route that brings BTC into Base along with support for moving assets from Ethereum and Solana as well. Non-custodial here means no single party holds your BTC in escrow during the transfer, which matters given Bitcoin's history of custodial bridge failures.
Both of these are narrower use cases than the Ethereum routes above, so double-check you're on the correct official URL before connecting a wallet, the same rule applies everywhere in this guide.
Bridge Routes at a Glance
| Route | Best for | Typical time | Trust model |
|---|---|---|---|
| Coinbase Exchange withdrawal | Funds already on Coinbase | Minutes, no bridge needed | Centralized exchange, no bridge risk |
| Superbridge / Brid.gg | ETH and general assets from Ethereum | Minutes in, ~7 days to withdraw back | Smart contract, lock-and-mint |
| Circle CCTP | USDC specifically | 8–20 seconds (V2 Fast Transfer) | Native burn-and-mint, no wrapped asset |
| Base-Solana Bridge | SOL and SPL tokens | Minutes | Cross-chain messaging |
| Garden | BTC and select assets | Varies by network | Non-custodial |
Bridge Aggregators: When You Don't Want to Pick a Route Yourself
If comparing five different bridges sounds like a chore every time you want to move funds, an aggregator does that comparison for you. LI.FI is the most commonly used one for routes into Base, it quotes across more than a dozen underlying bridges, including Across, Stargate, Wormhole, Hop, and deBridge, and routes your transfer through whichever one is cheapest and fastest for your specific asset and amount at that moment.
Stargate is worth knowing about on its own too. It routes through LayerZero's messaging layer using unified liquidity pools rather than the simple lock-and-mint model, and its v2 "Hydra" route also taps into CCTP for native USDC delivery, similar to the dedicated CCTP route described above.
Cost-wise, expect typical hop fees in the 0.05% to 0.2% range on top of gas, meaning a $1,000 transfer usually runs somewhere between $0.50 and $2.00 in total fees when using one of these aggregated routes. Settlement through these routes generally lands in one to five minutes, with Across specifically known for sub-30-second fills on ETH, WETH, and WBTC transfers.
The tradeoff with an aggregator is one more layer between you and the underlying bridge. You're trusting the aggregator's routing logic in addition to whichever bridge it selects. For most routine transfers that's a reasonable tradeoff for the convenience, just don't skip verifying the aggregator's own URL is legitimate before connecting a wallet.
What to Do After Your Funds Land on Base
Once you've bridged, confirm the transfer actually completed before assuming something's wrong. Copy your wallet address into BaseScan, Base's block explorer, and check the transaction history directly rather than relying on your wallet's balance display, which can lag by a few minutes.
If a token shows up on BaseScan but not in your wallet, it usually means the wallet hasn't auto-detected the token contract yet. Most wallets let you manually add a token by pasting its contract address, which you can also pull directly from the BaseScan transaction.
Don't panic if an Ethereum-to-Base transfer through Superbridge or Brid.gg takes a few minutes longer than you expected. Deposits into a rollup typically settle faster than withdrawals, but there's still a confirmation window on the Ethereum side before the funds are usable on Base.
Why Bridges Get Hacked
It's worth understanding why bridge security gets talked about so seriously, because the failure modes aren't hypothetical.
Wormhole lost $325 million in February 2022 after a routine contract upgrade left a verification check effectively disabled, making every message look pre-verified. Nomad lost over $190 million a few months later when a smart contract bug meant one exploit transaction became copy-pasteable, and hundreds of unrelated wallets piled in within hours once word spread.
Multichain's collapse wasn't even a hack in the traditional sense. It relied on a small custodian holding the underlying assets and issuing IOUs on other chains. When that custodian disappeared, the IOUs became worthless overnight.
Ronin and Harmony both lost funds after attackers compromised the private keys controlling their multi-signature bridge wallets, not through a code exploit at all. The common thread across nearly every major bridge hack is a trust assumption breaking, whether that's a validator set, a custodian, or a signing key, not users making individual mistakes.
That's actually good news for you as someone learning to bridge to Base: the routes covered in this guide (especially CCTP, which has no custodian or wrapped-asset step to compromise) are structurally simpler than the bridges in that hack history. Your personal risk when you bridge to Base has more to do with phishing than protocol-level exploits.
How to Spot a Fake Bridge Before You Connect Your Wallet

Phishing is the risk that actually threatens most people trying to bridge to Base, not a repeat of Wormhole or Nomad. Fake bridge sites replicate the real interface, branding, and even wallet-connect prompts closely enough that a quick glance won't catch the difference.
A few checks that catch most fakes:
- Type the URL yourself or use a bookmark, never click a bridge link from a search ad, DM, or reply
- Confirm the URL against Base's own documentation, not a link someone else sent you
- Check the wallet-connect popup shows the correct domain before approving anything
- Avoid granting unlimited token approvals when a bridge only needs a one-time amount
- Treat urgency as a red flag. Real bridges don't need you to act in the next 60 seconds
Sneak peek: if you're bridging to Base specifically to start building, the Base app building guide walks through what to do once your funds actually land.
Common Mistakes People Make When They Bridge to Base
A few mistakes show up over and over in accounts of people who lost money bridging, not just to Base, but to any chain. Worth naming them directly.
Bridging your entire balance on the first try. Test transfers exist for a reason. Send a small amount first, confirm it lands correctly, then move the rest. It costs a few extra minutes and it's the single easiest way to avoid a catastrophic mistake.
Confusing a similarly-named token for the real one. Scam tokens sometimes copy a legitimate project's name and symbol exactly, differing only in the contract address. Always verify the contract address you're bridging matches the official one, not just the ticker symbol shown in a wallet's token list.
Granting unlimited approvals out of habit. Many wallets default to an unlimited spending approval when you interact with a new contract. A one-time bridge doesn't need indefinite access to your tokens going forward. Set a custom, limited approval when the option is available.
Assuming a bridge is legitimate because it ranks first in search results. Paid search ads have been used to place phishing sites above the real one for popular bridges before. Ranking position is not verification.
Bridging during a network incident without checking status first. If Base or Ethereum is experiencing congestion or an outage, transactions can behave unpredictably. A quick check of the relevant network's status page before a large transfer costs nothing and can save a stuck transaction headache.
A Pre-Bridge Safety Checklist

Run through this before every bridge transaction, not just your first one:
- Confirm the exact URL against Base's official bridge documentation
- Double-check the token contract address you're bridging, especially for ERC-20s
- Start with a small test amount before moving your full balance
- Never sign a transaction you don't understand just because a wallet popup says "approve"
- If you're bridging USDC, check whether CCTP is available before defaulting to a generic bridge
Common Questions About Bridging to Base
Is there still an official Coinbase bridge for Base? No. The bridge at bridge.base.org has been deprecated and now redirects to documentation. Base currently directs users to third-party providers like Superbridge and Brid.gg instead.
What's the fastest way to bridge to Base? For USDC, Circle's CCTP V2 Fast Transfer route settles in roughly 8 to 20 seconds. For other assets, expect a few minutes to bridge in, though withdrawing back to Ethereum can take about a week due to the optimistic rollup challenge period.
Do I need to bridge if my funds are on Coinbase? No. You can withdraw directly from Coinbase Exchange to a Base address with no bridge involved at all, which is also the lowest-risk option available.
Is CCTP safer than a regular bridge? Structurally, yes. CCTP burns and mints native USDC directly rather than locking funds behind a wrapped-asset bridge contract, removing the liquidity-pool and custodian risks that caused several major bridge hacks.
What should I do if I think I connected my wallet to a fake bridge? Move any remaining assets to a fresh wallet immediately, revoke any token approvals you granted using a revocation tool, and save the URL, transaction hashes, and screenshots in case you need to report it.
Should I use a direct bridge or an aggregator like LI.FI? For USDC, prefer a direct CCTP route when it's exposed to you. For other assets, an aggregator is usually fine for routine transfers since it's comparing routes for you automatically, just verify the aggregator's own URL before connecting a wallet, same as any other bridge.
Why does bridging back from Base to Ethereum take so much longer than bridging in? Base is an optimistic rollup, and withdrawals back to Ethereum have to pass through a challenge period, typically about a week, that lets the network dispute fraudulent withdrawals before they finalize. Deposits into Base don't need that same window, which is why the two directions feel so different.
Can I speed up a slow withdrawal back to Ethereum? Some third-party services offer "fast withdrawal" liquidity for a fee, effectively fronting you the funds immediately and collecting the official withdrawal themselves once the challenge period ends. That convenience comes with its own counterparty risk, so weigh the fee against how urgently you actually need the funds on Ethereum.
Bridging to Base isn't more dangerous than bridging anywhere else in crypto, but the rules changed when the official bridge was deprecated, and a lot of the guides still floating around haven't caught up. Use Coinbase's withdrawal route if you can, CCTP for USDC, and always type the URL yourself. That covers most of what actually goes wrong.


