Skip to main content

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.

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.

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.
The trust model depends on who verifies the source-chain event and who can release or mint the destination-chain asset. Native Ethereum ↔ Base bridging uses the OP Stack bridge and fault proof system. Other bridge providers may use different validator sets, liquidity networks, or custody models.
Bridge security and withdrawal timing vary by provider and route. Always verify the destination token, bridge provider, and withdrawal assumptions before moving significant funds.

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.
Double check the token address for ERC-20s You can use any ERC-20 that is supported on the network. You can check what assets are on Base and the corresponding contract address via this hub. Ensure there is an address for base, example. Always test with small amounts to ensure the system is working as expected.
This implementation can only bridge assets to Base. Do not attempt to alter the code to withdraw the assets.

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

GoalTypical route
Move ETH or canonical ERC-20s between Ethereum and BaseUse an Ethereum ↔ Base bridge such as Superbridge or Brid.gg.
Withdraw from Base to Ethereum with native security assumptionsUse the native withdrawal path and account for the 7 day challenge window.
Move assets or messages between Solana and BaseUse the Base-Solana bridge.
Move BTC or BTC-like assets to BaseUse a provider that supports Bitcoin routes to Base, such as Garden.

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

No, the bridge on bridge.base.org has been deprecated.
Navigate to one of the Superchain Bridges to look up your transaction.
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.
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.
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.
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.