Three independent signing devices placed on separate mats, with two screens illuminated, editorial illustration
BIP 390 / MULTISIG

Put MuSig2 in a descriptor.

The musig() key expression describes an aggregate key assembled from multiple participants.

Read the explanation
← All standards

Why it exists

BIP 390 introduces musig() as a descriptor key expression for MuSig2 aggregate keys. It describes how several participant keys produce the one public key used in an output, preserving the construction needed for a wallet to recognize and coordinate spending.

How it works

In one form, participant keys are derived for an address index, sorted and then aggregated. Another form aggregates suitable public keys first and applies further unhardened derivation to the aggregate, using BIP 328. These are distinct constructions with different syntax constraints.

The expression belongs inside supported output expressions such as tr(). It records the key construction; the interactive signing protocol remains a separate process. Participants must exchange the required nonce and signature data safely to produce a valid aggregate signature.

PUT IT IN CONTEXT

A practical example

A schematic tr(musig(A,B)/0/*) describes outputs derived from the aggregate of two suitable account keys. A and B are placeholders, not real keys. Both participants are required for this aggregate signing path; musig() does not mean an arbitrary two-of-three threshold policy.

What to keep in mind

Parsing a descriptor and deriving its addresses does not establish that a wallet can complete MuSig2 signing. Nonce misuse can compromise keys. Recovery must preserve participants, derivation choices and any alternative script paths, as well as the required signing material.

Status & implementation

The BIP remains Draft. Core documents MuSig2 descriptor parsing from 30.0 and signing from 31.0. These separate milestones show why an earlier wallet may recognize an output without being able to execute its signing workflow.

Specification status: Draft · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close