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

Coordinate MuSig2 in a PSBT.

Additional PSBT fields carry MuSig2 participant keys, public nonces and partial signatures.

Read the explanation
← All standards

Why it exists

BIP 373 extends PSBT to coordinate MuSig2 signing. Instead of collecting several independent signatures for a multisig script, participants exchange the public information needed to produce one aggregate Schnorr signature. The extension helps different coordinators and signers agree on how to package each round.

How it works

The fields identify the participant public keys behind an aggregate key and carry public nonces and partial signatures. Related key-origin fields describe derivation and help identify change. They do not carry the secret nonce values that each signer must protect locally.

First the participants contribute public nonces. Once the required nonces are present, each signer checks the session and adds a partial signature. A final signer or finalizer can combine the contributions into a BIP 340 signature, which then fits the ordinary Taproot key-path or script-path signature field. These fields work in PSBT v0 and v2.

PUT IT IN CONTEXT

A practical example

In a two-party wallet, one device adds its public nonce and the other adds its own. The package must return to both parties with the complete nonce set before each produces its partial signature. A coordinator can carry these packages between devices, but possession of the packages alone does not give it either private key or permission to sign a different payment.

What to keep in mind

MuSig2 requires all participants in that aggregate key. Secret nonce reuse can compromise a signing key; restarting or restoring a session must be handled by the signer implementation. PSBT fields are a transport convention, not a replacement for the cryptographic protocol.

Status & implementation

Bitcoin Core added these fields in 30.0; MuSig2 signing followed in 31.0. The BIP’s repository status is Complete, which describes the specification rather than universal wallet support.

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