From: Ryan Grant <bitcoin-dev@rgrant•org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Exploring alternative activation mechanisms: decreasing threshold
Date: Fri, 26 Feb 2021 17:48:33 +0000 [thread overview]
Message-ID: <CAMnpzfo0X4d9vuVJGxMf9f=yxr8gT_zUZ+d+_X0Dtv7ADTwCnQ@mail.gmail.com> (raw)
In-Reply-To: <bc69d684-3d6e-624e-a859-c2ef8ad5cb13@posteo.net>
Huh.
I like the mechanism.
I like the honesty that once a feature with high demand and safety is
ready, activation pressure will keep increasing.
The gradual march of time in this Decreasing Threshold proposal is
predictable and incremental in ways that help avoid brinkmanship.
Avoiding the hard fork dynamic (that LOT=true requires) prevents some
chain splits, but activation under political opposition may then still
depend on a UASF. If I thought the time had come to line up a UASF
for a feature, I'd first want to have nodes out there running this
softer Decreasing Threshold activation (maybe before it fails).
It's also not as unresponsive to miner wisdom as LOT=true.
Conceptually, it asks miners to arbitrate both version adoption as
well as whether nodes which haven't upgraded face risks in an early
activation. Should miners find themselves in dramatic unanimity, they
even have enough influence to technically fail any activation.
next prev parent reply other threads:[~2021-02-26 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 22:33 Gregorio Guidi
2021-02-26 17:48 ` Ryan Grant [this message]
2021-02-27 17:55 ` Luke Dashjr
2021-02-27 23:49 ` Gregorio Guidi
2021-02-28 2:38 ` Matt Corallo
2021-02-28 14:06 ` Ryan Grant
2021-03-01 14:33 ` Anthony Towns
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='CAMnpzfo0X4d9vuVJGxMf9f=yxr8gT_zUZ+d+_X0Dtv7ADTwCnQ@mail.gmail.com' \
--to=bitcoin-dev@rgrant$(echo .)org \
--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