Why it exists
BIP 383 gives descriptors a way to express ordinary threshold multisig scripts. The multi() and sortedmulti() expressions record how many signatures are required and which keys can provide them, making the shared wallet configuration explicit and portable.
How it works
In multi(k,KEY1,KEY2,...), k is the signature threshold and keys retain the supplied order. sortedmulti() uses the same threshold but sorts the actual public keys before building each script. Both describe CHECKMULTISIG-based constructions.
When extended keys are ranged, they advance together at the same address index. Sorting happens after child derivation. Wrappers such as wsh() or sh() determine how the script appears on-chain and impose their own key-count and encoding restrictions.
A practical example
The schematic expression wsh(sortedmulti(2,A/0/*,B/0/*,C/0/*)) describes native-SegWit receiving scripts requiring two of three cosigners. A, B and C stand for complete extended-key expressions; this illustration omits real keys, origins and checksum and is not an importable wallet.
What to keep in mind
A public descriptor reconstructs addresses but cannot replace missing signing secrets. The threshold, wrapper, all cosigner keys and derivations must match the funded wallet. These expressions are not the Taproot CHECKSIGADD forms: copying multi() into a Taproot script tree is not a valid substitution.
Status & implementation
The official status is Deployed. Core lists these multisig descriptor expressions among its supported descriptor features, with the descriptor family implemented from 0.17.0. A device may still support only a subset of policies or signer counts.
Specification status: Deployed · Sources checked 13 November 2026
