Pruning deletes the whole old blocks.
Here https://bitcoincore.org/en/releases/0.11.0/
Block pruning allows Bitcoin Core to delete the raw block and undo data once it’s been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or for rescanning the wallet. The block index continues to hold the metadata about all blocks in the blockchain.
The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the block index and UTXO databases. The minimum was chosen so that Bitcoin Core will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 blocks on disk.
Block pruning works during initial sync in the same way as during steady state, by deleting block files “as you go” whenever disk space is allocated. Thus, if the user specifies 550MB, once that level is reached the program will begin deleting the oldest block and undo files, while continuing to download the blockchain.
BitcoinIsFuture
npub1wl…5caw8
2026-05-29 16:41:12 UTC
in reply to nevent1q…trv8
Author Public Key
npub1wl6kysagynfz2ulmw4wa2trnc9ycd52upjv9zt297n0tpr5ls7dqk5caw8Published at
2026-05-29 16:41:12 UTCEvent JSON
{
"id": "c60904a0f07959ce8c12ba7cfad8b5895861bca11864f0cdde9922128c372a30",
"pubkey": "77f56243a824d22573fb755dd52c73c14986d15c0c98512d45f4deb08e9f879a",
"created_at": 1780072872,
"kind": 1,
"tags": [
[
"p",
"55f573b651eff351db57b0601d23022d8c532f9825db10a5733ebf39be4aa21b"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
],
[
"e",
"8ed77b1a9c2b3943e1d8ef786a0fc116aa689f36370516fb0bb04bec6e154808",
"wss://nostr.wine/",
"root",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
],
[
"e",
"07852239b71f1ca0f81c6e20d74ff9b5129717928da29224ed2322d9b0fa0b15",
"wss://theforest.nostr1.com/",
"reply",
"55f573b651eff351db57b0601d23022d8c532f9825db10a5733ebf39be4aa21b"
]
],
"content": "Pruning deletes the whole old blocks.\n\nHere https://bitcoincore.org/en/releases/0.11.0/\n\nBlock pruning allows Bitcoin Core to delete the raw block and undo data once it’s been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or for rescanning the wallet. The block index continues to hold the metadata about all blocks in the blockchain.\n\nThe user specifies how much space to allot for block \u0026 undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the block index and UTXO databases. The minimum was chosen so that Bitcoin Core will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 blocks on disk.\n\nBlock pruning works during initial sync in the same way as during steady state, by deleting block files “as you go” whenever disk space is allocated. Thus, if the user specifies 550MB, once that level is reached the program will begin deleting the oldest block and undo files, while continuing to download the blockchain.",
"sig": "4fd384bb6760cd0a6e39c87338905ee08d5be9e0e964c7524566aafdb8faac11b0b0268f1c5881820f917a20aba1e6052de2495d8e4753c5b4071f9ed0f4f020"
}