Bitcoin Core listdescriptors RPC for Wallet Inventory

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.

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.

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.