How to bridge ETH to Arbitrum using MetaMask? (Step-by-Step)

Setting Up MetaMask for Arbitrum Compatibility

1. Open the MetaMask extension in your browser and click the profile icon in the top-right corner.

2. Navigate to Settings → Advanced and toggle on “Show Test Networks” to expose Ethereum testnets.

3. Switch to the Ethereum Mainnet or a supported testnet such as Sepolia, depending on your target deployment environment.

4. Confirm that your MetaMask version supports EIP-3085 custom network addition via wallet_addEthereumChain RPC calls.

5. Ensure your browser allows third-party script execution, as Arbitrum bridges rely on injected web3 providers for signature handling.

Adding the Arbitrum Network Manually

1. Visit the official Arbitrum documentation page listing current RPC endpoints and chain IDs.

2. In MetaMask, click the network dropdown and select “Add Network” → “Add a network manually”.

3. Input the Arbitrum One network parameters: Chain ID 42161, RPC URL https://arb1.arbitrum.io/rpc, Currency Symbol ETH, Block Explorer URL https://arbiscan.io.

4. Save the configuration and verify the network appears under the dropdown menu with the Arbitrum logo.

5. Confirm that the balance display updates correctly when switching to the Arbitrum network, even if it shows zero ETH initially.

Initiating the Bridge Transaction

1. Go to the official Arbitrum Bridge interface at bridge.arbitrum.io while connected to Ethereum Mainnet in MetaMask.

2. Connect your MetaMask wallet using the “Connect Wallet” button located prominently on the page.

3. Enter the amount of ETH you wish to transfer from Ethereum to Arbitrum; minimum thresholds apply based on gas estimation.

4. Click “Deposit” and approve the transaction in your MetaMask popup; this initiates a Layer 1 transaction requiring Ethereum block confirmations.

5. Wait for the status indicator to change from “Pending” to “Ready to Withdraw”, which typically takes between 7 and 20 minutes depending on Ethereum congestion.

Confirming Receipt on Arbitrum

1. After the deposit is finalized, switch MetaMask’s active network to Arbitrum One.

2. Refresh your wallet view; the bridged ETH should appear in your balance without requiring manual token import.

3. Verify the transaction hash on Arbiscan by clicking the “View on Arbiscan” link provided in the bridge UI.

4. Check that the “From” address matches your Ethereum wallet address and the “To” address corresponds to your Arbitrum wallet address.

5. Observe the “Status” field showing “Success” and confirm the block number aligns with recent Arbitrum block heights.

Frequently Asked Questions

Q: Can I bridge tokens other than ETH using the official Arbitrum Bridge?Yes, the Arbitrum Bridge supports ERC-20 tokens deployed on Ethereum Mainnet, provided they are whitelisted and have canonical bridging contracts deployed on Arbitrum.

Q: Why does my bridged ETH not appear immediately after the L1 transaction confirms?The delay occurs because the Arbitrum sequencer must ingest the state commitment, process it through the Nitro stack, and publish it to the Arbitrum chain before balances reflect the update.

Q: Is it possible to reverse an Arbitrum bridge transaction once initiated?No, all bridge operations are irreversible after Ethereum confirmation; users must ensure correct recipient addresses and amounts before signing.

Q: Do I need separate private keys for Ethereum and Arbitrum addresses?No, Arbitrum uses the same cryptographic key derivation path as Ethereum; your MetaMask seed phrase controls both addresses identically.