Bridges to Base after bridge.base.org

You went looking for the Base bridge, arrived at bridge.base.org, and found it retired. Two questions follow, and this article answers both: what Base's own documentation points to instead, and whether you need a bridge at all — because if the coins are sitting on an exchange account rather than in your own wallet, a withdrawal straight into the Base network does the same job with fewer moving parts. The network itself, its parameters and the routes that are open right now live on our Base ecosystem hub.

What actually happened to bridge.base.org

Base documentation states it without decoration: "The bridge previously at bridge.base.org has been deprecated." No reason is given there, and we will not invent one. Read the sentence carefully instead, because it is a statement about a web interface and not about the network: no assets were stranded, no route was removed from the protocol, and nothing you hold on Base became less reachable that day.

The distinction is where most of the confusion starts. A bridge in the OP Stack sense is a pair of smart contracts — one on Ethereum, one on Base — that lock assets on one side and make them available on the other. A bridge UI is a website that composes those contract calls so you do not have to. One such website was retired. The contracts it talked to are part of the chain.

The bridge is contracts, not a front end

Deposits into Base and withdrawals out of it run through the standard OP Stack bridges. On the Base side, those contracts sit at fixed, published addresses: L2StandardBridge at 0x4200000000000000000000000000000000000010 and WETH9 at 0x4200000000000000000000000000000000000006, both listed in Base's own contract reference. They are properties of the chain, not of any particular interface pointed at them.

Direction matters more than most guides admit. Moving assets from Ethereum into Base completes when the deposit transaction is processed. Moving them back out is a different mechanism: Base's protocol specification describes withdrawals to Ethereum as passing through a challenge window, the period during which anyone can challenge invalid state transitions using fault proofs. That is the security model doing its job. We deliberately print no duration here — treat the withdrawal as "not immediate", and read the specification if the precise behaviour matters to your case.

When you need a bridge, and when an exchange is simpler

A bridge is the right tool in one situation: the asset already sits in a self-custody wallet on another chain, and you want it on Base. Then a bridge is what moves it, and there is no way around a contract interaction.

It is the wrong tool when the asset is on an exchange. In that case the exchange sends it to Base for you, and you skip the bridge entirely. Base docs make this point about Coinbase specifically — a direct withdrawal there is "not technically a bridge", because assets are sent straight to the Base network — and from your side of the screen every other exchange with the Base network enabled behaves the same way: you pick Base as the withdrawal network, you receive coins on Base.

Which of the two costs less is not a question anyone should answer in prose: it depends on the asset, on the exchange's own fee schedule, which it can change without telling anyone, and on conditions at the moment you press the button. Compare the exchange withdrawal cost in the table further down against the quote the bridge shows you, and decide with both in front of you.

The routes Base documentation points to

Base's ecosystem-bridges page lists the routes it considers relevant, each with a different job:

• Superbridge — Ethereum to Base, for ETH and ERC-20 tokens. Named in the docs under the domain superbridge.app.
• Brid.gg — Ethereum to Base. Named in the docs under the domain brid.gg.
• Base–Solana Bridge — bidirectional transfers between Base and Solana, for assets that live on Solana rather than on Ethereum.
• Garden — the Bitcoin route: BTC into cbBTC on Base.
• Direct withdrawal from Coinbase — listed alongside the bridges, and explicitly not a bridge in the technical sense.

Two things about this list. First, it is Base's list, not a recommendation of ours: we have audited none of these services and deliberately do not link to them from this page. Open the ecosystem-bridges page in the documentation and take the link from there. Second, Base docs disclaim responsibility for third-party services in so many words — a name on that page is a pointer, not an endorsement, and the counterparty risk stays yours.

How to be sure you are on the real site

Base docs name these services by domain rather than hosting them, so the last step is always yours. The defence is procedural.

1. Start at docs.base.org every time and follow the outbound link from there. Never arrive at a bridge from a search result, a direct message or a social post, even one that looks official.
2. Read the domain character by character before connecting a wallet. Substituted letters and extra words are the whole trick.
3. Bookmark the page you reached through the documentation and use the bookmark afterwards.
4. Send a small test amount first and confirm it arrived. This catches a wrong network as well as a wrong site.
5. Never enter a seed phrase into a bridge. No bridge needs one.

Withdrawing to Base from an exchange: the live picture

This section contains affiliate links. Yieldo may earn a commission at no extra cost to you.

The table below is the comparison the prose above keeps deferring to: what each exchange charges to withdraw into the Base network, what its minimum is, and whether the route is open right now. Data comes from exchange APIs and changes without notice; the freshness date sits next to the table, and this page was last reviewed 11 September 2026. Read three things from it — the network must be Base and not Ethereum, the minimum must be below what you are sending, and a status of "closed" means not today rather than never.

Per-asset views with every exchange in one place are on our pages for USDC withdrawal fees to Base and ETH withdrawal fees to Base. Among the venues whose Base routes we poll are Binance, Bybit and OKX; which of them is worth using on a given day is the table's verdict, not ours.

Checklist before you send

1. Decide the route first: bridge if the asset is in your own wallet on another chain, exchange withdrawal if it is on an account.
2. Check that your wallet is on Base and that the receiving address is one you control. Base is a standard EVM chain, so the address string is the same one you use on Ethereum — which is exactly why a wrong-network send is so easy.
3. If you are moving dollars, make sure you end up with native USDC on Base, the token Circle issues there, and not USDbC — the older "Bridged USDC from Ethereum", which Circle describes as legacy and neither issues nor redeems.
4. Keep a little ETH on Base for gas before you need it, not after. A wallet with tokens and no gas cannot move them.
5. Test with a small amount. Then send the rest.

Once the funds are there, the next question is what they do while they sit: stablecoin yields covers where USDC currently earns on exchanges, with a date attached to every figure. The whole network view — parameters, wallets, bridges and what is open today — stays on the Base hub.

Sources and check date

• Base Documentation — Ecosystem bridges: the deprecation of bridge.base.org, the list of routes and the third-party disclaimer.
• Base Documentation — Base protocol overview: the sequencer and fault proofs.
• Base Documentation — Withdrawals: the challenge window on withdrawals to Ethereum.
• Base Documentation — Base contracts: the L2StandardBridge and WETH9 predeploy addresses.
• Base Documentation — Connect to Base: Base as a standard EVM chain.
• Circle — Native USDC on Base: native USDC versus the legacy USDbC.

Checked on 11 September 2026.