# Ethereum archive nodes: asking what an account held in the past 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. Evidence: [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-archive-nodes/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Historical state:** Archive operation supports queries about past account and storage state. ([Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive)) - **Retention:** Configured history limits determine which old states remain available. ([Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive)) - **Proofs:** Historical proof support may require retained trie-node history. ([Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive)) ## 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. Evidence: [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive); [Ethereum JSON-RPC API](https://ethereum.org/en/developers/docs/apis/json-rpc/) ## 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. Evidence: [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive) ## 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. Evidence: [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive) ## Questions ### 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. Evidence: [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/); [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive) ### 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. Evidence: [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive) ## Claims and scope ### ethereum-archive-nodes-quick-answer 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: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-archive-nodes-fact-historical-state Historical state: Archive operation supports queries about past account and storage state. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-archive-nodes-fact-retention Retention: Configured history limits determine which old states remain available. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-archive-nodes-fact-proofs Proofs: Historical proof support may require retained trie-node history. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Geth archive node](https://geth.ethereum.org/docs/fundamentals/archive) — Go Ethereum. Historical state availability depends on client version and archive retention/index configuration. Locator: Hash-based archive; path-based archive. Retrieved: 2026-10-02T18:55:26.554Z. - [Ethereum JSON-RPC API](https://ethereum.org/en/developers/docs/apis/json-rpc/) — ethereum.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. Retrieved: 2026-10-02T18:55:24.990Z. - [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/) — ethereum.org contributors. Post-Merge client roles, optional validators and synchronization modes. Locator: Execution and consensus clients; synchronization; node types. Retrieved: 2026-10-02T18:55:26.405Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees 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/