Why Your Wallet Keeps the Old RPC: Choose the Active One
Why is your wallet still using the old RPC after adding a new one? The new endpoint may be saved under the same chain, while the old one remains selected.
By Web3 Report Editorial5 min read
Your wallet can keep using the old RPC because adding an endpoint for a chain does not necessarily select it; you must choose the new RPC, and a dApp may still use its own endpoint for reads.
Wallets identify EVM networks by chain ID and use a selected RPC for each network. Chainlist provides network details, including chain IDs and RPC endpoints. When you add an endpoint from Chainlist, it may join the network entry you already have instead of creating a separate network or changing the active endpoint.
Why does my wallet keep the old RPC?
For the same chain ID, the wallet can store the new URL with the existing network entry while leaving the old RPC selected by default.
- Chain ID: identifies the network entry.
- RPC URL: endpoint the wallet can use to communicate with that network.
- Selected RPC: endpoint currently used by the wallet for that network.
These are related but distinct settings. Adding a network through EIP-3085’s wallet_addEthereumChain asks the wallet to add a chain; the standard does not require the wallet to select it automatically. Wallet behavior varies, but in MetaMask, a request to add a chain prompts for approval and the user may choose to switch to it. When the chain is already known, adding it again may leave you with the existing network entry rather than a second entry for the same chain ID.
So the change from before is often just another RPC URL available under the same network. The old URL remains the active choice until you select the new one in the network settings. If you expected a separate network in the network menu, check the chain ID: a matching ID points to the existing network entry.
Why does the dApp still show the same balance?
A dApp can keep showing data from its own RPC because many apps make read requests through a separately configured endpoint.
Reading and writing can follow different routes. A dApp might query its RPC for balances, token details, transaction history, or contract state. It can do this whether or not your wallet has switched endpoints. In a common setup, the app sends a transaction request through the wallet, which handles signing and submission using its selected network and RPC. That means a wallet RPC change can affect wallet traffic and transaction handling while leaving the data displayed by the app unchanged.
For instance, suppose MetaMask has a new RPC selected, but a trading interface uses a public client configured to read from another provider. The wallet’s network setting does not rewrite that client’s configuration. The page may continue to show the same balances or state until its own read path changes or refreshes. Apps built with wagmi can define transports by chain ID, including a specific HTTP RPC URL, so their read requests can follow that configuration independently of the wallet’s endpoint.
This split has a practical trade-off: you can choose which endpoint the wallet uses without controlling the dApp’s data source. To diagnose a stale balance, compare the wallet’s own balance view with the app’s display. If the wallet view changes but the app does not, the two may be reading through different RPCs.
How do I make the new RPC take effect?
Select the new endpoint in the wallet’s network settings, reload the dApp, and check a wallet-based view or transaction.
In MetaMask, open the network settings for the chain and select the new RPC URL as the default. Confirm you are on the intended chain by checking its network name and chain ID. Then reload the dApp so it can refresh its connection and reads. Chainlist can help you compare the network’s chain ID and endpoint details if you need to confirm which entry you added.
Use the wallet’s own balance view as a first check because it reflects the wallet’s selected network endpoint more directly. For a stronger check, make a transaction only when you already intend to do so, and confirm its network and result. A dApp’s displayed balance alone is a poor test of the wallet RPC switch because its read path may be separate.
When should I contact wallet or dApp support?
Contact wallet support if the selected RPC reverts after you change it, the endpoint fails in the wallet, or the network entry behaves inconsistently with its chain ID. Share the wallet version, chain ID, RPC URL, and the steps you took; never send a recovery phrase or private key.
Contact the dApp’s support team if the wallet’s own view uses the new endpoint but the app continues to show stale or inconsistent data after a reload. Tell them which chain you selected and ask which RPC or transport the app uses for reads. If you are unsure which path is responsible, describe the difference between the wallet view and the app view.
- Same chain ID usually means the RPC was added to an existing network entry.
- Select the new RPC in wallet settings to make it the wallet’s active endpoint.
- A dApp’s reads may use its own RPC, independent of the wallet setting.