{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "pruned-bitcoin-nodes",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/pruned-bitcoin-nodes/",
  "collection": "bitcoin",
  "title": "Pruned Bitcoin nodes: full validation with less historical storage",
  "description": "Understand how Bitcoin pruning reduces retained block storage while preserving validation, and which historical queries it makes unavailable locally.",
  "aliases": [],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T18:15:23.891Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "pruned-bitcoin-nodes-quick-answer",
    "sourceIds": [
      "core-pruning-release",
      "core-pruning"
    ]
  },
  "keyFacts": [
    {
      "label": "Validation",
      "value": "Pruning removes data after validation rather than skipping the initial validation process.",
      "sourceIds": [
        "core-pruning-release"
      ],
      "id": "validation",
      "claimId": "pruned-bitcoin-nodes-fact-validation"
    },
    {
      "label": "State",
      "value": "The chainstate retains information needed to validate current spends.",
      "sourceIds": [
        "core-pruning"
      ],
      "id": "state",
      "claimId": "pruned-bitcoin-nodes-fact-state"
    },
    {
      "label": "History",
      "value": "Deleted block bodies cannot be served from the node’s local retained files.",
      "sourceIds": [
        "core-pruning-release"
      ],
      "id": "history",
      "claimId": "pruned-bitcoin-nodes-fact-history"
    }
  ],
  "prerequisites": [
    "bitcoin-nodes-explained"
  ],
  "sections": [
    {
      "id": "storage",
      "heading": "Separate current state from historical block files",
      "sourceIds": [
        "core-pruning"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "rescan",
      "heading": "Understand the cost of importing an old wallet",
      "sourceIds": [
        "core-pruning-release",
        "core-importdescriptors"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "version",
      "heading": "Do not turn historical introduction limits into current claims",
      "sourceIds": [
        "core-pruning-release",
        "core-pruning"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does pruning make the node trust other people’s transaction validation?",
      "answer": "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.",
      "sourceIds": [
        "core-pruning-release"
      ]
    }
  ],
  "claims": [
    {
      "id": "pruned-bitcoin-nodes-quick-answer",
      "articleSlug": "pruned-bitcoin-nodes",
      "statement": "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.",
      "sourceIds": [
        "source-997df60df1815097",
        "source-49ac1d73e9642790"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-997df60df1815097",
          "locator": "Block file pruning"
        },
        {
          "sourceId": "source-49ac1d73e9642790",
          "locator": "blocks; chainstate"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read Core 0.11.0 Block file pruning and v29.0 blocks/chainstate layout. Validation precedes pruning; current UTXO state is distinct from historical raw/undo files.",
          "The article explicitly dates the historical release and avoids importing its old wallet incompatibility as a current restriction. Missing historical scans need data acquisition, not merely a descriptor."
        ]
      }
    },
    {
      "id": "pruned-bitcoin-nodes-fact-validation",
      "articleSlug": "pruned-bitcoin-nodes",
      "statement": "Validation: Pruning removes data after validation rather than skipping the initial validation process.",
      "sourceIds": [
        "source-997df60df1815097"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-997df60df1815097",
          "locator": "Block file pruning"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read Core 0.11.0 Block file pruning and v29.0 blocks/chainstate layout. Validation precedes pruning; current UTXO state is distinct from historical raw/undo files.",
          "The article explicitly dates the historical release and avoids importing its old wallet incompatibility as a current restriction. Missing historical scans need data acquisition, not merely a descriptor."
        ]
      }
    },
    {
      "id": "pruned-bitcoin-nodes-fact-state",
      "articleSlug": "pruned-bitcoin-nodes",
      "statement": "State: The chainstate retains information needed to validate current spends.",
      "sourceIds": [
        "source-49ac1d73e9642790"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-49ac1d73e9642790",
          "locator": "blocks; chainstate"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read Core 0.11.0 Block file pruning and v29.0 blocks/chainstate layout. Validation precedes pruning; current UTXO state is distinct from historical raw/undo files.",
          "The article explicitly dates the historical release and avoids importing its old wallet incompatibility as a current restriction. Missing historical scans need data acquisition, not merely a descriptor."
        ]
      }
    },
    {
      "id": "pruned-bitcoin-nodes-fact-history",
      "articleSlug": "pruned-bitcoin-nodes",
      "statement": "History: Deleted block bodies cannot be served from the node’s local retained files.",
      "sourceIds": [
        "source-997df60df1815097"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-997df60df1815097",
          "locator": "Block file pruning"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read Core 0.11.0 Block file pruning and v29.0 blocks/chainstate layout. Validation precedes pruning; current UTXO state is distinct from historical raw/undo files.",
          "The article explicitly dates the historical release and avoids importing its old wallet incompatibility as a current restriction. Missing historical scans need data acquisition, not merely a descriptor."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "core-pruning-release",
      "label": "Bitcoin Core 0.11.0 release notes",
      "publisher": "Bitcoin Core",
      "url": "https://bitcoincore.org/en/releases/0.11.0/",
      "locator": "Block file pruning",
      "note": "Pruning removes old block files after validation while retaining chainstate.",
      "version": "Bitcoin Core 0.11.0 historical introduction",
      "checkedAt": "2026-10-02T17:03:41.974Z",
      "contentSha256": "bfba2b0e8a351ef0032fb0f2e8f6892c31214792ef249376feefa524943fd9f1",
      "recordId": "source-997df60df1815097"
    },
    {
      "id": "core-pruning",
      "label": "Bitcoin Core pruning design",
      "publisher": "Bitcoin Core",
      "url": "https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md",
      "locator": "blocks; chainstate",
      "note": "On-disk block files and the chainstate used by a validating node.",
      "version": "Bitcoin Core v29.0",
      "checkedAt": "2026-10-02T17:03:41.146Z",
      "contentSha256": "b22521efd202f947f5a126bb1f8bf24b1f03e48c3cc7928d3d5d11c53e2657b4",
      "recordId": "source-49ac1d73e9642790"
    },
    {
      "id": "core-importdescriptors",
      "label": "importdescriptors RPC",
      "publisher": "Bitcoin Core",
      "url": "https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/importdescriptors/",
      "locator": "Arguments and result fields",
      "note": "Descriptor import, active ranges, timestamps and watch-only use.",
      "version": "Bitcoin Core 29.0.0 RPC",
      "checkedAt": "2026-10-02T17:03:40.832Z",
      "contentSha256": "f11c0815a39b91d5c8fb7e080f7f7b07777fd71615771dfa490a44bc86590140",
      "recordId": "source-0b4367ccf61f3090"
    }
  ],
  "related": {
    "articles": [
      "simplified-payment-verification",
      "watch-only-wallets",
      "bitcoin-output-descriptors"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "Initial Bitcoin encyclopedia entry at this permanent URL."
    },
    {
      "date": "2026-10-02",
      "kind": "publishing-format",
      "summary": "Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification."
    }
  ],
  "citation": "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/"
}