How to Add Base Network to MetaMask

Adding Base to MetaMask requires entering its network configuration — chain ID 8453, an RPC URL, currency symbol, and block explorer — which can be done automatically through a one-click prompt from a trusted dapp or manually through MetaMask's network settings menu.

Fastest method: let a dapp add it for you

Many Base-native and Base-supporting applications, including the official Base Bridge, will prompt MetaMask to add the network automatically the first time you try to connect and transact. If the prompt comes from a site you've verified is the genuine, official version, approving it is the simplest way to get set up, since MetaMask fills in the correct network details for you without manual entry.

Manual setup steps

1. Open MetaMask and click the network selector.
2. Choose "Add network", then "Add a network manually."
3. Enter the following:

Field	Value
Network name	Base
New RPC URL	https://mainnet.base.org
Chain ID	8453
Currency symbol	ETH
Block explorer URL	https://basescan.org

4. Save, then switch to the Base network using the selector.

As with any manual network entry, verify these details against Base's own official documentation before saving, rather than trusting a link or screenshot from an unverified source.

Confirming the setup worked

After adding the network, confirm your wallet reflects a sensible ETH balance (zero if you haven't bridged any funds yet) and that your address matches what you see when looking it up on the Basescan block explorer.

You still need to bridge funds separately

Adding the network configuration to MetaMask only lets your wallet communicate with Base — it doesn't move any assets there. To actually use Base DeFi, you'll need to bridge ETH or tokens over from Ethereum mainnet or another supported chain; see our full walkthrough in how to bridge to Base.

Common issues and fixes

• Duplicate network entries: check your existing network list first — MetaMask may have already auto-added Base from a previous dapp visit.
• RPC connectivity issues: if the public endpoint is temporarily slow or unresponsive, check Base's official documentation for alternative RPC providers.
• Funds not appearing after bridging: verify the bridging transaction actually completed on Base by checking the transaction hash on Basescan before troubleshooting your wallet configuration.
• Confusing Base with another similarly named network: double-check the chain ID (8453) matches exactly, since scam or copycat networks with similar names have appeared in the past.

A note on alternative wallets

This guide covers MetaMask specifically since it's one of the most commonly used wallets for interacting with L2s, but the same network details — chain ID 8453, the RPC endpoint, and block explorer — apply if you're configuring Base in a different wallet. Most modern wallets support an equivalent "add custom network" flow, even if the exact menu wording differs. If your wallet offers a network list import feature, that can reduce the chance of a manual entry mistake, so long as the list itself comes from a source you trust.

What to do once you're connected

With Base configured and funds bridged in, you can begin exploring its DeFi ecosystem, including decentralized exchanges, lending markets, and liquid staking options that have grown quickly on the network. See our full guide to DeFi on Base for an overview, and review DeFi wallet security fundamentals before depositing significant funds anywhere.

Checking your setup against the block explorer

A useful final sanity check after adding any new network is to look up your own wallet address on that network's block explorer — in this case Basescan — and confirm the balance and transaction history shown there matches what MetaMask displays. If the two ever disagree, it usually points to a misconfigured RPC endpoint rather than an actual discrepancy in your funds, and re-entering the official RPC URL typically resolves it.

Why network details matter more than they might seem

It's easy to treat adding a network as a trivial formality, but an incorrectly entered chain ID or RPC URL can cause confusing downstream problems — transactions failing silently, balances appearing incorrect, or a wallet connecting to an unintended or malicious network entirely if a fraudulent RPC endpoint were ever entered. Taking the extra minute to verify each field against Base's own official documentation before saving is a small effort that avoids a meaningfully larger headache later, particularly once you start moving real funds across the network.

Bottom line

Setting up MetaMask for Base takes only a couple of minutes using its chain ID (8453) and official RPC endpoint, whether through an automatic dapp prompt or manual entry. Remember that adding the network is separate from funding it — you'll still need to bridge assets over before you can use any Base-based application.