raw() and addr() Output Script Descriptors

The five-minute read

One action, walked through

1. Open BIP 385 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This document specifies raw() and addr() output script descriptors.
3. Name the object that changes: raw() and addr() Output Script Descriptors.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 385 at the status the text itself states: Deployed.
• The object that has to change is raw() and addr() Output Script Descriptors. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

What happened after the paper

The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What must an implementation of raw() and addr() Output Script Descriptors accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: raw() and addr() Output Script Descriptors?

Terms

BIP 385

The public text titled raw() and addr() Output Script Descriptors.

Deployed

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• This document specifies raw() and addr() output script descriptors.
• In order to make descriptors maximally compatible with scripts in use today, it is useful to be able to wrap any arbitrary output script or an address into a descriptor.
• Two new script expressions are defined: raw() and addr() .

How the mechanism is specified

• Taken from the specification, the next constraint is: In order to make descriptors maximally compatible with scripts in use today, it is useful to be able to wrap any arbitrary output script or an address into a descriptor.
• Locate raw() and addr() Output Script Descriptors in BIP 385 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 385 when a pitch says 'raw() and addr() Output Script Descriptors' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.