RPC
Remote Procedure Call (RPC) is a software communication protocol that allows a program to request a service from a program located in another computer on a network. In blockchain contexts, RPC endpoints allow decentralized applications (dApps) to communicate with a blockchain node. By sending JSON-RPC requests, developers can query balance data, submit transactions, or check the state of the network, acting as the necessary bridge between front-end interfaces and back-end blockchain data.
Explain Like I'm 12
Think of RPC like ordering food at a restaurant. You are the customer (the application), and you send your order to the kitchen (the blockchain). The waiter who takes your order and brings back the food is the RPC, acting as the messenger between you and the kitchen.
Why It Matters
RPC is the vital link that makes dApps usable. Without RPC endpoints, browsers and mobile wallets would be unable to interact with the blockchain in real-time.
How It Works
A client application sends a standardized message (JSON-RPC) to an RPC provider endpoint. The provider processes this request on a node, retrieves the data from the blockchain's database, and returns the result back to the application in a readable format.
Real-World Example
Infura or Alchemy provide RPC endpoints that allow MetaMask to read your wallet balance.
Advantages
- Enables dApp connectivity
- Standardized communication protocol
- Easy access to chain data
Limitations
- Centralization risks
- Potential privacy leaks
- Single point of failure
Common Misconceptions
- It is not a part of the blockchain protocol itself.
- It does not provide direct access to the consensus layer.
Knowledge Explorer
Explore This Concept in the Knowledge Graph
See how RPC connects to other concepts, books, research, and developer resources.
Related Terms
API
A defined set of methods and data formats that software uses to communicate with another application or service.
JSON-RPC
A lightweight remote-procedure-call protocol using JSON messages and widely used by blockchain nodes and wallets.
Node
A node is any computer or device that connects to a blockchain network and participates by running the protocol's software. Nodes play various roles, including validating transactions, maintaining a copy of the blockchain history, and propagating new data to other peers. Different types of nodes exist, such as full nodes (which store the entire blockchain history and enforce all rules) and light nodes (which store only headers for efficiency). Nodes are the active participants that uphold the network's integrity and decentralization.
ASIC
An Application-Specific Integrated Circuit (ASIC) is a specialized hardware device engineered to perform a single computational task with maximum efficiency. In the context of blockchain, ASICs are designed exclusively for the hashing algorithms required to mine proof-of-work cryptocurrencies. Unlike general-purpose CPUs or GPUs, which process various instructions, ASICs are hard-wired for specific mathematical operations, providing orders of magnitude higher hash rates and energy efficiency for dedicated mining operations.
Account
In the context of blockchain architecture, an account is a persistent entity that holds a balance of native tokens, stores state data, and possesses an associated address derived from a public key. Unlike the UTXO model used by Bitcoin, account-based models—most notably used by Ethereum—track the current state of every participant, allowing for complex smart contract interactions. Accounts serve as the fundamental primitive for identity and value representation, enabling protocols to manage user assets and execution environments securely within the ledger.
Address
In blockchain, an address is a unique identifier derived from a public cryptographic key, acting as the destination for transactions. Similar to an IBAN in traditional banking, it allows users to receive digital assets. An address is typically a shortened hexadecimal string, generated by applying a hashing function to a public key. It functions as the public-facing identity of an account, ensuring that funds sent to it are only accessible to the entity possessing the corresponding private key.
Related Articles
Web3 Infrastructure: The Hidden Backbone of Decentralization
Everyone talks about DeFi, NFTs, and DAOs.Few talk about the invisible machinery that makes it all work. Behind every flashy dApp, staking pool, or meme token lies a network of nodes, validators, oracles, and data layers — the unsung heroes of decentralization. Without them, Web3 isn’t possible. In
“Hide the Wires”: Why Web3 Is Getting Invisible
One of the biggest criticisms of Web3 has always been this: it’s too complicated for the average user. Wallets, gas fees, seed phrases, RPC settings — all of these concepts make sense to crypto natives, but they’re intimidating to everyday people. In 2025, a new movement in Web3 design is taking hol
Why Most Web3 Products Fail at the Infrastructure Layer First
When a Web3 product fails, the assumption is usually the same. Bad idea. Weak execution. No demand. But more often than not, that’s not where the problem starts. It starts underneath the product. At the infrastructure layer. The Misdiagnosis of Failure From the outside, failure looks like: ...