Bitcoin output descriptors and wallet recovery
Understand script policies, key origins, receive/change branches and checksums before relying on a descriptor backup.
The quick answer
An output descriptor describes how a wallet derives output scripts from keys and a spending policy. It can preserve information that recovery words alone may not identify.
A descriptor can be public or secret
Descriptors may contain extended public keys or private key material. Public versions expose address derivation and financial history; private versions can authorize spending. A checksum catches mistakes, not a malicious replacement with a valid checksum.
Step by step
- 1
Export from the trusted wallet
Use its documented descriptor or configuration export. Preserve the script expression, key origins, derivation paths and checksum exactly.
- 2
Keep receive and change coverage
Record all required branches and relevant wallet metadata, such as range or scan starting information. A single displayed address is not equivalent to the full account policy.
- 3
Test compatible recovery
Import into a suitable practice or watch-only setup following official instructions. Compare derived addresses with your signer before relying on the export.
Worked example
An account may derive receive addresses under /0/* and change under /1/*. Saving only the receive branch can omit information needed to find change outputs.
Before you continue
A related question
Does a public descriptor replace signing keys?
No. It can reconstruct the covered scripts and monitor funds, but the required private keys are still needed to satisfy the spending policy.
Try it with a tool
Sources & further reading
Source links checked on 15 Oct 2026. Examples explain the mechanics; provider fees and features can change.
- Bitcoin Core github.com
- BIP 380 github.com
