From: Matt Corallo <lf-lists@mattcorallo•com>
To: "David A. Harding" <dave@dtrt•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot activation proposal "Speedy Trial"
Date: Sat, 6 Mar 2021 16:48:45 -0500 [thread overview]
Message-ID: <a76b9eee-0015-105c-2c8d-6131a91e95e3@mattcorallo.com> (raw)
In-Reply-To: <20210306202350.qdcpvxgedn6qhuxa@ganymede>
I don't think anyone is proposing anything to "prevent" other people from doing anything they wish. My understanding of
the goal of this proposal, itself, was to keep the community together by proposing a solution that was palatable to all.
My point was that I'm not sure that this proposal achieves its own goal, and that there may be solutions which are even
more likely to keep the community of nodes together.
Matt
On 3/6/21 15:23, David A. Harding wrote:
> On Sat, Mar 06, 2021 at 01:11:01PM -0500, Matt Corallo wrote:
>> I'm really unsure that three months is a short enough time window that there
>> wouldn't be a material effort to split the network with divergent consensus
>> rules.
>
> I oppose designing activation mechanisms with the goal of preventing
> other people from effectively exercising self determination over what
> consensus rules their nodes enforce.
>
> Three months was chosen because it's long enough to give miners a
> reasonable enough amount of time to activate taproot but it's also short
> enough that it doesn't delay any of the existing proposals with roughly
> one-year timelines. As such, I think it has the potential to gain
> acceptance from multiple current factions (even if it doesn't ever gain
> their full approval), allowing us to move forward with rough social
> consensus and to gain useful information from the attempt that can
> inform future decisions.
>
> -Dave
>
next prev parent reply other threads:[~2021-03-06 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 3:43 David A. Harding
2021-03-06 4:44 ` Jeremy
2021-03-06 6:04 ` Andrew Chow
2021-03-06 14:44 ` Russell O'Connor
2021-03-15 2:51 ` Luke Dashjr
2021-03-15 3:14 ` Andrew Chow
2021-03-06 9:29 ` Anthony Towns
2021-03-06 10:26 ` Eric Voskuil
2021-03-06 18:11 ` Matt Corallo
2021-03-06 20:23 ` David A. Harding
2021-03-06 21:48 ` Matt Corallo [this message]
2021-03-06 20:44 ` Ariel Luaces
2021-03-06 20:55 ` Keagan McClelland
2021-03-06 19:56 Michael Folkson
2021-03-06 21:55 ` Matt Corallo
2021-03-15 14:06 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=a76b9eee-0015-105c-2c8d-6131a91e95e3@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dave@dtrt$(echo .)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