Multisig Output Script Descriptors

The five-minute read

One action, walked through

1. Open BIP 383 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 multi() , and sortedmulti() output script descriptors.
3. Name the object that changes: KEY_1, KEY_2.
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 383 at the status the text itself states: Deployed.
• The object that has to change is KEY_1, KEY_2. A neighbouring document with a similar name is not this one.
• Wallet support is not the same as consensus validity.

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 is covered by the signed bytes in Multisig Output Script Descriptors?
• Can the same signature be replayed on another chain, account, or message?
• Which primitive does the text require: KEY_1, KEY_2?

Terms

BIP 383

The public text titled Multisig 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

A signature that does not commit to what the user saw can be replayed into a different spend, a different chain, or a different message.

What the design proposes

• This document specifies multi() , and sortedmulti() output script descriptors.
• Both functions take a threshold and one or more public keys and produce a multisig output script.
• multi() specifies the public keys in the output script in the order given in the descriptor while sortedmulti() sorts the public keys lexicographically when the output script is produced.

How the mechanism is specified

• Taken from the specification, the next constraint is: Both functions take a threshold and one or more public keys and produce a multisig output script.
• Locate KEY_1, KEY_2 in BIP 383 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

• A signature scheme is not a privacy system. It hides the signer only if the protocol says so.
• Wallet support is not the same as consensus validity.
• 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 383 when a pitch says 'Multisig Output Script Descriptors' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.