An open recovery folder, signing device, blank steel backup plate and sealed envelope, editorial illustration
BIP 328 / KEYS

Derive from an aggregate key.

BIP 328 defines a BIP 32-compatible extended public key for MuSig2 aggregate keys.

Read the explanation
← All standards

Why it exists

BIP 328 defines how a MuSig2 aggregate public key can become the root of an extended public key. This allows a shared wallet to derive fresh public keys without repeatedly deriving and combining a new key from every participant. It connects MuSig2 aggregation with familiar BIP 32 public derivation.

How it works

The scheme wraps the aggregate key in a synthetic xpub with a specified fixed chain code and root metadata. Anyone holding this xpub can derive non-hardened public children using BIP 32 rules. This is public information; no one receives a combined private key as part of the process.

When signing for a derived child, the participants account for each derivation tweak in their MuSig2 session. Deriving the public key is therefore only one half of the workflow: compatible signers must reproduce and apply the same tweaks when forming the signature. BIP 390 supplies descriptor notation for relevant wallet constructions.

PUT IT IN CONTEXT

A practical example

A coordinator could derive receiving branch 0 and address index 7 from the synthetic xpub while both signers remain offline. Later, to spend that output, both signers need the agreed aggregate-key context and the same derivation path. Merely owning the xpub is sufficient to watch the branch, but cannot produce the spending signature.

What to keep in mind

Only non-hardened derivation is available from this aggregate public key. Sharing the synthetic xpub exposes its descendants, much like sharing a conventional account xpub. Recovery also requires participant keys and policy context; the xpub is not a substitute for the individual signing backups.

Status & implementation

Bitcoin Core supports this derivation through musig() descriptors from 30.0. The BIP is Complete; that status does not imply every BIP 32 wallet can sign for MuSig2-derived children.

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