---
name: avax-networks
description: Configure Avalanche C-Chain, Fuji or a named L1 without mixing RPCs, chain IDs and native assets.
---

# Networks & chain identity

Source review: 2026-09-06. Recheck network-dependent facts before use.

1. Select the network from the reference below; for a custom L1 retrieve its operator-published RPC, EVM chain ID, native currency, explorer and supported VM version. Finish with one coherent chain configuration, not a mixture of networks.
2. Read `eth_chainId` from the configured EVM RPC and compare it with the intended ID before reads or signing. Recheck after a wallet network change. An Avalanche network ID, EVM chain ID and blockchain ID are distinct identifiers.
3. Route Solidity and ERC-token work to C-Chain or an explicitly EVM-compatible L1. P-Chain coordinates validators; X-Chain is an asset chain. Their transaction formats and address systems are not ordinary C-Chain ERC-20 transfers.
4. For cross-chain work retain the chain's Avalanche blockchain ID separately and read [Interchain](../interchain/SKILL.md). Finish with a checked destination identity, not just a wallet chain number.

## Public C-Chain configuration

| Network | EVM chain ID | Public RPC | Native gas asset |
| --- | --- | --- | --- |
| Mainnet | 43114 (0xa86a) | https://api.avax.network/ext/bc/C/rpc | AVAX |
| Fuji testnet | 43113 (0xa869) | https://api.avax-test.network/ext/bc/C/rpc | Test AVAX |

AVAX uses 18 decimals in the EVM. Public RPC endpoints are shared infrastructure, not a capacity guarantee. Fuji token balances and deployments are separate from mainnet.

**Evidence to return:** intended and observed chain ID, RPC host, network label and check time. Never include credential-bearing RPC URLs.

## Primary sources

- [Primary Network configuration](https://build.avax.network/docs/primary-network)
- [C-Chain RPC reference](https://build.avax.network/docs/rpcs/c-chain)

## Prove network identity rather than a configured label

From the executable bundle root run `node examples/network/inspect.mjs`. It verifies raw eth_chainId, captures client version and pins actual block/hash plus a contract/fee probe. A client's configured or static network object must not conceal a mismatched RPC.

`node research/parity-dexes/run-live.mjs` performs live protocol reads; `node research/parity-dexes/fork-execution.mjs` imports C-Chain state into an isolated loopback node. Protocol forks use43114, the core demo uses43113; neither submits public-chain transactions. An executor must bind both the network identifier and intended transport. Do not present local receipts as explorer-resolvable public transactions.

For each L1 retrieve operator-published VM/genesis, RPC, explorer and upgrade rules. Keep EVM chain ID, Avalanche network ID, Avalanche blockchain ID and CCTP domain in separate typed fields. Identical deployment addresses on Fuji/mainnet do not share tokens or allowances. A local fork's opcode support does not establish target-network feature activation.