MuSig2: Simple Two-Round Schnorr Multi-Signatures

Authors Jonas Nick; Tim Ruffing; Yannick Seurin
Year 2020 (IACR ePrint; published at CRYPTO 2021)
Project MuSig2 / Bitcoin
License CC BY 4.0 for the IACR paper; BIP 327 has a separate BSD-3-Clause license
Official Source MuSig2 research paper (IACR ePrint)

This page is an educational summary, not a verbatim reproduction or a wallet setup guide. MuSig2 is a specific n-of-n Schnorr multi-signature protocol. It does not by itself provide a 2-of-3 or other threshold policy, and a published specification does not mean every wallet supports it.

Publication and Current Specification

Jonas Nick, Tim Ruffing, and Yannick Seurin introduced MuSig2 in IACR ePrint 2020/1261, received on October 14, 2020. The ePrint is a major revision of their CRYPTO 2021 publication in LNCS 12825, pages 189–221; the archive lists its latest revision on October 20, 2023. The IACR page labels the paper CC BY. That research-paper license is separate from the implementation specification’s license.

BIP 327, “MuSig2 for BIP340-compatible Multi-Signatures,” specifies the protocol for Bitcoin-compatible Schnorr keys and signatures. Its current header marks it Deployed and Informational, lists Jonas Nick, Tim Ruffing, and Elliott Jin as authors, and identifies version 1.0.4, dated August 19, 2026. The BIP document is BSD-3-Clause; that license does not replace or change the paper’s CC BY license. “Deployed” describes the BIP’s status, not universal support in wallets or a new Bitcoin consensus rule.

What MuSig2 Does

MuSig2 lets a group combine public keys and cooperate to produce one ordinary Schnorr signature that verifies against an aggregate public key. For a Bitcoin Taproot key-path spend, this can make a shared n-of-n output look like a single-key Taproot spend to a blockchain observer. The privacy benefit applies to the key path; it does not hide information revealed by a script-path spend, wallet behavior, or other data.

MuSig2 is n-of-n: every signer included in the aggregate key must take part in the signing session. It is not a t-of-n threshold scheme. If a policy is “any 2 of these 3 people can sign,” ordinary MuSig2 is not that policy. A wallet can instead use a threshold protocol such as FROST or a Bitcoin script that expresses the desired policy, with different setup and on-chain trade-offs.

Key Aggregation and Taproot

Before a signing session, participants exchange their public keys and calculate an aggregate key using the MuSig2 key-aggregation algorithm. It uses coefficients derived from the key list rather than simply adding public keys, helping address rogue-key attacks. The input order can affect the result, so applications need a consistent ordering or the specified sorting process. This setup step is not one of MuSig2’s two signing communication rounds.

For Taproot, the aggregate internal key may be tweaked to create the output key and commit to an optional script tree. The untweaked aggregate key and the final Taproot output key are therefore not always the same value. BIP 327 specifies support for these tweaks and for producing signatures that verify under the tweaked key.

The Two Signing Rounds

  1. Nonce exchange: Each signer creates a secret nonce and its public counterpart, each containing two nonce components, then shares the public nonce with the other participants. MuSig2 does not add a separate nonce-commitment round. A binding coefficient combines the nonce components using the complete nonce set, aggregate key, and message.
  2. Partial signatures: After the session data is fixed, every signer computes a partial signature. Participants can verify contributions; the valid partial signatures are aggregated into one BIP340-compatible Schnorr signature.

Some applications can prepare the first round before the message is ready. That can shorten the later interaction, but it means secret nonce material may need to be stored longer, increasing the importance of safe, single-use state.

Key Technical Properties

Research paper IACR ePrint 2020/1261; CRYPTO 2021 publication; revised through October 2023
Signature family Schnorr, compatible with BIP340
Signer policy n-of-n; all participants in the aggregate key sign
Signing communication Two rounds: public-nonce exchange, then partial-signature exchange
Bitcoin specification BIP 327, Deployed / Informational, version 1.0.4 (August 19, 2026)
Separate threshold protocol FROST is a distinct t-of-n protocol, specified in RFC 9591
Licenses IACR paper: CC BY; BIP 327: BSD-3-Clause

Nonce Safety

Each secret nonce must be used for one signing session only. Reusing the same secret nonce in multiple signing operations can expose a signer’s private key. The protocol has no commitment-hash round that makes reuse safe, and saving a commitment is not a substitute for correct nonce handling. BIP 327 calls for high-quality randomness and careful protection of the secret nonce and session state; implementations must prevent accidental reuse across crashes, retries, and concurrent sessions.

This is a protocol-level requirement, not a guarantee that a particular wallet or hardware device handles state correctly. Users should follow the wallet’s documented recovery and multisignature procedures and should not improvise protocol steps from a general explanation.

Security Model and Limits

The paper presents proofs for two variants: one in the random-oracle model, and a more efficient variant in the random-oracle and algebraic-group models. Both rely on a weaker variant of the one-more discrete-logarithm assumption. BIP 327 describes its security in terms of the algebraic one-more discrete-logarithm (AOMDL) assumption. These are formal results under stated assumptions, not proof that every implementation, device, coordinator, or key-management process is free of defects.

MuSig2 can reduce the on-chain visibility of an n-of-n key-path spend, but it does not remove the need to coordinate signers, back up wallet descriptors and recovery data, or protect each key. If a required signer is unavailable, the group cannot complete an ordinary MuSig2 signature. A separate script path can provide an alternative spending policy, but using that path may reveal more information on-chain.

MuSig2 and FROST Are Different

FROST is a separate Schnorr threshold-signing protocol. It allows a threshold number of participants holding shares of a distributed secret to produce a signature; MuSig2 instead requires all n signers represented in its aggregate key. FROST is not an extension or mode of MuSig2, even though both use two signing rounds and can produce Schnorr-compatible signatures in supported ciphersuites.

RFC 9591 specifies FROST and is published for informational purposes. The RFC explicitly says it is not an Internet Standards Track specification, an IETF product, or a standard. A wallet’s use of either protocol depends on its own implementation and supported key setup.

Bitcoin Uses and Adoption

The clearest Bitcoin use described by BIP 327 is cooperative n-of-n signing for a Taproot key-path output. A BIP’s Deployed status does not tell users which particular wallet versions expose MuSig2, whether two devices interoperate, or how recovery works. Check the wallet vendor’s current documentation for those details.

Do not infer that MuSig2 is required for every Lightning payment, payment-channel close, or proposed point time-locked contract (PTLC). The research paper and BIP specify a signing scheme; they do not establish universal deployment in Lightning software. Likewise, a 2-of-3 custody product may use a threshold protocol, script policy, or another arrangement. Do not label a product’s signing algorithm without a direct source from its provider.

Related Terms

See Also

Sources

Social Media Sentiment

A small sample of recent r/Bitcoin discussions showed interest in Taproot and aggregated-signature privacy alongside practical questions about wallet support, signer coordination, backups, and recovery. One development thread listed MuSig2 among Bitcoin privacy and multisignature work; a separate multisignature discussion focused on setup and recovery complexity. This is a limited sample of forum posts, not a representative measure of Bitcoin users or wallet adoption. Technical status is better established by BIP 327 than by Reddit comments; the discussion links are included for context.

Last updated: 2026-10