From: Matt Corallo <lf-lists@mattcorallo•com>
To: Andrew Poelstra <apoelstra@wpsoftware•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Michael Folkson <michaelfolkson@gmail•com>
Subject: Re: [bitcoin-dev] Update on "Speedy" Trial: The circus rolls on
Date: Thu, 8 Apr 2021 11:18:33 -0400 [thread overview]
Message-ID: <125be010-93b9-f7dd-70d4-81a63a603621@mattcorallo.com> (raw)
In-Reply-To: <YG8TbUFieg1yb/Ax@camus>
Probably worth noting, but while the coin toss was acceptable to many people as "who cares, just move on", the two
authors of actual code for the two proposals here also came to an agreement on a way forward, so its not like it was a
"coin toss to overrule everyone on 'the other side'".
On 4/8/21 10:30, Andrew Poelstra via bitcoin-dev wrote:
> On Thu, Apr 08, 2021 at 12:40:42PM +0100, Michael Folkson via bitcoin-dev wrote:
>>
>> All of this makes me extremely uncomfortable and I dread to think what
>> individuals and businesses all over the world who have plans to
>> utilize and build on Taproot are making of all of this. As an
>> individual I would like to distance myself from this circus. I will
>> try to keep the mailing list informed though of further developments
>> re Speedy Trial in Core or progress on an alternative client.
>>
>
> Thank you for your updates.
>
>
> For what it's worth, as somebody who wants to use Taproot I don't care *at
> all* about activation parameters, and I especially don't care about block
> height vs MTP.
>
> If a coin toss is what it takes for people to move past this that's fine
> by me.
>
>
>
>
next prev parent reply other threads:[~2021-04-08 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 11:40 Michael Folkson
2021-04-08 14:30 ` Andrew Poelstra
2021-04-08 15:18 ` Matt Corallo [this message]
2021-04-08 21:56 ` David A. Harding
2021-04-09 11:19 ` Michael Folkson
2021-04-10 12:07 ` 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=125be010-93b9-f7dd-70d4-81a63a603621@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=apoelstra@wpsoftware$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@gmail$(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