How to Add the Avalanche C-Chain Network to MetaMask

Network Configuration Steps

1. Open the MetaMask browser extension and click the network selector located in the top-center area of the interface.

2. Select “Custom RPC” from the dropdown menu to initiate manual chain setup.

3. Enter “Avalanche C-Chain” as the Network Name in the designated field.

4. Input the official Avalanche C-Chain RPC URL: https://api.avax.network/ext/bc/C/rpc.

5. Set Chain ID to 43114, which is the canonical identifier for the mainnet C-Chain.

6. Specify “AVAX” as the Currency Symbol, matching the native token standard across all official Avalanche documentation.

7. Paste the block explorer URL: https://snowtrace.io/, ensuring seamless transaction verification and contract interaction.

8. Click “Save” to finalize the configuration; the network will appear in the MetaMask network list immediately.

Wallet Connection Verification

1. After saving the network, confirm that the top network indicator displays “Avalanche C-Chain” without any warning icons.

2. Click the account avatar icon and select “Account Details” to inspect the current network context assigned to the active address.

3. Initiate a test transaction by sending 0.001 AVAX to another address on the same chain; successful inclusion in a block confirms full RPC connectivity.

4. Navigate to Snowtrace.io, paste the sender’s address, and verify real-time balance updates and recent transaction history.

5. Attempt to interact with a verified contract such as the official Avalanche Token Router at 0x60aE616428f16691F11a0898D3a3887B82C37D27; successful ABI call execution indicates proper EVM compatibility alignment.

Gas Parameter Optimization

1. Access MetaMask Settings → Advanced → “Show hex data” to enable raw transaction inspection during submission.

2. Observe default gas limit values when interacting with Avalanche-native dApps; typical contract calls range between 120,000 and 250,000 units.

3. Manually adjust gas price using the “Edit” option before confirming; recommended values hover around 22.5 Gwei under normal load conditions.

4. Monitor pending transaction status via the Avalanche Subnet Explorer to detect anomalies such as stuck or dropped transactions.

5. If multiple consecutive transactions fail, reset the nonce manually in MetaMask Settings → Advanced → “Reset Account” to clear local state inconsistencies.

Token Import Protocol

1. Within the Avalanche C-Chain network view, click “Import Tokens” and select the “Custom Token” tab.

2. Enter the contract address of the target ERC-20 token—examples include JOE at 0x6e84a6216eA6dACC71Ee8E6b09E9C7C22312e9DE or PNG at 0x60781C2586D68229fde47564546784ab3fACA982.

3. Confirm symbol and decimals fields auto-populate based on on-chain metadata retrieval.

4. Click “Next”, then “Add Tokens” to register the asset into the wallet interface.

5. Validate balance visibility and transfer functionality by initiating a small outbound transfer to a secondary wallet address.

Frequently Asked Questions

Q: Why does MetaMask show “Unknown Network” after adding Avalanche C-Chain?A: This occurs when Chain ID 43114 is misentered as 43113 or 43115. Recheck the value in network settings and re-save.

Q: Can I use the same mnemonic phrase to access Avalanche C-Chain on Ledger or Trezor?A: Yes—Avalanche C-Chain supports BIP-44 derivation path m/44'/60'/0'/0/0, compatible with hardware wallets configured for Ethereum-style accounts.

Q: What happens if I send AVAX to an X-Chain or P-Chain address?A: Funds become irretrievable because cross-chain addresses are non-interoperable at the base layer; always verify destination chain context before signing.

Q: Is it safe to import third-party token contracts listed on unofficial forums?A: No—malicious contracts may override approve() logic or drain balances silently; only import tokens verified on Snowtrace.io with ≥3 independent audit reports.