# Pruned Bitcoin nodes: full validation with less historical storage A pruned Bitcoin full node validates blocks and maintains the current chainstate, then deletes eligible older block files to reduce disk use. It still checks consensus rules. Pruning limits access to historical block data, so some rescans and historical queries require obtaining that data again. Evidence: [Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/); [Bitcoin Core pruning design](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) Canonical: https://degreesofsatoshi.com/encyclopedia/pruned-bitcoin-nodes/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T18:15:23.891Z 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 - **Validation:** Pruning removes data after validation rather than skipping the initial validation process. ([Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/)) - **State:** The chainstate retains information needed to validate current spends. ([Bitcoin Core pruning design](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md)) - **History:** Deleted block bodies cannot be served from the node’s local retained files. ([Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/)) ## Separate current state from historical block files Bitcoin Core stores block data and chainstate for different purposes. The unspent-output state helps determine whether a new transaction can spend its inputs. Old blocks also support historical queries and reconstruction. Deleting old eligible block files does not erase those transactions from Bitcoin’s history. It changes what this particular node retains locally. Evidence: [Bitcoin Core pruning design](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) ## Understand the cost of importing an old wallet An imported wallet may need to inspect blocks from before the node’s retained window to discover earlier receipts. If those blocks are absent, a complete scan needs another way to acquire the necessary historical data. A correct public descriptor is not enough to make missing historical files reappear. Match backup and recovery procedures to the node’s storage configuration. Evidence: [Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/); [importdescriptors RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/importdescriptors/) ## Do not turn historical introduction limits into current claims The cited 0.11.0 release notes describe the historical introduction of pruning. Some compatibility restrictions in that release are not a timeless description of later Bitcoin Core versions. The accompanying v29.0 file-layout reference describes the retained storage categories. For an installation, use the help and documentation for its actual version to choose supported pruning and wallet options. Evidence: [Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/); [Bitcoin Core pruning design](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) ## Questions ### Does pruning make the node trust other people’s transaction validation? Pruning itself does not. A fully validating node can check blocks and later discard older bodies. Its configuration and synchronization assumptions should be evaluated separately. Evidence: [Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/) ## Claims and scope ### pruned-bitcoin-nodes-quick-answer A pruned Bitcoin full node validates blocks and maintains the current chainstate, then deletes eligible older block files to reduce disk use. It still checks consensus rules. Pruning limits access to historical block data, so some rescans and historical queries require obtaining that data again. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### pruned-bitcoin-nodes-fact-validation Validation: Pruning removes data after validation rather than skipping the initial validation process. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### pruned-bitcoin-nodes-fact-state State: The chainstate retains information needed to validate current spends. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### pruned-bitcoin-nodes-fact-history History: Deleted block bodies cannot be served from the node’s local retained files. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Bitcoin Core 0.11.0 release notes](https://bitcoincore.org/en/releases/0.11.0/) — Bitcoin Core. Pruning removes old block files after validation while retaining chainstate. Locator: Block file pruning. Retrieved: 2026-10-02T17:03:41.974Z. - [Bitcoin Core pruning design](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) — Bitcoin Core. On-disk block files and the chainstate used by a validating node. Locator: blocks; chainstate. Retrieved: 2026-10-02T17:03:41.146Z. - [importdescriptors RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/importdescriptors/) — Bitcoin Core. Descriptor import, active ranges, timestamps and watch-only use. Locator: Arguments and result fields. Retrieved: 2026-10-02T17:03:40.832Z. ## Revision history - 2026-10-02: Initial Bitcoin encyclopedia entry at this permanent URL. - 2026-10-02: Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification. ## Cite this entry Degrees of Satoshi editorial project. “Pruned Bitcoin nodes: full validation with less historical storage.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/pruned-bitcoin-nodes/