A Taproot output controlled by several signers through key aggregation, such as MuSig2 (BIP 327), can be spent with one aggregate key and one signature, so on chain it is indistinguishable from a single-signer Taproot output.
Sources and checks
T1BIP 327, MuSig2 for BIP340-compatible Multi-SignaturesBIP, says this directly
MuSig2 Taproot outputs are indistinguishable for a blockchain observer from regular, single-signer Taproot outputs
Motivation, read 2026-11-20
T1BIP 341, TaprootBIP, says this directly
Such multi-party public keys and signatures are indistinguishable from their single-party equivalents.
Design, Schnorr signature validation, read 2026-11-20
BIP 327's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0327.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 17:27 UTCblock 976,759
Published Revision 1, run 2026-11-20-seed-taproot