Bridging moves assets or messages between Base and another chain. The user experience can look like a single transfer, but the underlying mechanism depends on the source chain, destination chain, asset, and bridge provider. Base supports several bridging paths, including canonical Ethereum ↔ Base bridging, Base ↔ Solana bridging, and third-party bridges for assets such as BTC. For protocol-level details, see the bridging specifications.Documentation Index
Fetch the complete documentation index at: https://base-a060aa97-mux-base-docs-codex-moly1dzt.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
How bridging works
Most bridge designs use one of three patterns:- Lock and mint: the source-chain asset is locked in a bridge contract or custody system, and a representation is minted on the destination chain.
- Burn and release: a bridged representation is burned on one chain, and the original or equivalent asset is released on the other chain.
- Message passing: a source-chain action emits a message that is verified and executed on the destination chain.
Ethereum ↔ Base
Ethereum is Base’s L1 settlement layer. Native deposits and withdrawals between Ethereum and Base use OP Stack bridge contracts and cross-domain messaging.Deposits to Base
Deposits start on Ethereum. A user deposits ETH or an ERC-20 through an L1 bridge contract, the deposit is included on Ethereum, and the corresponding L2 transaction is derived and executed on Base. Deposits typically complete much faster than withdrawals because they do not need the fault proof challenge window.Withdrawals to Ethereum
Withdrawals start on Base and complete on Ethereum. The user initiates a withdrawal on Base, the withdrawal is proven against an output root on Ethereum, and the funds can be finalized after the fault proof challenge window if the output root remains valid.Only Base-to-Ethereum withdrawals through the native bridge use the 7 day finality period. Normal Base transactions do not wait 7 days. See Transaction Finality.
Bridge providers
Several bridge interfaces support Ethereum ↔ Base transfers: See the sample code repository to see how to bridge ETH and ERC-20s from Ethereum to Base.Solana ↔ Base
The Base-Solana bridge enables bidirectional token transfers and message passing between Base and Solana. It uses bridge contracts/programs and validators to verify cross-chain messages between the two ecosystems. Use this route when you need to move SOL, SPL tokens, wrapped tokens, or application messages between Solana and Base.Base-Solana Bridge
Read the implementation guide, contract addresses, token wrapping flow, and message passing examples.
Terminally Onchain
Use a production terminal UI for bridging and cross-chain contract calls.
For Mainnet, Sepolia, and Solana Devnet addresses, see the Base-Solana Bridge documentation.
Bitcoin → Base
Garden is a fast non-custodial Bitcoin bridge that enables you to bridge BTC and other supported assets from Ethereum, Solana, and more, directly to Base.Supported networks
Choosing a route
| Goal | Typical route |
|---|---|
| Move ETH or canonical ERC-20s between Ethereum and Base | Use an Ethereum ↔ Base bridge such as Superbridge or Brid.gg. |
| Withdraw from Base to Ethereum with native security assumptions | Use the native withdrawal path and account for the 7 day challenge window. |
| Move assets or messages between Solana and Base | Use the Base-Solana bridge. |
| Move BTC or BTC-like assets to Base | Use a provider that supports Bitcoin routes to Base, such as Garden. |
Related specs and references
- Standard Bridges spec explains the protocol bridge model.
- Deposits spec describes Ethereum-to-Base deposits.
- Withdrawals spec describes Base-to-Ethereum withdrawals.
- Base contracts lists deployed bridge contract addresses.
- Transaction Finality explains withdrawal finality.
Disclaimer
Coinbase Technologies, Inc., provides links to these independent service providers for your convenience but assumes no responsibility for their operations. Any interactions with these providers are solely between you and the provider.FAQ
Can I still use the bridge on bridge.base.org?
Can I still use the bridge on bridge.base.org?
No, the bridge on bridge.base.org has been deprecated.
I used bridge.base.org in the past, how do I find my deposit or withdrawal?
I used bridge.base.org in the past, how do I find my deposit or withdrawal?
Navigate to one of the Superchain Bridges to look up your transaction.
Why has Base deprecated the bridge on bridge.base.org?
Why has Base deprecated the bridge on bridge.base.org?
Base is committed to decentralization and the Superchain vision. Leveraging the community to bootstrap the Superchain bridges is a step in that direction; increasing censorship resistance and decentralization.
Who operates the Superchain Bridges like Garden.finance, Superbridge.app and Brid.gg?
Who operates the Superchain Bridges like Garden.finance, Superbridge.app and Brid.gg?
Superchain Bridges are operated by third parties, not by Coinbase Technologies, Inc. (“Coinbase”). Coinbase does not control, operate, or assume any responsibility for the performance of these external platforms. Before using any Superchain Bridge, you may be required to agree to their terms and conditions. We strongly recommend you review these terms carefully, as well as any privacy policies, to understand your rights and obligations. The integration or inclusion of the Superchain Bridges does not imply an endorsement or recommendation of any bridge by Coinbase.
How does the Base-Solana bridge work?
How does the Base-Solana bridge work?
The Base-Solana bridge uses validators to verify cross-chain messages. When bridging from Solana to Base, tokens are locked on Solana and minted on Base. When bridging from Base to Solana, tokens are burned on Base and unlocked on Solana. See the full documentation for implementation details.
What if I have a question, issue, or problem?
What if I have a question, issue, or problem?
The Base Discord community is available around the clock for general questions,
assistance and support! You can create a support ticket in the #general-support
channel.