How to add Avalanche to MetaMask? (C-Chain settings)

Understanding Avalanche C-Chain Integration

1. Avalanche operates with three distinct blockchains: the Exchange Chain (X-Chain), Platform Chain (P-Chain), and Contract Chain (C-Chain). The C-Chain is an Ethereum-compatible blockchain that supports smart contracts and EVM-based dApps.

2. MetaMask does not include Avalanche C-Chain by default, so manual configuration is required to interact with tokens, decentralized exchanges, and staking interfaces on Avalanche.

3. Adding the C-Chain enables users to send AVAX, deploy contracts, bridge assets from Ethereum, and access DeFi protocols like Trader Joe, Benqi, and Pangolin.

4. The integration relies on correct RPC endpoint, chain ID, currency symbol, and block explorer URL—any misconfiguration leads to transaction failures or balance mismatches.

Required Network Parameters

1. Network Name: Avalanche Mainnet C-Chain

2. New RPC URL: https://api.avax.network/ext/bc/C/rpc

3. Chain ID: 43114

4. Currency Symbol: AVAX

5. Block Explorer URL: https://snowtrace.io/

6. These values are standardized across all official Avalanche documentation and verified by the Ava Labs engineering team.

Step-by-Step Manual Configuration

1. Open MetaMask and click the network selector dropdown in the top-left corner, then choose “Custom RPC”.

2. Enter the Network Name as “Avalanche Mainnet C-Chain” to distinguish it from testnets or other chains.

3. Paste the RPC URL exactly as https://api.avax.network/ext/bc/C/rpc — no trailing slashes or typos.

4. Input Chain ID 43114 without commas or leading zeros; MetaMask validates this field before saving.

5. Set Currency Symbol to AVAX and confirm Block Explorer URL points to snowtrace.io for accurate transaction lookups.

6. Click “Save”. MetaMask will connect and fetch the latest block height automatically.

Verification and Troubleshooting

1. After saving, switch to the newly added network and check if the balance displays zero AVAX—this indicates successful connection but no funds yet.

2. Attempt a small transfer from an Avalanche wallet like Core or Trust Wallet to verify inbound transaction visibility.

3. If transactions stall or show “Unknown network”, revisit the RPC URL and ensure no ad-blockers or corporate firewalls interfere with the endpoint.

4. A common error occurs when users accidentally select the Fuji testnet RPC instead of mainnet; double-check the URL ends with /ext/bc/C/rpc, not /fuji/.

Frequently Asked Questions

Q: Can I use the same seed phrase to access my Avalanche C-Chain funds in MetaMask?A: Yes. Avalanche C-Chain uses standard Ethereum HD derivation paths (m/44'/60'/0'/0), so your existing MetaMask seed phrase fully controls corresponding C-Chain addresses.

Q: Why does MetaMask show “Not connected” even after adding the network?A: This usually means the RPC endpoint returned an HTTP error. Confirm your internet connection allows outbound HTTPS requests to api.avax.network and that no browser extension blocks the domain.

Q: Do I need to import AVAX as a custom token after adding the network?A: No. AVAX is the native currency of the C-Chain and appears automatically. ERC-20 style tokens like JOE or PNG require manual addition using their respective contract addresses on snowtrace.io.

Q: Is it safe to enter Avalanche’s official RPC URL into MetaMask?A: Yes. https://api.avax.network is operated by Ava Labs and is the canonical public endpoint listed in the official Avalanche documentation and GitHub repositories.