The Diet for the Librarian: Understanding pruneblockchain

The Bitcoin blockchain is huge, and it grows every day. For a "Librarian" with a small house (a small hard drive), this is a problem. Pruning is the solution. It allows the node to "Forget" the old, raw block data while still "Remembering" the current balances. The command pruneblockchain is the "Diet for the Librarian," the "Optimization of the Vault."

Analyzing the "Cleanup" Code

In the source code (src/rpc/blockchain.cpp), the node checks if it is "Eligible" for pruning before deleting any files.

/**
 * This function "Prunes" (deletes) the old raw block data.
 */
static RPCMethod pruneblockchain()
{
 // ... (Arguments omitted)
 [](const RPCMethod& self, const JSONRPCRequest& request) -> UniValue
{
 int height = request.params[0].getInt<int>();

 ChainstateManager& chainman = EnsureAnyChainman(request.context);
 if (!chainman.m_blockman.IsPruneMode()) {
 throw JSONRPCError(RPC_MISC_ERROR, "Node is not in prune mode!");
 }

 // We delete the old 'Block Files' up to the height.
 chainman.ActiveChainstate().PruneBlockFilesManual(height);

 return height;
}

Explaining the Diet to a Non-Coder

• IsPruneMode: Pruning is a "Lifestyle Choice." You must decide to enable it when you start the node. Once you delete the old blocks, you can't get them back without downloading them again. It is the "Sacrifice of History for the sake of the Present."

• PruneBlockFilesManual: The node doesn't delete "Address Balances" (the UTXO set). It only deletes the "Raw Blocks" (the transaction history). It's like a library that keeps the "Current Directory" but throws away the "Old Newspapers." It is the "Lean Architecture of the Core."

The Efficiency of Survival

Pruning allows a Bitcoin node to run on a $50 computer with a small SD card. It ensures that Bitcoin remains "Accessible" to everyone, not just those with massive servers. By mastering pruneblockchain, you are learning how to maintain "Financial Sovereignty" on a budget. It is the "Democratization of the Vault."