net_version

net_version returns the network ID of the chain a node is connected to, as a decimal string. For Avalanche C-Chain mainnet — the EVM chain where AVAX pays for gas, secured by Snowman/Avalanche consensus — the network ID is "43114", matching its chain ID 43114 (0xa86a). It is a fast way to confirm an endpoint really is the network you expect before you trust its data or send transactions. Send the request to https://avalanche.therpc.io/YOUR_API_KEY and check the returned string.

Use cases

• Verify a wallet or dApp is pointed at C-Chain mainnet ("43114") before submitting an AVAX transaction, guarding against accidentally broadcasting to the wrong network.
• Differentiate C-Chain mainnet from the Fuji testnet in environment-aware logic, branching configuration based on the network ID the node reports.

Parameters

هذا الأسلوب لا يأخذ أي معاملات. مرر مصفوفة فارغة [].

Response

Example request

1curl https://avalanche.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "net_version",
7    "params": [],
8    "id": 1
9  }'

Try it live in the Avalanche playground.

Errors & troubleshooting

Common pitfalls

• Network ID and chain ID coincide on the C-Chain (both 43114), but that is not universal — on some networks they differ. For transaction signing and replay protection, always derive the value from eth_chainId rather than net_version.
• The value comes back as a decimal string ("43114"), not a hex quantity — unlike most other numeric JSON-RPC responses such as net_peerCount. Parse it as base 10, not hex.

Supported networks

• Mainnet — Chain ID: 43114
• Fuji

See also

• eth_chainId
• net_listening
• net_peerCount

1curl https://avalanche.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"net_version","params":[]}'