Your wallet doesn't store the blockchain
A blockchain is hundreds of gigabytes of history replicated across thousands of machines. Your wallet, obviously, holds none of that. What it holds is your keys — and a list of phone numbers for computers that do hold the chain. Every balance you see and every transaction you send passes through one of those computers. They are called RPC nodes, and they are the least-discussed dependency in your entire crypto setup.
What an RPC node actually is
RPC stands for remote procedure call — a plain request-response protocol. An RPC node is a machine running full blockchain node software that exposes an API endpoint (a URL) where clients can ask questions and submit transactions. On EVM chains the interface is standardized as JSON-RPC, with methods for reading balances, querying contracts, estimating gas and broadcasting signed transactions. When people configure a "network" in a wallet, the RPC URL is the part that matters: it decides which machine answers on behalf of the chain.
What happens when you check a balance or hit send
Opening your wallet fires a volley of RPC reads: the native coin balance for your address, token balances via contract queries, current fee levels. Sending is the more instructive flow: the wallet builds the transaction, signs it locally with your key, and only then hands the signed bytes to the RPC node to broadcast into the network. The division of labor is absolute — the node never sees your private key and cannot alter what you signed; it is a courier, not a co-signer. That is the technical heart of self-custody: signing happens on your device, and everything past the signature is public information anyway.
Public vs private endpoints — and what they see
Chains ship with public RPC endpoints, and infrastructure providers run faster, more reliable ones; wallets typically default to a curated mix. The differences that matter are reliability (public endpoints rate-limit and lag under load) and privacy: whichever endpoint you use can observe your IP address together with every address you query — a linkage worth understanding, since your on-chain addresses are otherwise pseudonymous. A malicious or compromised endpoint still cannot steal funds, but it can serve stale data, censor your broadcasts, or log your metadata. Choosing RPC infrastructure is thus a trust decision, just a much smaller one than choosing who holds keys.
One wallet, many dialects
The neat JSON-RPC story is an EVM story. Solana speaks its own RPC vocabulary (accounts, slots, compute units), and TON's client APIs are different again. A wallet that spans ecosystems — see what a multi-chain wallet is — must maintain healthy connections to every network it supports, in each network's dialect, with failover when an endpoint degrades. That invisible fleet management is a real part of what separates a smooth multi-chain wallet from a frustrating one.
When RPC breaks: wrong balances and stuck sends
Most "where did my crypto go?" panics are RPC weather. A lagging endpoint shows a stale balance; an overloaded one times out mid-broadcast; a dropped connection makes a healthy wallet look empty. The reassuring physics: your funds live on the chain, controlled by your keys — never inside the endpoint. Switching RPC (or letting the wallet fail over) fixes the view without touching the money. If a dApp connection is the thing misbehaving instead, that is a different layer — covered in connecting your wallet to a dApp safely.
How WATS fits in
WATS sits on the user's side of everything this article described. It maintains the connections to EVM, Solana and TON for you — no hand-editing endpoint URLs per chain — while signing stays strictly local: WATS is non-custodial, you hold your keys, and WATS never holds one. And where classic wallets still make you keep a gas coin per network before an RPC broadcast will succeed, WATS charges every action — transfers, swaps, staking — in one token, ATS, instead of the chain's native gas: via an ERC-4337 paymaster on EVM and an equivalent fee-payer/relayer on Solana and TON. ATS is a LayerZero OFT, so a single balance works across all three ecosystems, and collected ATS is burned from a 100M supply toward a 30M floor. WATS is the first and only wallet to combine ERC-4337 and OFT single-token fees with that burn — the full model is on the ATS fee page.
Frequently asked questions
Does an RPC node hold my crypto?
No. An RPC node is a read-and-relay service: it answers queries about the chain and broadcasts transactions you have already signed. Your funds are controlled by your private keys, which never leave your device in a self-custody wallet. If an RPC endpoint goes down or misbehaves, your assets are untouched — only your view of the chain is affected.
Can a malicious RPC endpoint steal my funds?
It cannot spend your funds, because it never has your keys and cannot modify a signed transaction without invalidating it. What a bad endpoint can do is lie about balances, delay or censor your broadcasts, and log your IP address alongside the addresses you query — a privacy leak rather than a theft risk. Using reputable, redundant endpoints (or a wallet that manages failover for you) addresses both.
Why does my wallet show a wrong or zero balance sometimes?
Almost always because the RPC endpoint it queried is lagging, rate-limited or briefly offline — the blockchain itself still records your balance correctly. Refreshing after a moment, switching endpoints, or letting the wallet fail over to another node restores the correct view. It is a display-layer problem, not a funds problem.