TERM_DEF // UPGRADES_BIPS / BIP_327_MUSIG2_SPEC
BIP 327
(MUSIG2 SPEC)
(MUSIG2 SPEC)
musig2-spec/">BIP 327 (MuSig2 Spec). Standard for the MuSig2 multi-signature protocol.
This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
WHAT_BIP_327_MUSIG2_SPEC_IS
BIP 327 (MuSig2 Spec) — at a glance
UPGRADES
BIP 327 — "MuSig2 Spec" is a proposal in the Signatures family, first published in 2023 with status active. Standard for the MuSig2 multi-signature protocol. Its technical mechanism: MuSig2 — 2-round signing protocol with pre-shared nonce commitments. enables multi-sig spending that is indistinguishable from single-sig on-chain
Why it exists
DESIGN
BIP 327 (MuSig2 Spec) exists to solve a specific problem: a non-interactive multi-signature scheme producing a single 64-byte Schnorr signature. Without a written, numbered spec, every wallet and node implementer would interpret the requirement differently — and Bitcoin's value depends on every implementation agreeing exactly. BIP-327 is the single source of truth for this concern, so any new client built today can match the behaviour of every client built since 2023.
HOW_IT_WORKS
Mechanism
HOW IT WORKS
Mechanically, BIP-327 muSig2 — 2-round signing protocol with pre-shared nonce commitments. Adoption today: enables multi-sig spending that is indistinguishable from single-sig on-chain.
1. Author drafts BIP-327 against the BIP-2 template — abstract, motivation, specification, rationale.
2. The text + a reference implementation are posted on the bitcoin-dev list and as a PR to bitcoin/bips.
3. Reviewers tear it apart: ambiguities, security concerns, edge cases, interaction with prior BIPs.
4. Once stable, the BIP editor merges it; it gets a number (BIP-327) and the status "draft" or "proposed".
5. Implementations land in Bitcoin Core / wallets / other clients. For consensus changes: activation parameters chosen.
6. After deployment + adoption, BIP-327 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".
WORKED_EXAMPLE
BIP-327 — quick reference card
EXAMPLE
BIP number : 327
Title : MuSig2 Spec
Area : Signatures
First published: 2023
Status : active
Fork class : no
Motivation : a non-interactive multi-signature scheme producing a single 64-byte Schnorr signature.
Mechanism : MuSig2 — 2-round signing protocol with pre-shared nonce commitments.
Where it shows up : enables multi-sig spending that is indistinguishable from single-sig on-chain.
Read the spec : https://github.com/bitcoin/bips/blob/master/bip-0327.mediawiki
KEY_PROPERTIES
OPT-IN
No authority can force a BIP on anyone. Adoption depends entirely on whether the change is genuinely useful.
NUMBERED
Stable numeric reference — BIP-327 means the same thing across every wallet, miner, and node that has read this spec.
NON-CONSENSUS
BIP-327 is not a consensus rule — clients can implement it without coordinating with the network at large.
DEPLOYED
Implementations of BIP-327 are in production. The behaviour is observable on mainnet today.
COMMON_PITFALLS
Things that catch people out
PITFALLS
- Don't confuse "draft" / "proposed" / "final" status — read the BIP header before relying on it in production.
- The BIP number is just an editorial counter — it doesn't imply correctness or stability. Always cross-reference with the latest bitcoin/bips repo.
RELATED_CONCEPTS
Other terms from Upgrades & BIPs — click any to read its page:
TERMINOLOGY_INDEX
TERMINOLOGY
BIP 327 (MuSig2 Spec)
Standard for the MuSig2 multi-signature protocol.
Segregated Witness (SegWit, BIP 141)
The 2017 upgrade separating witness-data/">witness data, fixing tx malleability, and introducing weight units.
Taproot (BIP 341)
The 2021 upgrade introducing key-aggregable Schnorr signatures and Merkleized script trees.
Tapscript (BIP 342)
Script-language updates accompanying Taproot — new opcodes, removed limits.
Schnorr (BIP 340)
The Schnorr signature spec adopted by Taproot.
BIP Process
The community workflow for proposing, discussing, and tracking changes to Bitcoin.
Soft Fork Activation
MASF (Miner-Activated Soft Fork)
Activation triggered by miner signaling in block versions.