Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£857.98
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains Bitcoin Core rescanblockchain 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 rescanblockchain searched local blocks for transactions related to the wallet. Optional start and stop heights bounded the scan; omission meant genesis and current tip respectively.
- Why it matters: rescanblockchain is a wallet-history discovery process whose result is only as complete as its known scripts, local block range and actual scanned bounds. Reconciliation, not command completion, proves recovery.
- Current position: Bitcoin Core 0.16.0 rescanblockchain searched local blocks for transactions related to the wallet.
Bitcoin Core rescanblockchain RPC in simple English
Bitcoin Core rescanblockchain RPC: Omitting start scans from genesis and omitting stop continues to tip. Full-history work can be expensive. Schedule it on an appropriate node, monitor CPU and disk and keep wallet-dependent financial automation paused.
Simple example
A miner is checking Bitcoin Core rescanblockchain RPC. Record active tip and chainwork at start and completion, especially if the tip advances during a long scan.
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.
Bounds validation
Use non-negative heights with start no greater than stop or active tip. Derive the start from the earliest relevant key or script time with a safety margin. A late start can silently omit history.
Defaults and cost
Omitting start scans from genesis and omitting stop continues to tip. Full-history work can be expensive. Schedule it on an appropriate node, monitor CPU and disk and keep wallet-dependent financial automation paused.
Returned range
Trust but verify returned start_height and stop_height rather than assuming requested values were fully processed. Record active tip and chainwork at start and completion, especially if the tip advances during a long scan.
Pruned-node limits
A pruned node may lack block bodies needed below its retained boundary. Use an archive-capable node or proof-based recovery. Do not interpret an unavailable historical range as evidence that the wallet had no transactions there.
Wallet scope
A rescan finds only scripts, addresses and keys already known to the wallet. Import recovery material first under a controlled backup procedure. Scanning cannot recover an unknown private key or unspecified script.
Abort and restart
abortrescan can stop work, leaving history incomplete. Record interruption and repeat from a conservative boundary. Test how the running version reports concurrent scans, restart and partially discovered state.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core rescanblockchain RPC?
Bitcoin Core rescanblockchain RPC: Omitting start scans from genesis and omitting stop continues to tip.
For Bitcoin Core rescanblockchain RPC, what should a beginner know about bounds validation?
Use non-negative heights with start no greater than stop or active tip.
For Bitcoin Core rescanblockchain RPC, what should a beginner know about defaults and cost?
Omitting start scans from genesis and omitting stop continues to tip. Full-history work can be expensive.
For Bitcoin Core rescanblockchain RPC, what should a beginner know about returned range?
Trust but verify returned start_height and stop_height rather than assuming requested values were fully processed.
Conclusion
rescanblockchain is a wallet-history discovery process whose result is only as complete as its known scripts, local block range and actual scanned bounds. Reconciliation, not command completion, proves recovery.
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.