From: Zac Greenwood <zachgrw@gmail•com>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Michael Folkson <michaelfolkson@protonmail•com>
Subject: Re: [bitcoin-dev] 7 Theses on a next step for BIP-119
Date: Thu, 21 Apr 2022 14:49:19 +0200 [thread overview]
Message-ID: <CAJ4-pEAsyeqq0wM7dJgbBb-RLKbgWpzuLikrBFBBMtz2zm4aCA@mail.gmail.com> (raw)
In-Reply-To: <uUzpB7Sapu5q3qxF7voLmwRIJfLPGCwcelhFVR8BClM7HBi9n86zj1A6SeYBdKZXOGL-8C049G1mEURDkyNMhksyPMfjIMPJXHoidOydAT8=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Wed, 20 Apr 2022 at 15:49, Michael Folkson via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
Assuming 90 percent of miners don't signal for it in one of the Speedy
> Trial windows then the activation attempt will have failed and it will be
> back in Jeremy's court whether he tries again with a different activation
> attempt.
>
> Assuming 90 percent of miners do signal for it (unlikely in my opinion but
> presumably still a possibility) then the CTV soft fork could activate
> unless full nodes resist it.
>
This is wrong. Miners do not have the mandate to decide the faith of
softforks. The MO of softforks is that once a softfork has been merged, it
already has consensus and must be activated by miners eventually. The
various activation methods exist to ensure miners cannot sabotage a
softfork that has consensus.
The way you phrase it, makes it sound like miners have any say over
softforks. This is not the case.
Zac
>
[-- Attachment #2: Type: text/html, Size: 2003 bytes --]
next prev parent reply other threads:[~2022-04-21 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:31 Jeremy Rubin
2022-04-20 13:24 ` Michael Folkson
2022-04-20 17:13 ` Robin Linus
2022-04-20 18:19 ` Michael Folkson
2022-04-20 19:46 ` Robin Linus
2022-04-20 22:04 ` Michael Folkson
2022-04-21 9:05 ` Robin Linus
2022-04-21 4:03 ` Billy Tetrud
2022-04-21 12:49 ` Zac Greenwood [this message]
2022-04-21 13:40 ` alicexbt
2022-04-21 14:16 ` Greg Sanders
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=CAJ4-pEAsyeqq0wM7dJgbBb-RLKbgWpzuLikrBFBBMtz2zm4aCA@mail.gmail.com \
--to=zachgrw@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@protonmail$(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