From: Beulah Evanjalin <beulahebenezer777@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Draft] NestedMuSig2: Recursive MuSig2 for BIP340-compatible Signatures
Date: Thu, 19 Nov 2026 00:43:58 -0800 (PST) [thread overview]
Message-ID: <0c3f16a8-2e0e-425f-8d0d-ed4fb89439afn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
Hi everyone,
I'd like to share a draft BIP specifying NestedMuSig2, a recursive
extension of BIP327 MuSig2 based on the Nested MuSig2 construction (
https://eprint.iacr.org/2026/223).
The proposal extends BIP327 to support hierarchical signing groups, where
each subgroup can participate through its aggregate public key. This allows
a tree of signers to collaboratively produce a single BIP340-compatible
signature, without revealing the internal signing structure.
BIP draft and reference implementation:
https://github.com/bitcoin/bips/pull/2297
I'd especially appreciate feedback on the specification. Specifically,
recursive nonce handling, nested session construction, root-level tweaks,
and BIP327 compatibility.
Reviews of the reference implementation and test vectors would also be very
helpful.
Thanks for your time and consideration. I look forward to your comments and
suggestions.
Best regards,
Beulah Evanjalin
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/0c3f16a8-2e0e-425f-8d0d-ed4fb89439afn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1750 bytes --]
reply other threads:[~2026-11-19 8:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0c3f16a8-2e0e-425f-8d0d-ed4fb89439afn@googlegroups.com \
--to=beulahebenezer777@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox