MuSig2
An enhanced version of MuSig that lowers the number of interaction rounds needed among cosigners.
MuSig2 is the practical successor to the original MuSig Schnorr-aggregation protocol, published in 2020 by Jonas Nick, Tim Ruffing, and Yannick Seurin. It does the same job - aggregate n cosigners into a single combined public key with a single combined signature - in just two rounds of communication instead of three, with the additional benefit that the first round's nonces can be generated and exchanged before the message is known. Each nonce must still be used exactly once; reusing one across sessions leaks the private key.
What changed mechanically:
- MuSig1 required commit-then-reveal nonces (three rounds): each signer first publishes a commitment to their nonce, then the actual nonces, then the partial signatures. The commit-reveal step was necessary to stop a signer from choosing its nonce after seeing everyone else's, which lets an attacker forge signatures across concurrent sessions using Wagner's algorithm; the original two-round MuSig was withdrawn for exactly this reason. (Key-cancellation, or rogue-key, attacks are a different problem, already solved by MuSig's key-aggregation coefficients.)
- MuSig2 uses two independent nonces per signer instead of one, combined in a way that defeats the same attack without needing commitments. Two rounds: exchange nonce pairs, then exchange partial signatures.
For ergonomics this is a meaningful upgrade. Three rounds means three back-and-forth messages with every signer; two rounds means two. For Lightning channel opens, multisig spend signing, and federation signature protocols where cosigners are geographically distributed, the round reduction is the difference between "signing this thing takes about a minute" and "signing this thing takes about ten seconds."
Properties (shared with MuSig1):
- n-of-n only. All cosigners must participate. For m-of-n threshold setups, FROST is the analog.
- Aggregated key. Deterministic function of the cosigner pubkeys.
- 64-byte signature. Same size as Taproot single-sig.
- Privacy. On-chain, indistinguishable from a Taproot key-path single-sig spend.
MuSig2 is the version that actually ships in production tooling: BIP 327 (drafted in 2022, merged in March 2023) standardized it, libsecp256k1 has shipped it since v0.6.0 in November 2024, and Ledger's Bitcoin app added it in March 2025, the first major hardware wallet to do so. When people say "MuSig" in 2026 they almost always mean MuSig2.
See How Taproot Actually Works for where an aggregate key sits in a Taproot output.
Key takeaways
- Minimizes the communication overhead in multi-party signing
- Maintains the privacy and size advantages of MuSig
- Ideal for collaborative setups with participants in different time zones
Related chapters
Corrected
-
Was: The entry said MuSig2's first-round nonces can be 'reused across signing sessions', and that the original MuSig needed its commit-reveal round to stop a key-cancellation attack.
Now: BIP-327 warns that signing twice with the same nonce exposes the secret key, so each nonce must be used exactly once, and the corrected entry says so. It also explains that the extra round in the original MuSig blocked forgeries across concurrent signing sessions, which is a different problem from key cancellation. Details
External references (1)
Related terms (14)
- PSBT (Partially Signed Bitcoin Transaction)
- ECDSA (Elliptic Curve Digital Signature Algorithm)
- Elliptic Curve
- HDM (Multi-Signature HD Wallet)
- Hierarchical Multisig
- Interactive Multi-Sig
- M-of-n
- Mono-Signature
- MuSig
- Partial Signature
- Quorum Signatures
- Schnorr Signature
- Signature Aggregation
- Signature Clipping
Published . Revised . One correction logged for this page.
Edit this page on GitHub