Skip to main content

​
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.

​
Definition

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.

​
Simple explanation

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.
Canonical knowledge ID: glossary:rpc