web3_clientVersion

web3_clientVersion returns a free-form string identifying the client software and version running behind an Avalanche C-Chain endpoint. The C-Chain's EVM is powered by coreth, a Geth-derived client embedded in AvalancheGo, so the string typically reflects that lineage and its build details. It is a quick way to learn what software is answering your calls on the chain where AVAX pays for gas under Snowman/Avalanche consensus. Send the request to https://avalanche.therpc.io/YOUR_API_KEY (chain ID 43114, 0xa86a).

Use cases

• Detect the underlying client type and version answering your C-Chain calls to decide whether client-specific behavior — such as availability of the txpool or debug namespaces in coreth — can be relied on.
• Log the node identity string alongside request traces during infrastructure diagnostics, so you can correlate behavior with a specific client build.

Parameters

This method takes no parameters. Pass an empty array [].

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": "web3_clientVersion",
7    "params": [],
8    "id": 1
9  }'

Try it live in the Avalanche playground.

Errors & troubleshooting

Common pitfalls

• Managed RPC endpoints like https://avalanche.therpc.io/YOUR_API_KEY may return a custom or redacted string rather than the exact upstream coreth build, so treat the value as informational rather than authoritative.
• Do not gate production logic on parsing this string for feature detection. Instead, probe for a method's availability directly and handle a "method not found" error, since the version text format is not standardized across clients.

Supported networks

• Mainnet — Chain ID: 43114
• Fuji

See also

• net_version

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":"web3_clientVersion","params":[]}'