RPC (Remote Procedure Call)
The HTTP/WebSocket interface through which wallets and applications query blockchain state and submit transactions.
Every interaction with a blockchain happens through an RPC endpoint. When MetaMask shows your balance, it's asking an RPC node "what is balanceOf(your_address)?". When you submit a swap, it goes to an RPC node which broadcasts it to the network.
Most users use shared RPC providers (Infura, Alchemy, QuickNode) because running a node is expensive. This creates centralization — a few providers handle the majority of Ethereum traffic. Personal RPC nodes are recommended for privacy-conscious users and high-volume traders.
RPC infrastructure is invisible but critical. Outages or rate-limits at major RPC providers can effectively halt parts of crypto.
How CryptoRadar24 tracks it
CryptoRadar24 doesn't directly track RPC infrastructure but references it when major outages affect user activity.
Related terms
FAQ
Why does my wallet need an RPC?
It needs a way to read blockchain state (your balance) and broadcast transactions. An RPC endpoint is that bridge. Without one, the wallet can't function.
Are public RPCs safe?
For reading, mostly yes. For sending transactions, public RPCs can see your transaction in the mempool and front-run it. Private RPCs (Flashbots Protect, MEVBlocker) prevent that.
What does "RPC error" mean?
The endpoint failed to respond — overloaded, rate-limited, or down. Switching RPC URLs in wallet settings usually fixes it.
How do I run my own RPC?
Run a full Ethereum node (Geth + consensus client) on a machine with ~2TB SSD. Takes a day to sync. Or run a light node for read-only access (still substantial).