How to Send ETH From MetaMask to an Arbitrum Wallet Address

Prerequisites for Cross-Chain ETH Transfer

1. Ensure your MetaMask wallet is updated to the latest stable version compatible with Arbitrum networks.

2. Confirm that the Arbitrum network is already added to your MetaMask network list—either Arbitrum One or Arbitrum Nova.

3. Verify that your MetaMask account holds sufficient ETH on Ethereum Mainnet to cover both the transfer amount and gas fees for bridging.

4. Double-check the destination Arbitrum address format—it must be a valid 42-character hexadecimal address beginning with “0x”.

5. Disable any third-party browser extensions that may interfere with MetaMask’s interface or signature requests.

Step-by-Step Bridge Execution

1. Open MetaMask and switch to the Ethereum Mainnet network using the network selector dropdown.

2. Click the “Send” button and paste the recipient’s Arbitrum address into the “To” field.

3. Enter the desired ETH amount, ensuring it exceeds the minimum threshold required by the official Arbitrum bridge.

4. Click “Next”, then select “Bridge to Arbitrum” when prompted—this triggers the canonical bridge flow via bridge.arbitrum.io.

5. Review the transaction summary: expected confirmation time, estimated L1 gas cost, and final receipt chain. Approve the initial Ethereum transaction.

Wallet Configuration for Arbitrum Receipt

1. After the Ethereum-side transaction confirms, navigate to the Arbitrum network in MetaMask’s network menu.

2. If Arbitrum is not yet added, manually insert its RPC details: Network Name Arbitrum One, New RPC URL https://arb1.arbitrum.io/rpc, Chain ID 42161.

3. Import the same private key or seed phrase used on Ethereum—no new wallet creation is needed.

4. Wait for the bridge’s second-phase confirmation; this usually takes 7–15 minutes under normal congestion.

5. Refresh the Arbitrum balance view—ETH should appear automatically without manual token addition.

Security Verification Practices

1. Always cross-verify the bridge domain: only use bridge.arbitrum.io—never arbitrum-bridge.com or similar lookalikes.

2. Inspect the transaction hash on Etherscan (for Ethereum) and Arbiscan (for Arbitrum) to confirm identical sender, recipient, and value fields.

3. Reject any pop-up requesting signature of an unknown contract call during bridging—legitimate flows only require two signed transactions: approve and deposit.

4. Never share your secret recovery phrase—even if prompted by a “verification” modal mimicking MetaMask UI.

5. Monitor pending status using the bridge’s built-in tracking ID instead of relying solely on wallet balance updates.

Frequently Asked Questions

Q1: Can I send ETH directly from MetaMask to an Arbitrum address without bridging?No. ETH on Ethereum Mainnet and ETH on Arbitrum are separate assets. A bridge protocol must lock ETH on Ethereum and mint equivalent ETH on Arbitrum.

Q2: Why does my ETH not appear immediately on Arbitrum after the first transaction confirms?Because the canonical bridge enforces a seven-day challenge period for withdrawals—but deposits follow a faster, deterministic path requiring only one L1 confirmation and subsequent L2 settlement.

Q3: What happens if I send ETH to an Arbitrum address while MetaMask is still set to Ethereum Mainnet?The transaction will execute on Ethereum, sending ETH to that address on Ethereum—not Arbitrum. The funds remain on Ethereum unless manually bridged later.

Q4: Is it safe to use third-party bridges like Synapse or Hop instead of the official Arbitrum bridge?Third-party bridges introduce additional smart contract risk and rely on external validator sets. The official bridge uses verified, audited contracts deployed by Offchain Labs and inherits Ethereum’s security assumptions for deposits.