You have fallen for the compromised Core propaganda about "prunable wallets".
Like all their propaganda, its manipulation and let me tell you why. I asked AI for you actually.
Can a prunable Bitcoin node, that verifies transactions 200 days back, recreate and old Bitcoin wallet backup that was done 600 days ago?
Short answer: No — not reliably.
Why:
A prunable Bitcoin node deletes old block data beyond its pruning threshold, so if it only retains the last 200 days of blocks it cannot reconstruct UTXO state or transaction history older than those retained blocks.
A wallet backup from 600 days ago may contain private keys/seed. If it contains a full seed/private keys, you can restore the wallet (private keys → addresses) on any node or wallet software, but to verify balances and historical transactions you need blockchain data covering the 600‑day-old transactions.
A pruned node that only has the last 200 days cannot validate or rescan the chain back to 600 days unless it can fetch missing blocks from peers. Bitcoin Core in pruned mode will refuse to download and keep full historical blocks to rebuild state; it can request missing blocks temporarily only if configured to do so and only if peers provide them, but by design pruning removes the ability to maintain full archival history locally.
Practical outcomes:
If your goal is only to recover private keys and spend funds: restoring the seed/private keys from the 600‑day backup will let you generate addresses and sign transactions; to find current UTXO set and balances the wallet can query a full node or a trusted third‑party (e.g., Electrum server, block explorer) or the node must temporarily obtain and process older blocks (which a pruned node normally won’t keep long-term).
If your goal is to fully rescan and cryptographically verify all historical transactions from that backup locally: you need access to blocks going back 600 days (a full archival node or a node that can download and retain that range). A strictly pruned node keeping only 200 days cannot do this alone.
BitcoinIsFuture
npub1wl…5caw8
2026-05-29 16:26:55 UTC
in reply to nevent1q…a0lq
Author Public Key
npub1wl6kysagynfz2ulmw4wa2trnc9ycd52upjv9zt297n0tpr5ls7dqk5caw8Published at
2026-05-29 16:26:55 UTCEvent JSON
{
"id": "c6d3432ad7f5d7c938f38dac7c2866b0c7a2258433ecbfee3591cad1ebb44273",
"pubkey": "77f56243a824d22573fb755dd52c73c14986d15c0c98512d45f4deb08e9f879a",
"created_at": 1780072015,
"kind": 1,
"tags": [
[
"p",
"55f573b651eff351db57b0601d23022d8c532f9825db10a5733ebf39be4aa21b"
],
[
"p",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"e",
"8ed77b1a9c2b3943e1d8ef786a0fc116aa689f36370516fb0bb04bec6e154808",
"wss://nostr.wine/",
"root",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
],
[
"e",
"465fef122bcd74a156b1175d20072c9395ee3f29b294e939d6b1f98de6d0cf1f",
"wss://relay.snort.social/",
"reply",
"55f573b651eff351db57b0601d23022d8c532f9825db10a5733ebf39be4aa21b"
]
],
"content": "You have fallen for the compromised Core propaganda about \"prunable wallets\".\nLike all their propaganda, its manipulation and let me tell you why. I asked AI for you actually.\n\nCan a prunable Bitcoin node, that verifies transactions 200 days back, recreate and old Bitcoin wallet backup that was done 600 days ago?\n\nShort answer: No — not reliably.\n\nWhy:\n\n A prunable Bitcoin node deletes old block data beyond its pruning threshold, so if it only retains the last 200 days of blocks it cannot reconstruct UTXO state or transaction history older than those retained blocks.\n A wallet backup from 600 days ago may contain private keys/seed. If it contains a full seed/private keys, you can restore the wallet (private keys → addresses) on any node or wallet software, but to verify balances and historical transactions you need blockchain data covering the 600‑day-old transactions.\n A pruned node that only has the last 200 days cannot validate or rescan the chain back to 600 days unless it can fetch missing blocks from peers. Bitcoin Core in pruned mode will refuse to download and keep full historical blocks to rebuild state; it can request missing blocks temporarily only if configured to do so and only if peers provide them, but by design pruning removes the ability to maintain full archival history locally.\n\nPractical outcomes:\n\n If your goal is only to recover private keys and spend funds: restoring the seed/private keys from the 600‑day backup will let you generate addresses and sign transactions; to find current UTXO set and balances the wallet can query a full node or a trusted third‑party (e.g., Electrum server, block explorer) or the node must temporarily obtain and process older blocks (which a pruned node normally won’t keep long-term).\n If your goal is to fully rescan and cryptographically verify all historical transactions from that backup locally: you need access to blocks going back 600 days (a full archival node or a node that can download and retain that range). A strictly pruned node keeping only 200 days cannot do this alone.\n",
"sig": "cdb078d000ae787d42086b066bbc79f33e3510768d641218aece490d0b2025c7920c2cc84295ac8b70d837ee315e1cc3c7532bd1227c95ef05ca0c2c8fbadd3c"
}