From: Andrew Chow <lists@achow101•com>
To: Anthony Towns <aj@erisian•com.au>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposed BIP for MuSig2 PSBT Fields
Date: Wed, 11 Oct 2023 23:59:16 +0000 [thread overview]
Message-ID: <5ebdc1ea-583e-472f-a7ff-6ae8976bf0fb@achow101.com> (raw)
In-Reply-To: <ZSc0Luwg3rpNvkfJ@erisian.com.au>
On 10/11/2023 07:47 PM, Anthony Towns wrote:
> On Tue, Oct 10, 2023 at 10:28:37PM +0000, Andrew Chow via bitcoin-dev wrote:
>> I've written up a BIP draft for MuSig2 PSBT fields. It can be viewed at
>> https://github.com/achow101/bips/blob/musig2-psbt/bip-musig2-psbt.mediawiki.
>
> I was hoping to see adaptor signature support in this; but it seems that's
> also missing from BIP 327?
This is the first time I've heard of that, so it wasn't something that I
considered adding to the BIP. Really the goal was to just be able to use
BIP 327.
But that doesn't preclude a future BIP that specifies how to use adaptor
signatures and to have additional PSBT fields for it. It doesn't look
like those are mutually exclusive in any way or that the fields that
I've proposed wouldn't still work.
I don't know enough about the topic to really say much on whether or how
such fields would work.
> FWIW, "participant" is typoed a bunch ("particpant")and the tables are
> hard to read: you might consider putting the description as a separate
> row? eg:
>
> https://github.com/ajtowns/bips/blob/202310-table/bip-musig2-psbt.mediawiki
Yes, I've been making some minor fixes throughout the day, and I'll
probably take your suggestion for the tables. Mediawiki tables are the
bane of my existence.
Andrew
next prev parent reply other threads:[~2023-10-11 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 22:28 Andrew Chow
2023-10-11 23:47 ` Anthony Towns
2023-10-11 23:59 ` Andrew Chow [this message]
2023-10-12 7:39 ` Anthony Towns
2023-10-12 7:43 ` Jonas Nick
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=5ebdc1ea-583e-472f-a7ff-6ae8976bf0fb@achow101.com \
--to=lists@achow101$(echo .)com \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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