An open recovery folder, signing device, blank steel backup plate and sealed envelope, editorial illustration
BIP 380 / BACKUP

Describe the wallet, not just its keys.

Descriptors express how keys and scripts produce a wallet’s outputs. The general format also defines an error-detecting checksum.

Read the explanation
← All standards

Why it exists

BIP 380 defines the common language of output script descriptors. A descriptor records how keys and script expressions produce wallet outputs, filling a gap left by a seed-only backup: the same keys can participate in different address types and policies.

How it works

A script expression states the output construction. Key expressions can carry a public or private key, an extended key, key-origin information and derivation steps. A final wildcard describes a series of child keys rather than one address.

An optional eight-character checksum detects transcription mistakes, and applications can require it. The checksum does not authenticate the author or prove that the wallet is safe. Separate BIPs define particular expressions such as multisig and Taproot.

PUT IT IN CONTEXT

A practical example

A watch-only wallet given a receiving descriptor can derive and monitor the corresponding addresses. A complete recovery record also includes change and every relevant policy branch. For a multisig wallet, that means the full cosigner configuration, not merely the keys held on two surviving devices.

What to keep in mind

Descriptors containing private keys grant spending power. Public-only descriptors still reveal a collection of linked addresses. Neither kind records all off-chain metadata automatically: transaction labels, signer instructions and any additional backup requirements need separate attention.

Status & implementation

Core documents descriptor support since 0.17.0 and uses descriptors to represent wallet outputs. The BIP is Deployed, but importing software must support the specific expression and derivation features present in the descriptor.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Find your next answer.

Search the complete field guide · Esc to close