Encyclopedia Ethereum · Entry 271
Ethereum archive nodes: asking what an account held in the past
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Historical state | Archive operation supports queries about past account and storage state. | [1] |
| Retention | Configured history limits determine which old states remain available. | [1] |
| Proofs | Historical proof support may require retained trie-node history. | [1] |
Specify which historical answer you need
A block’s transactions describe activity, but an efficient query for an arbitrary old account balance needs the relevant state or a way to reconstruct it. A service can retain transaction history without offering every historical state query.
State values and cryptographic proofs are also different outputs. Ask whether the endpoint supports the specific method at the target block.
An old balance and an old proof can have different support
The retrieved Geth documentation distinguishes path-based archive behavior across versions: v1.16.x does not support historical eth_getProof in that mode, while v1.17.x can support it with the required historical trie retention. This is a versioned example, not a blanket claim about every node.
A successful historical balance lookup therefore does not prove that the same endpoint can supply the corresponding historical Merkle proof.
Retention and completed indexes matter
Geth documents configurable historical state retention and indexing. Pruned history cannot be recovered merely by changing a retention flag after the fact. A complete archive may require obtaining the missing history through an appropriate rebuild or other supported process.
Confirm the retained range and indexing completion before relying on an audit query. Disk-size and synchronization-time estimates change with chain growth and hardware, so this article does not promise a fixed resource budget.
Direct answers
Questions people ask
Is every full Ethereum node an archive node?
No. Full validation and retention of arbitrary historical state are different capabilities. A node can validate current blocks while pruning old state.
Does the word archive guarantee all historical RPC methods?
No. Verify the client version, retained data, index completion and specific method. Historical values and historical proofs can have different requirements.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An archive node retains historical state so it can answer questions such as an account balance or contract storage value at an old block. Keeping block history alone is not the same capability. In Geth, historical flat-state queries and historical Merkle proofs have distinct retention and indexing requirements, so check the client version and requested RPC method.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimHistorical state: Archive operation supports queries about past account and storage state.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRetention: Configured history limits determine which old states remain available.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimProofs: Historical proof support may require retained trie-node history.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Geth archive nodeGo Ethereum
Historical state availability depends on client version and archive retention/index configuration.
Locator: Hash-based archive; path-based archive · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.554ZOpen source - Ethereum JSON-RPC APIethereum.org contributors
RPC requests explicitly identify addresses and block scope; receipts and removed log fields support verification examples.
Locator: eth_getBalance; eth_getTransactionReceipt; block parameter; logs · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:24.990ZOpen source - Ethereum nodes and clientsethereum.org contributors
Post-Merge client roles, optional validators and synchronization modes.
Locator: Execution and consensus clients; synchronization; node types · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.405ZOpen 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 archive nodes: asking what an account held in the past.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-archive-nodes/