Wrong network RPC error checklist

Checklist

1. Confirm the intended chain row on Main.net and open its primary source links.
2. Compare the decimal chain ID with the hexadecimal chain ID used by JSON-RPC.
3. Call eth_chainId on the configured RPC endpoint and compare the response.
4. Confirm the explorer URL and gas token belong to the same chain row.
5. Regenerate wallet configuration from the EIP-3085 JSON before copying settings.
6. For production apps, use dedicated infrastructure and monitoring rather than relying on a shared public RPC endpoint.

Common mismatch points

Decimal vs hex chain ID

Many docs show decimal IDs, while JSON-RPC returns hexadecimal IDs such as 0x2105 for Base.

RPC URL from another network

An endpoint can respond successfully while still reporting a different chain ID than the app expects.

Copied wallet settings

Copied settings can become stale. Prefer rows with source links and regenerate EIP-3085 JSON from the latest fields.

Reference rows

Useful references

• Chain ID list for reviewed decimal and hex IDs.
• EIP-3085 wallet config JSON for copy-ready read-only settings.
• /api/v1/chains.json for JSON chain fields.