From: Christopher Allen <ChristopherA@lifewithalacrity•com>
To: Ava Chow <lists@achow101•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: bitcoindev@groups•io
Subject: Re: [bitcoin-dev] MuSig2 derivation, descriptor, and PSBT field BIPs
Date: Tue, 16 Jan 2024 00:18:26 -0800 [thread overview]
Message-ID: <CACrqygDY0p-trbHGyhg0_uyViyryyJqO-CkOS6+tknTUG05Wew@mail.gmail.com> (raw)
In-Reply-To: <5d299fc4-8809-4f32-a9b8-17e353d6ff30@achow101.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Mon, Jan 15, 2024 at 4:28 PM Ava Chow via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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 topic of some challenges in using x-only pubkeys with FROST recently
came up in a conversation that I didn't completely understand. It sounds
like it may be related to this issue with MuSig2.
What are the gotcha's in x-only keys with these multisig protocols? Can you
explain a little more? Any other particular things do we need to be careful
about with x-only pubkeys? I had mistakenly assumed the technique was just
a useful trick, not that it might cause some problems in higher level
protocols.
Thanks!
-- Christopher Allen
[-- Attachment #2: Type: text/html, Size: 1751 bytes --]
next prev parent reply other threads:[~2024-01-16 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 23:29 Ava Chow
2024-01-16 8:18 ` Christopher Allen [this message]
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=CACrqygDY0p-trbHGyhg0_uyViyryyJqO-CkOS6+tknTUG05Wew@mail.gmail.com \
--to=christophera@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoindev@groups$(echo .)io \
--cc=lists@achow101$(echo .)com \
/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