BIP 380–386 (Output Descriptors Family) — Glossary

TERM_DEF // UPGRADES_BIPS / BIP_380_386_OUTPUT_DESCRIPTORS_FAMILY

BIP 380–386 (OUTPUT
DESCRIPTORS FAMILY)

output-descriptors-family/">BIP 380–386 (Output Descriptors Family). The family of specs defining output descriptors and their semantics.

This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.

WHAT_BIP_380_386_OUTPUT_DESCRIPTORS_FAMILY_IS

BIP 380–386 (Output Descriptors Family) — at a glance

UPGRADES

BIP 380 is a proposal in the Descriptors family, first published in 2020 with status final. The family of specs defining output descriptors and their semantics. Its technical mechanism: output descriptors: wpkh(...), sh(wsh(...)), tr(...), with [fp/path]xpub origins. every Bitcoin Core wallet since 0.21 is descriptor-based

Why it exists

DESIGN

BIP 380–386 (Output Descriptors Family) exists to solve a specific problem: a compact, parseable string describing a wallet's scripts + key paths. Without a written, numbered spec, every wallet and node implementer would interpret the requirement differently — and Bitcoin's value depends on every implementation agreeing exactly. BIP-380 is the single source of truth for this concern, so any new client built today can match the behaviour of every client built since 2020.

HOW_IT_WORKS

Mechanism

HOW IT WORKS

Mechanically, BIP-380 output descriptors: wpkh(...), sh(wsh(...)), tr(...), with [fp/path]xpub origins. Adoption today: every Bitcoin Core wallet since 0.21 is descriptor-based.

1. Author drafts BIP-380 against the BIP-2 template — abstract, motivation, specification, rationale. 2. The text + a reference implementation are posted on the bitcoin-dev list and as a PR to bitcoin/bips. 3. Reviewers tear it apart: ambiguities, security concerns, edge cases, interaction with prior BIPs. 4. Once stable, the BIP editor merges it; it gets a number (BIP-380) and the status "draft" or "proposed". 5. Implementations land in Bitcoin Core / wallets / other clients. For consensus changes: activation parameters chosen. 6. After deployment + adoption, BIP-380 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".

WORKED_EXAMPLE

BIP-380 — quick reference card

EXAMPLE

BIP number : 380 Title : BIP 380–386 (Output Descriptors Family) Area : Descriptors First published: 2020 Status : final Fork class : no Motivation : a compact, parseable string describing a wallet's scripts + key paths. Mechanism : output descriptors: wpkh(...), sh(wsh(...)), tr(...), with [fp/path]xpub origins. Where it shows up : every Bitcoin Core wallet since 0.21 is descriptor-based. Read the spec : https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki

KEY_PROPERTIES

OPT-IN

No authority can force a BIP on anyone. Adoption depends entirely on whether the change is genuinely useful.

NUMBERED

Stable numeric reference — BIP-380 means the same thing across every wallet, miner, and node that has read this spec.

NON-CONSENSUS

BIP-380 is not a consensus rule — clients can implement it without coordinating with the network at large.

DEPLOYED

Implementations of BIP-380 are in production. The behaviour is observable on mainnet today.

COMMON_PITFALLS

Things that catch people out

PITFALLS

Don't confuse "draft" / "proposed" / "final" status — read the BIP header before relying on it in production.
The BIP number is just an editorial counter — it doesn't imply correctness or stability. Always cross-reference with the latest bitcoin/bips repo.

RELATED_CONCEPTS

Other terms from Upgrades & BIPs — click any to read its page:

TERMINOLOGY_INDEX

TERMINOLOGY

BIP 380–386 (Output Descriptors Family)

The family of specs defining output descriptors and their semantics.

Segregated Witness (SegWit, BIP 141)

The 2017 upgrade separating witness-data/">witness data, fixing tx malleability, and introducing weight units.

Taproot (BIP 341)

The 2021 upgrade introducing key-aggregable schnorr-signatures/">Schnorr signatures and Merkleized script trees.

Tapscript (BIP 342)

Script-language updates accompanying Taproot — new opcodes, removed limits.

Schnorr (BIP 340)

The Schnorr signature spec adopted by Taproot.

BIP Process

The community workflow for proposing, discussing, and tracking changes to Bitcoin.

Soft Fork Activation

The mechanism (versionbits, MASF, UASF, Speedy Trial) by which soft forks turn on.

MASF (Miner-Activated Soft Fork)

Activation triggered by miner signaling in block versions.