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 listdescriptors RPC for Wallet Inventory
Bitcoin Core 22 listdescriptors guide to public descriptors, timestamps, flags, ranges, next indexes, backups, privacy controls and restoration tests.
This guide explains Bitcoin Core listdescriptors 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 22.0 introduced listdescriptors for descriptor-enabled wallets. It returns the wallet name and public versions of imported descriptors with creation timestamps, active and internal flags, and range or next-index state where applicable.
- Why it matters: listdescriptors turns wallet policy into auditable inventory. Its public output still needs strong confidentiality, and a real backup must pair descriptors and range state with signing custody and a tested restoration procedure.
- 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.
Scope
The RPC applies to a selected descriptor-enabled wallet and has no arguments in 22.0. Select the intended wallet endpoint explicitly and record the returned wallet_name before trusting the inventory.
Public descriptors
Core returns public descriptor forms, which support watch-only discovery but should not expose private keys. Public extended keys, origins and derivation patterns remain sensitive operational data.
Flags
active marks descriptors used for address generation; internal distinguishes change from receive only for active entries. Inactive does not mean irrelevant because historical funds may still depend on it.
Time and range
timestamp controls historical scan boundaries. Ranged descriptors may include inclusive range bounds and the next address index, which are central to gap-safe recovery and issuance continuity.
Backup use
Capture the inventory into encrypted, access-controlled recovery evidence and pair it with seed or signer custody, network, wallet version and restoration instructions. The output alone cannot sign.
Change control
Diff canonical descriptors, flags, ranges and next indexes before and after imports or upgrades. Investigate unexpected key origins, wrapper types, disabled descriptors or index regressions.
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 listdescriptors RPC for Wallet Inventory?
Bitcoin Core 22.0 introduced listdescriptors for descriptor-enabled wallets. It returns the wallet name and public versions of imported descriptors with creation timestamps, active and internal flags, and range or next-index state where applicable.
Is Bitcoin Core listdescriptors RPC for Wallet Inventory 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 listdescriptors RPC for Wallet Inventory matter?
listdescriptors turns wallet policy into auditable inventory. Its public output still needs strong confidentiality, and a real backup must pair descriptors and range state with signing custody and a tested restoration procedure.
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
listdescriptors turns wallet policy into auditable inventory. Its public output still needs strong confidentiality, and a real backup must pair descriptors and range state with signing custody and a tested restoration procedure.
Primary sources
- Bitcoin Core 22.0 listdescriptors RPC
- Bitcoin Core 22.0 release notes
- Bitcoin Core descriptor documentation
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.