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

Many signers. One Schnorr signature.

MuSig2 combines participant keys and partial signatures into a BIP 340-compatible signature.

Read the explanation
← All standards

Why it exists

BIP 327 standardizes MuSig2, a protocol in which several people jointly produce one Schnorr signature. The result can verify against one aggregate public key, so a cooperative Taproot spend need not publish a separate signature for every participant. The private keys remain separate throughout the protocol.

How it works

Participants first agree on the public-key set and aggregate key. During signing they exchange public nonces, then produce partial signatures for the agreed session and transaction message. The contributions are combined into a BIP 340-compatible signature. The aggregation rules are designed to resist attacks involving maliciously chosen participant keys.

The protocol supports key tweaks used by Taproot and public child-key derivation. Those tweaks, participant keys, nonces and message must all match the same session. BIP 373 describes how PSBT can transport the public signing data; it does not change MuSig2’s cryptographic requirements.

PUT IT IN CONTEXT

A practical example

Two company officers can jointly control an aggregate key. Both devices exchange nonce data and approve the same payment, then contribute partial signatures. The blockchain ultimately sees one valid signature. If either officer refuses or loses access, that aggregate key alone cannot spend; a separately designed recovery path would be needed.

What to keep in mind

MuSig2 is n-of-n, not a general two-of-three threshold scheme. Secret nonce reuse is dangerous, including after backups or interrupted sessions. Compact on-chain appearance also does not hide transaction amounts, counterparties’ records or information leaked by the coordinator.

Status & implementation

Bitcoin Core supports MuSig2 key aggregation from 30.0 and signing from 31.0. The BIP is Deployed, but device interoperability and recovery-policy support must still be checked.

Specification status: Deployed · 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