The descriptor BIPs are reclassified from Standard to Specification
Victoria Shinder1 min readA change merged into the Bitcoin Improvement Proposals repository updates BIP 379 through BIP 390 to the Specification type. The pull request, #2292 from danielabrozzoni, was merged by murchandamus.
Those numbers are the descriptor BIPs — the documents defining output descriptors and the individual script expressions built on them, the notation a modern wallet uses to say which outputs it owns and how they can be spent.
What it means
This is metadata, and metadata in the BIP repository is how the process communicates what a document is for. The revised BIP process distinguishes between types, and moving a document from one to another is a statement about the kind of agreement it represents: a Specification describes something implementations are expected to conform to, as distinct from a proposal about how Bitcoin's consensus rules should change.
That distinction is the right one for descriptors. Nothing in BIP 379-390 asks the network to agree to anything — no soft fork, no consensus change. What they do is define an interchange format, and the property that makes them valuable is that two independently written wallets read the same string and derive the same addresses. Interoperability documents fail differently from consensus proposals, and classifying them differently is an admission that the process was conflating two things.
Nothing changes in any wallet because of this commit. It is worth a note only because BIP type labels are the first thing a reader uses to judge what weight a document carries, and a reader who assumed descriptor support was optional-because-proposal has been reading the wrong signal.