net_version

net_version returns the network ID of the chain a node is connected to, as a decimal string. For Polygon PoS mainnet — the MATIC-fee network — the value is "137", which matches its chain ID. It is a fast way to confirm you are talking to Polygon rather than Ethereum or another EVM chain before sending requests. Call it against the Polygon mainnet endpoint at https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89) and you should get "137" back.

Use cases

• Verify that a wallet or dApp is connected to Polygon mainnet ("137") before submitting a MATIC transaction, guarding against accidental sends on the wrong network.
• Differentiate Polygon mainnet ("137") from the Amoy testnet ("80002") in environment-aware application logic so staging and production hit the right chain.

Parameters

此方法不需要任何参数，传入空数组 [] 即可。

Response

Example request

1curl https://polygon.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 Polygon playground.

Errors & troubleshooting

Common pitfalls

• On Polygon mainnet the network ID and chain ID happen to coincide at 137, but they are conceptually distinct and can differ on other networks. For transaction signing always use the chain ID from eth_chainId, not this value.
• The result is a decimal string ("137"), not a hex value — unlike most numeric Polygon RPC responses, which return 0x-prefixed hex. Parse it as base-10.

Supported networks

• Mainnet — Chain ID: 137
• Amoy — Chain ID: 80002

See also

• eth_chainId
• net_listening
• net_peerCount

1curl https://polygon.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":[]}'