From: Ava Chow <lists@achow101•com>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
bitcoindev@groups•io
Subject: [bitcoin-dev] MuSig2 derivation, descriptor, and PSBT field BIPs
Date: Mon, 15 Jan 2024 23:29:46 +0000 [thread overview]
Message-ID: <5d299fc4-8809-4f32-a9b8-17e353d6ff30@achow101.com> (raw)
Hi All,
In October I sent the MuSig2 descriptor and PSBT field BIPs to the list.
Since then, I've made a few changes to the BIPs and am looking for
feedback on these.
The most significant change is the addition of third BIP which describes
how the synthetic xpubs are constructed and derived. This is split from
the descriptors BIP as I felt that the PSBT fields BIP needed to
reference this process too, and referencing the descriptors BIP for that
seemed a bit odd.
Otherwise, the descriptors BIP is unchanged, although I am open to
Salvatore's suggestion of dropping the ranged derivation within the
expression and only allow ranged derivation of the aggregate pubkey itself.
I've also made a change to the PSBT fields BIP where the aggregate
pubkey is included as a plain pubkey rather than as xonly. I think this
change is necessary for to make discovering derived keys easier. The
derivation paths for derived keys contain the fingerprint of the parent
(i.e. the aggregate pubkey) and the fingerprint requires the evenness
bit to be serialized. So the aggregate pubkey in the PSBT fields need to
contain that evenness information in order for something looking at only
the PSBT to be able to determine whether a key is derived from an
aggregate pubkey also specified in the PSBT.
The full text of the BIPs can be found at the following:
* Derivation:
https://github.com/achow101/bips/blob/musig2/bip-musig2-derivation.mediawiki
* Descriptors:
https://github.com/achow101/bips/blob/musig2/bip-musig2-descriptors.mediawiki
* PSBT:
https://github.com/achow101/bips/blob/musig2/bip-musig2-psbt.mediawiki
Thanks,
Ava Chow
next reply other threads:[~2024-01-15 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 23:29 Ava Chow [this message]
2024-01-16 8:18 ` Christopher Allen
2024-01-23 12:12 ` Michael Folkson
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=5d299fc4-8809-4f32-a9b8-17e353d6ff30@achow101.com \
--to=lists@achow101$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoindev@groups$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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