Ryan Grant [ARCHIVE] on Nostr: 📅 Original date posted:2021-02-28 📝 Original message:On Sat, Feb 27, 2021 at ...
📅 Original date posted:2021-02-28
📝 Original message:On Sat, Feb 27, 2021 at 5:55 PM Luke Dashjr via bitcoin-dev
<bitcoin-dev at 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.
📝 Original message:On Sat, Feb 27, 2021 at 5:55 PM Luke Dashjr via bitcoin-dev
<bitcoin-dev at 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.