Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core scanblocks RPC: Compact-Filter Discovery Guide
Bitcoin Core 25 scanblocks guide covering compact-filter index prerequisites, descriptors, ranges, false positives, status, abort, pruning and verified rescans.
This guide explains Bitcoin Core scanblocks 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 25.0 introduced scanblocks to scan compact block filters for scripts derived from descriptors and return block hashes that may be relevant. It requires a completed blockfilterindex.
- Why it matters: scanblocks accelerates discovery by narrowing the block set, but it does not complete wallet recovery. Reliable use preserves descriptor and range evidence, verifies candidates against blocks and reconciles the resulting wallet history.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
What this means in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- 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.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Index prerequisite
The node must construct the compact filter index with blockfilterindex enabled. Confirm index readiness with getindexinfo before starting; a configured option is not evidence of completion.
Actions
start performs a scan and returns only when complete, status reports approximate progress and current height, and abort requests cancellation. An abort true result does not promise instant termination.
Scan objects
Each item is a descriptor string or an object with desc and an optional range. Ranged HD descriptors default to 1000, so choose bounds from recovery evidence rather than habit.
Height range
start_height defaults to zero and stop_height to the chain tip. Pin both for reproducible jobs and preserve the observed tip hash so reorganisations can be reconciled.
False positives
By default relevant_blocks may include compact-filter false positives. Filtering those requires block access, is slower and may fail on pruned nodes; every candidate still needs full verification.
Timeout and concurrency
The call may take minutes, and official examples recommend no RPC client timeout. Use one controlled scan, poll status separately and prevent competing jobs from confusing operators.
Recovery flow
Validate descriptors, scan a bounded range, fetch candidate blocks, rescan wallet history, compare transactions and UTXOs with independent records, then extend the range only when evidence requires it. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is Bitcoin Core scanblocks RPC?
Bitcoin Core 25.0 introduced scanblocks to scan compact block filters for scripts derived from descriptors and return block hashes that may be relevant. It requires a completed blockfilterindex.
Is Bitcoin Core scanblocks RPC active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Bitcoin Core scanblocks RPC matter?
scanblocks accelerates discovery by narrowing the block set, but it does not complete wallet recovery. Reliable use preserves descriptor and range evidence, verifies candidates against blocks and reconciles the resulting wallet history.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
scanblocks accelerates discovery by narrowing the block set, but it does not complete wallet recovery. Reliable use preserves descriptor and range evidence, verifies candidates against blocks and reconciles the resulting wallet history.
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.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.