How to Add Arbitrum to MetaMask Wallet?

Arbitrum Network Configuration Steps

1. Launch the MetaMask browser extension and ensure it is updated to the latest stable version compatible with Arbitrum One and Arbitrum Sepolia.

2. Click the network selector dropdown located in the top-center of the interface, then select Add Network.

3. Choose Add a network manually instead of relying on automatic detection, as manual entry guarantees parameter accuracy.

4. Input the following official Arbitrum One parameters: Network Name = Arbitrum One; New RPC URL = https://arb1.arbitrum.io/rpc; Chain ID = 42161; Currency Symbol = ETH; Block Explorer URL = https://arbiscan.io.

5. Confirm all fields match exactly and click Save. The wallet interface will refresh and display Arbitrum One as the active network.

Verification and Initial Balance Check

1. After saving, confirm the top network indicator changes from “Ethereum Mainnet” to “Arbitrum One” without delay.

2. Open the account overview and verify the balance remains zero unless previously funded — Arbitrum does not auto-transfer ETH from Ethereum Mainnet.

3. Access Arbiscan directly using the wallet’s connected address to inspect on-chain activity, including pending or confirmed transactions linked to the Arbitrum chain.

4. Attempt a simple balance query via the MetaMask asset panel — if no tokens appear, it confirms the wallet is isolated to Arbitrum’s execution layer and requires native ETH deposit or bridging.

Bridging ETH from Ethereum to Arbitrum

1. Navigate to the official Arbitrum Bridge at bridge.arbitrum.io while MetaMask is connected to Ethereum Mainnet.

2. Connect the same wallet, enter the desired ETH amount, and initiate the deposit transaction — this triggers a Layer 1 confirmation followed by Layer 2 settlement.

3. Wait for the L1 transaction to receive at least one block confirmation before proceeding; average wait time ranges between 15–30 seconds under normal congestion.

4. Monitor the bridge status page until it displays “Ready to claim” — then switch MetaMask to Arbitrum One and click “Claim” to finalize the transfer on L2.

5. Refresh MetaMask after claiming; the newly bridged ETH should appear under the Arbitrum network balance within five seconds.

Token Import and Asset Management

1. To add custom ERC-20 tokens deployed on Arbitrum, click the “Import tokens” button beneath the asset list while connected to Arbitrum One.

2. Select the “Custom token” tab and paste the correct Arbitrum-native contract address — addresses from Ethereum Mainnet or other chains will fail validation.

3. MetaMask automatically retrieves token symbol, decimals, and name from the contract’s public interface if the address is valid and the RPC responds.

4. Confirm import; the token appears in the asset list with real-time balance reflecting only Arbitrum-based holdings — no cross-chain balance aggregation occurs.

5. For widely adopted tokens like USDC.e or ARB, MetaMask may auto-suggest them when searching by name — always validate the contract address against Arbiscan before confirming.

Frequently Asked Questions

Q1. Why does my ETH balance show zero after switching to Arbitrum One?ETH on Ethereum Mainnet is not natively available on Arbitrum. Users must bridge assets using bridge.arbitrum.io or a trusted third-party bridge supporting Arbitrum’s canonical bridge protocol.

Q2. Can I use the same seed phrase to access Arbitrum accounts?Yes. Arbitrum uses the same derivation path and cryptographic key generation as Ethereum. The same 12-word recovery phrase unlocks identical addresses across both chains, provided the wallet software supports EVM-compatible HD wallets.

Q3. What happens if I send tokens to an Arbitrum address from BSC or Polygon?The tokens become irretrievable. Arbitrum has no shared state or validator coordination with BSC or Polygon. Cross-chain transfers require bridges explicitly supporting both source and destination chains.

Q4. Is it safe to input RPC URLs manually?Only official RPC endpoints published by Arbitrum.io or verified infrastructure providers such as Infura, Alchemy, or Pocket Network should be used. Unverified RPCs may log private keys or return manipulated balances.