Step-by-step
- Read {got} as an integer. 1 is Ethereum, 8453 is Base, 56 is BNB Chain. Use the lookup widget. If {got} is a surprise, the URL is the wrong product’s endpoint.
- Fix the form, then Test & add. Either change chain id to {got} (if that is the network you wanted) or paste an RPC that really serves your id. HTTPS only.
- Avoid Add anyway unless you intend the lie. Add anyway is for intentional aliases, not for ignoring a mismatch. Malicious RPCs can still lie about balances even when ids match.
Probe vs Add anyway
The probe also has settings.networks.probeUnreachable when the URL does not answer. Mismatch is specifically eth_chainId ≠ the number you typed. Duplicate ids error with settings.networks.error.duplicateChainId.
| You typed | Node returned | Typical mistake |
|---|---|---|
| 8453 (Base) | 1 | Copied an Ethereum public RPC |
| 1 | 11155111 | Sepolia endpoint in a mainnet form |
| 56 | 1 | Infura/Alchemy Ethereum URL labeled “BSC” in a scam list |
Chainlist-style pages can be mirrored. Prefer first-party docs or GaurdWallet’s built-in nets (proxy RPC at /api/rpc/evm/{chainId} so Tatum keys never sit in the client).
Built-in nets already exist
Ethereum, BNB Chain, Polygon, Arbitrum, Base and the rest of the catalog do not need a custom row. Enable them in Settings. Custom is for chains we do not ship. Related: add a custom EVM network.
settings.networks.probeMismatch → chain id {got} ≠ form
Default RPC for known ids → https://gaurdwallet.com/api/rpc/evm/{chainId}Matching chain id does not make an RPC honest. It can still censor txs or show fake balances. Use it for convenience, not as a security boundary.
FAQ
Should I always click Add anyway? No. That flag exists for odd but intentional setups. A random mismatch is a wrong URL.
Why not auto-correct the chain id? Silent correction would send funds on a network you did not label. The warning forces you to read {got}.
Does this affect Bitcoin RPC? Custom EVM networks are the probe described here. Bitcoin uses the Esplora-style endpoint in the adapter, not an EVM chain id.