Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£865.25
EST. MONTHLY
204
DAYS
EST. ROI
This guide explains Bitcoin Core pruneblockchain RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.16.0 pruneblockchain manually deleted eligible local block files up to a requested boundary and returned the height of the last block pruned. The argument could be a block height or a Unix timestamp; timestamp mode selected blocks whose block time was at least two hours older.
- Why it matters: pruneblockchain is a deliberate storage deletion boundary. Safe operation depends on exact target resolution, service-role separation, post-prune verification and a proven way to reacquire historical data.
- Current position: Bitcoin Core 0.16.0 pruneblockchain manually deleted eligible local block files up to a requested boundary and returned the height of the last block pruned.
Bitcoin Core pruneblockchain RPC in simple English
Bitcoin Core pruneblockchain RPC: A numeric height requests pruning up to an eligible block height. Validate against the current chain and safety constraints.
Simple example
A miner is checking Bitcoin Core pruneblockchain RPC. Archive-dependent services must be migrated before deletion, not discovered afterwards. After pruning, verify pruneheight, disk use, tip, chainwork, peers and dependent service tests.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Pruning prerequisite
Confirm the node is configured and operating as a pruned role, fully understands the active tip and has healthy disk and database state. Archive-dependent services must be migrated before deletion, not discovered afterwards.
Height boundary
A numeric height requests pruning up to an eligible block height. Validate against the current chain and safety constraints. Record requested and returned heights because internal retention rules may keep more recent data.
Timestamp mode
A Unix timestamp requests pruning blocks whose header time is at least two hours older than that timestamp. Block timestamps are not exact wall clocks. Convert timezone and units explicitly and resolve the resulting height before approval.
Destructive local effect
Deleted block bodies cannot be restored by an inverse RPC. Recovery requires downloading or copying data from a trusted source, potentially rebuilding indexes or rescanning. Treat the call as irreversible local deletion with a tested recovery plan.
Service compatibility
Historical getblock, transaction lookup, Merkle proofs, wallet rescans and serving old blocks can fail below the retained boundary. Maintain an archive node where those functions matter and route requests by declared capability.
Monitoring and evidence
After pruning, verify pruneheight, disk use, tip, chainwork, peers and dependent service tests. Keep the returned last-pruned height and configuration snapshot. Do not claim saved bytes until filesystem measurements stabilise.
Recovery drill
On a disposable synced copy, prune by height and timestamp, test every historical consumer, restart and simulate a later rescan request. Restore from trusted block data and measure downtime before approving production use. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of Bitcoin Core pruneblockchain RPC?
Bitcoin Core pruneblockchain RPC: A numeric height requests pruning up to an eligible block height.
For Bitcoin Core pruneblockchain RPC, what should a beginner know about pruning prerequisite?
Confirm the node is configured and operating as a pruned role, fully understands the active tip and has healthy disk and database state.
For Bitcoin Core pruneblockchain RPC, what should a beginner know about height boundary?
A numeric height requests pruning up to an eligible block height. Validate against the current chain and safety constraints.
For Bitcoin Core pruneblockchain RPC, what should a beginner know about timestamp mode?
A Unix timestamp requests pruning blocks whose header time is at least two hours older than that timestamp.
Conclusion
pruneblockchain is a deliberate storage deletion boundary. Safe operation depends on exact target resolution, service-role separation, post-prune verification and a proven way to reacquire historical data.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.