Can Switching a Chainlist RPC Change My Balance?

If your wallet shows a different balance after you change a Chainlist RPC endpoint, that switch alone did not move or remove your assets. An RPC endpoint is the server your wallet asks for blockchain data. A changed number can reflect another chain, account, token contract, point in chain history, or an inaccurate response. The first task is to establish what each number represents.
What a Chainlist RPC Switch Changes
Changing the saved RPC URL changes where your wallet sends JSON-RPC balance queries. The wallet asks that endpoint for data, such as the balance of a native coin or the number of units held by a token contract. Replacing the URL does not sign, broadcast, or execute a transfer. Your assets remain recorded on the chain unless an on-chain event changes them.
For example, suppose you switch endpoints and a token balance immediately appears lower. The new endpoint may be behind the latest block, or your wallet may still be showing data cached from the previous one. Neither display, by itself, shows that the endpoint moved tokens. You need observations of the same asset at the same chain state to tell whether the difference is real.
Which Balance Are You Comparing?
A meaningful comparison uses the same chain, account address, asset contract, and block context. Start with the active network and the account selected in the wallet. If the wallet is now querying a different chain or account, both balances can be accurate for their respective contexts while answering different questions. The chain ID helps identify a network, but a matching ID alone does not prove that an endpoint returned an accurate balance.
For a token, compare its contract address as well as its name and symbol. Two contracts can use the same display name, and a wallet may discover one automatically while leaving another out of its token list. A missing token row can therefore mean that the wallet has not displayed the contract; it does not establish a zero on-chain balance. If you chose an endpoint from a Chainlist RPC list, the endpoint choice also does not change which token contract holds your units.
Finally, compare observations from roughly the same block height. A block is a batch of transactions added to the chain. If one endpoint reports an earlier block, it may show the balance before a recent transaction. Keep token units separate from the wallet’s estimated fiat value: a changing price quote can alter the displayed value even when the on-chain number of tokens stays fixed.
When Do Two Endpoints Disagree?
Two endpoints can disagree because they observe different blocks, serve stale data, or return different answers for the same request. A lagging node may not yet show a confirmed transaction. The wallet may also retain a cached balance briefly after an endpoint change. If a recent transaction is still pending, one view may anticipate it while another reports only confirmed state.
Chain reorganisations add another complication. Sometimes a recently accepted block is replaced as the chain settles on a different history. A balance observed near that event can genuinely change between observations, even though changing the RPC URL was not the cause. For this reason, note the transaction status and block height before interpreting a difference seen immediately after a switch.
For a stubborn mismatch, compare the account and asset on a relevant block explorer and through an independent endpoint at a comparable block. Agreement between those two sources supports that observation. If they disagree, investigate the chain, contract, block height, and recent transactions before drawing a conclusion. An RPC can return misleading data, so a plausible network name or matching chain ID is insufficient evidence on its own.
What Else Matters When You Change Networks?
Wallet support, possible fees, and the action requested in the wallet prompt affect what happens next.
What if my wallet cannot add the network?
A failed add-network request leaves you needing to confirm which network the wallet actually selected. Some wallets do not support custom EVM networks; others require you to enter the chain ID and RPC URL manually. If the network was never added, a balance shown on the old network is not a comparison with the new one.
Can wallets other than MetaMask use these settings?
Yes, if the wallet supports the relevant EVM network and lets you add or edit its RPC settings. The way it displays tokens and cached balances may differ. Use the chain ID, account address, and token contract to compare results across wallets, rather than assuming matching wallet screens represent matching on-chain state.
Does using it cost anything?
Changing network settings does not itself create a transaction or a gas fee. Sending a transaction on that network can cost gas, and an RPC provider may impose usage limits or offer paid access. Those costs depend on the transaction and provider, not on a balance query alone.
Is connecting my wallet safe?
Connecting for a network change does not itself authorize a transfer, but the wallet prompt still matters: adding a network, signing a message, and approving a transaction are different actions. A Chainlist network search can help you find candidate RPC settings; it cannot guarantee that every later balance response is accurate. When using Chainlist to select an endpoint, review the network details in the wallet prompt and reject any unexpected request to sign or send a transaction.