What Is an RPC Endpoint, and How Do You Switch It in Your Wallet?

The first time a wallet suddenly shows nothing at all, many beginners assume their assets are gone or the wallet is broken. In a surprising number of cases, neither is true. The problem is the "communication line" between the wallet and the blockchain — and that line is called an RPC endpoint.

An RPC (Remote Procedure Call) endpoint is, in plain terms, the gateway server your wallet uses to reach a blockchain. Your wallet does not store the whole chain itself. Every time it shows a balance, broadcasts a transaction, or interacts with a DApp, it asks and sends through an RPC URL. The blockchain may be perfectly healthy, but if that gateway server is overloaded, down, or slow, all you see is spinning loaders and blank screens.

Put another way: your assets are recorded on-chain, and the RPC is just a window you look through. A dirty or closed window does not mean the room behind it is empty. Once you understand this, many scary-looking symptoms become calm, checkable problems.

RPC is the gateway between your wallet and the chain

Ethereum and other EVM chains are networks made up of many nodes. Ordinary users do not run a full node themselves, so wallets connect to a public RPC service by default — for example, MetaMask reaches Ethereum mainnet through nodes operated by Infura.

When you open your wallet, it queries your balance through RPC. When you confirm a transfer, the signed transaction is broadcast through RPC. When a DApp reads contract data, that also goes through RPC. Apart from signing, which happens locally on your device, almost every visible action depends on the endpoint.

A single chain usually has many public RPC endpoints run by different providers. That is exactly why "switching RPC" fixes things: if one line is congested, you take another line, and the on-chain data is still the same data.

Common symptoms of an RPC failure

When an RPC endpoint has problems, your wallet rarely says "the RPC is down." Instead you see symptoms that are easy to misread:

• Balances show as 0 or load forever. The assets are still on-chain; the wallet just cannot fetch the data.
• Transactions stay stuck at Pending, or you hit send and nothing appears on the block explorer.
• DApps report network errors, fail to connect to your wallet, or time out while reading data.
• Token lists flicker — fine after one refresh, blank after the next.

The first step is not to panic but to cross-check: paste your address into a block explorer such as Etherscan. If the explorer shows your balance correctly, it is almost certainly a display or RPC issue on the wallet side, not an asset issue. This is the same troubleshooting mindset as the classic "my wallet has the tokens but the DApp can't see them" problem.

How to switch or add an RPC in MetaMask

In MetaMask, the rough path is: open the network selector, find the current network, open its edit or details view, and you will see the RPC URL field. Newer versions of MetaMask let you save multiple RPC URLs for the same network and switch between them.

When adding a new RPC, you typically fill in:

1. Network name: a label for yourself; the text does not affect functionality.
2. RPC URL: the endpoint address — the field that matters most.
3. Chain ID: the chain's unique number, for example 1 for Ethereum mainnet and 8453 for Base. The wallet will reject a wrong value.
4. Currency symbol: such as ETH.
5. Block explorer URL: optional, but handy for jumping from the wallet to the explorer.

If you prefer not to type these by hand, tools like Chainlist (chainlist.org) let you search for a chain, connect your wallet, and add a community-listed RPC configuration in one click. Note that Chainlist itself should also be reached through the correct domain.

After switching, refresh the wallet home screen. If balances come back and transactions broadcast normally, the old endpoint was indeed the problem.

Only take RPC addresses from trusted sources

An RPC URL is not just any string that happens to work — it decides whose version of the chain your wallet listens to. Only accept RPC addresses from:

• The chain's official documentation, such as the Ethereum website or the official docs of Base and other L2s.
• Long-standing, widely used aggregators such as Chainlist.
• Configuration guides from your wallet's official help center.

Sources to avoid: "faster nodes" sent by strangers in group chats or DMs, setup tutorials in search-engine ad slots, and screenshots of unknown origin. These are the most common ways malicious RPCs spread.

The risks of a malicious RPC

Because the RPC is your wallet's only window onto the chain, an attacker-controlled endpoint can lie to you:

• Fake balances. A common scam has you connect to a malicious RPC and "see" extra money in an account, then pushes you to pay fees or deposit real assets to withdraw funds that never existed.
• Misleading transaction context. A malicious node can return tampered contract data or transaction status, so that a phishing page gets you to sign under false information.
• Logging your address and query patterns for targeted phishing later.

To be clear: an RPC cannot take your private key or seed phrase — signing always happens locally on your device. The danger of a malicious RPC is that it shows you a fake world and lets you make the wrong decision yourself. Refuse any request to add a network configuration you cannot verify.

Checklist

When your wallet acts up or you are about to change RPCs, run through this list:

• Verify the real state of your assets and transactions on a block explorer first, separating "display problems" from "asset problems."
• Check whether the issue affects only one chain while other networks work fine.
• Get backup RPC addresses from official docs or Chainlist — never from group chats or DMs.
• When adding a network, confirm the Chain ID matches the official value.
• After switching, confirm balances and transaction broadcasting are back to normal.
• Treat any claim that you must "add a special network to claim assets" as high risk.
• Periodically review the custom networks saved in your wallet and delete configurations whose origin you can no longer remember.

FAQ

Does switching RPCs affect my assets? No. Assets are recorded on the blockchain, regardless of which RPC you use. Switching only changes the line you query and broadcast through, and your private key and seed phrase are never sent to the node.

Can an RPC provider see my private key? No. Signing happens locally on your device; the RPC only receives signed transactions and read requests. It can, however, see your address, IP, and query behavior — privacy-focused node services exist if that concerns you.

What is the difference between free public RPCs and paid ones? Mostly stability and rate limits. Public endpoints can get congested at peak times but are fine for everyday use. Heavy users may sign up with providers like Infura or Alchemy for a dedicated endpoint. Beginners can stick with officially recommended public gateways.

I switched RPCs but my transaction is still pending — now what? Check the transaction hash on a block explorer first. If the transaction never made it on-chain, you may need to resend it. If it shows as pending on-chain, the cause is usually a low gas setting rather than the RPC, and you can speed it up or cancel it.

Related reading

• Why Can't I See My Tokens in a Wallet or DApp?
• What Is a Transaction Hash, and How Do You Check It?
• What Is Base Network, and How Do You Start Safely?

References

• ethereum.org: Nodes and clients - https://ethereum.org/en/developers/docs/nodes-and-clients/
• ethereum.org: JSON-RPC API - https://ethereum.org/en/developers/docs/apis/json-rpc/
• MetaMask Help Center - https://support.metamask.io/
• Chainlist - https://chainlist.org/