How to add the Arbitrum One network to your wallet?

Adding Arbitrum One to MetaMask

1. Open MetaMask and click the network selector dropdown located at the top of the interface.

2. Select Add Network from the bottom of the list.

3. Choose Arbitrum One from the preset networks if it appears in the list—this option is available in newer MetaMask versions.

4. If not listed, manually enter the network details: Network Name as “Arbitrum One”, RPC URL as “https://arb1.arbitrum.io/rpc”, Chain ID as “42161”, Currency Symbol as “ETH”, and Block Explorer URL as “https://arbiscan.io”.

5. Click Save to confirm the configuration and activate the network.

Verifying Connection Integrity

1. After saving, ensure the MetaMask interface displays “Arbitrum One” in the network selector with no warning icons.

2. Visit arbiscan.io and paste your wallet address to verify that transaction history or balance appears under the Arbitrum tab.

3. Send a small test transaction—such as transferring 0.001 ETH—to confirm gas estimation and confirmation behavior aligns with Arbitrum’s low-fee model.

4. Check that the transaction hash resolves on Arbiscan within seconds and finalizes in under one minute.

5. Confirm that your wallet’s token list includes native ETH and popular Arbitrum-native tokens like ARB, GMX, and MAGIC without manual contract address input.

Token Visibility and Custom Asset Integration

1. MetaMask does not auto-detect all Arbitrum tokens by default—even those verified on Arbiscan.

2. To add a custom token, click Import Tokens in the Assets tab, then switch to the “Custom Token” tab.

3. Paste the token’s contract address from Arbiscan into the field; MetaMask will auto-populate symbol and decimals if the token is verified.

4. For widely used tokens such as UNI on Arbitrum, entering the official Uniswap Arbitrum contract address triggers automatic recognition of name, symbol, and logo.

5. Avoid adding tokens from unverified sources—always cross-check contract addresses against official project documentation or Arbiscan’s verified contracts section.

Security Considerations During Setup

1. Never import a network using an RPC URL from an untrusted website or social media post—only use official Arbitrum sources like arbitrum.io.

2. Double-check the Chain ID value: Arbitrum One uses “42161”; Arbitrum Nova uses “42170”—confusing them may lead to failed transactions or lost assets.

3. Disable “Connected Sites” permissions for dApps you do not actively use—this prevents unauthorized network switches or token approvals.

4. Ensure hardware wallet users have firmware updated to support Arbitrum’s EVM-equivalent execution layer before initiating any bridge transfers.

5. Avoid clicking “Approve” on token allowance requests unless you fully understand the scope and duration of the permission being granted.

Frequently Asked Questions

Q: Why does my ETH balance show zero after switching to Arbitrum One?A: ETH on Ethereum Mainnet is not automatically mirrored on Arbitrum. You must bridge ETH using the official Arbitrum Bridge or a supported third-party bridge like Across or Synapse.

Q: Can I use the same seed phrase for Arbitrum One and Ethereum Mainnet?A: Yes—Arbitrum One is an EVM-compatible L2 chain. Your private keys and derivation path remain identical; only the execution environment differs.

Q: Do I need separate gas tokens for Arbitrum One?A: No—ETH serves as the native gas token on Arbitrum One. You do not require ARB or any other token to pay for transaction fees.

Q: What happens if I send tokens to an Ethereum address on Arbitrum without bridging first?A: The tokens will reside at that address on Arbitrum but remain inaccessible until bridged correctly. They are not lost—but cannot be used until the proper cross-chain transfer is completed.