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 importdescriptors RPC: Safe Wallet Import Guide
Bitcoin Core 0.21 importdescriptors guide covering descriptor checksums, timestamps, ranges, active and internal flags, rescans, partial results and backups.
This guide explains Bitcoin Core importdescriptors 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.21 introduced importdescriptors for descriptor wallets. It accepts a required array of complete descriptor requests and can trigger a blockchain rescan from the earliest supplied timestamp.
- Why it matters: importdescriptors makes descriptor-wallet recovery and watch-only provisioning precise, but timestamp, range and internal semantics determine what the wallet discovers and how it classifies outputs. Validate every request and back up the resulting wallet.
- 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
- 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.
Wallet boundary
Use this RPC only with a descriptor wallet selected explicitly through the wallet endpoint. Record the network, wallet name, database format and whether private keys are enabled.
Descriptor request
Each entry requires a descriptor and timestamp. Validate the descriptor and checksum with getdescriptorinfo, preserve key origins and never place private descriptors in shell history or general logs.
Time and rescan
Timestamp zero scans the entire chain, while now skips historical scanning for scripts known never to have been used. Core scans from up to two hours before the earliest timestamp; an early value can take over an hour.
Ranges and activation
Ranged descriptors can specify an end or begin-and-end range. An active ranged descriptor may set next_index; active, range, internal and label values must reflect the intended receive or change policy.
Internal and labels
Internal marks matching outputs as non-incoming, such as change. Labels are allowed only when internal is false. Incorrect classification can distort payment reporting even when scripts are technically valid.
Partial results
The result array matches the request array and each entry has success plus optional warnings or error. Inspect every element and do not roll forward if only part of a coordinated policy imported.
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 Bitcoin Core importdescriptors RPC?
Bitcoin Core 0.21 introduced importdescriptors for descriptor wallets. It accepts a required array of complete descriptor requests and can trigger a blockchain rescan from the earliest supplied timestamp.
Is Bitcoin Core importdescriptors 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 importdescriptors RPC matter?
importdescriptors makes descriptor-wallet recovery and watch-only provisioning precise, but timestamp, range and internal semantics determine what the wallet discovers and how it classifies outputs. Validate every request and back up the resulting wallet.
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
importdescriptors makes descriptor-wallet recovery and watch-only provisioning precise, but timestamp, range and internal semantics determine what the wallet discovers and how it classifies outputs. Validate every request and back up the resulting wallet.
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.