Encyclopedia Ethereum · Entry 24
Ethereum nodes and RPC: how wallets see the chain
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Client roles | Execution clients process execution; consensus clients follow proof-of-stake consensus | [1] |
| Staking distinction | Running a verifying node does not itself require activating a validator | [1][3] |
| Query scope | RPC state queries can specify a block, rather than an unspecified latest state | [2] |
Execution and consensus answer different questions
The execution client checks transactions, executes EVM operations and maintains execution state such as account balances and contract storage. The consensus client follows proof-of-stake blocks, votes and the rules that determine the chain head and finality.
Together they let a node verify the chain it follows. Validator software adds proposal and voting duties using an activated validator’s keys. Simply reading and verifying Ethereum does not require depositing the stake needed to activate a validator.
RPC is a request-and-response interface
JSON-RPC defines methods a wallet or application can call. For example, eth_chainId identifies the network, eth_getBalance reads an account’s ETH balance, eth_call executes a read or simulation against selected state, and eth_sendRawTransaction submits a signed transaction.
A hosted endpoint is a service operated by someone else. The wallet can hold signing keys separately while requesting data from that service. Using RPC is therefore not the same thing as giving the endpoint custody of a private key, although the endpoint influences the data the application receives.
Example: asking the same balance question twice
Suppose an application asks for an account’s balance at block 1,000 and gets 2 ETH. A later transaction changes the balance. A request for latest can now produce a different answer because it refers to a different state; this does not mean the earlier response was necessarily wrong.
For reproducible comparisons, record the network and block context and use an appropriate block identifier. Recent blocks can reorganize, so finality also matters. A block number without its network, and sometimes without a block hash, is an incomplete description of the evidence.
Verification, data access and privacy are separate concerns
A self-operated node gives you direct control over verification and the RPC service you use. That does not mean every node retains every historical state. Pruning, synchronization choices and archive capabilities affect which old queries it can answer.
A remote provider receives the queries you send, including requested addresses and network access information available to that service. Endpoint errors, limits or stale responses can affect an application without changing the underlying blockchain. Treat the RPC response and the consensus evidence behind it as related but distinct things.
Direct answers
Questions people ask
Must I stake 32 ETH to run a node?
No. A node can verify and serve chain data without an activated validator. Validator activation is a separate consensus role with its own stake requirements.
Is RPC a blockchain?
No. It is an interface for requesting information or submitting operations to software connected to a blockchain.
Can every full node answer any historical balance query?
No. Data retention and archive capabilities vary. Verifying the current chain and retaining every historical state are different requirements.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An Ethereum node runs software that follows and verifies the network. Execution and consensus clients work together; a validator is an additional role. Wallets often query a node through RPC to read balances, simulate calls and submit signed transactions, so the endpoint affects their view of the chain.
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimClient roles: Execution clients process execution; consensus clients follow proof-of-stake consensus
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimStaking distinction: Running a verifying node does not itself require activating a validator
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimQuery scope: RPC state queries can specify a block, rather than an unspecified latest state
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Nodes and clientsethereum.org contributors
Supports execution/consensus client roles, independent validation, RPC services and node-versus-validator distinctions.
Locator: What are nodes and clients; benefits to you; alternatives · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.541421+00:00Open source - JSON-RPC APIethereum.org contributors
Defines chain identity, balance/nonces, read-only simulation and receipt/status/log fields.
Locator: eth_chainId; eth_getBalance; eth_getTransactionCount; eth_call; eth_getTransactionReceipt · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.605538+00:00Open source - Solo stakingethereum.org contributors
Supports running execution/consensus/validator software and the operational nature of staking.
Locator: How it works; responsibilities; considerations · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.704988+00:00Open source - Proof of stakeethereum.org contributors
Supports 12-second slots, 32-slot epochs, stake-weighted checkpoint voting and block verification.
Locator: Validators; transaction execution; finality; fork choice · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.818781+00:00Open source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Ethereum nodes and RPC: how wallets see the chain.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-nodes-rpc/