From: Ryan Grant <bitcoin-dev@rgrant.org>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
Luke Dashjr <luke@dashjr.org>
Subject: Re: [bitcoin-dev] Exploring alternative activation mechanisms: decreasing threshold
Date: Sun, 28 Feb 2021 14:06:42 +0000 [thread overview]
Message-ID: <CAMnpzfpDbskd70z0fKk-_FVCM-A1qYVVCQbRVM=1KOv63RrJrQ@mail.gmail.com> (raw)
In-Reply-To: <202102271755.02271.luke@dashjr.org>
On Sat, Feb 27, 2021 at 5:55 PM Luke Dashjr via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> This has the same problems BIP149 did: since there is no signalling, it is
> ambiguous whether the softfork has activated at all.
You only need to see one block in the heaviest valid chain to dissolve
that ambiguity. There are a lot of volunteers in this space who would
(collectively) commit a few block's worth of hashrate, to know.
> Additionally, it loses the flexibility of BIP 8 to, after the initial
> deployment, move the timeoutheight sooner.
It doesn't interfere with concurrent UASFs using any combination of
timeoutheights.
next prev parent reply other threads:[~2021-02-28 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 22:33 [bitcoin-dev] Exploring alternative activation mechanisms: decreasing threshold Gregorio Guidi
2021-02-26 17:48 ` Ryan Grant
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 [this message]
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='CAMnpzfpDbskd70z0fKk-_FVCM-A1qYVVCQbRVM=1KOv63RrJrQ@mail.gmail.com' \
--to=bitcoin-dev@rgrant.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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