Luke's proposed changes to BIP8 (specifically, the FAILING state)
seem designed to address the regression compared to BIP9 that there is
no way to avoid activating a softfork that is shown to be suboptimal or
flawed in some (serious enough) way - after deployment is well underway -
without hardforking.
I agree with your
principle but we should also look at the circumstances in which this
mechanism would be beneficial vs. when it would cause harm (compared to
BIP8 without this mechanism). The scenario this was designed for is
"miners refusing to activate, on non-technical grounds, a widely desired
upgrade" - in which case the "wakeup call" would be in users' hands,
not anyone in particular.
Is there a
hypothetical scenario in which the orphan risk outweighs the benefits of
having this kind of upgrade mechanism that can (at deploy-time) be
chosen to be optional by default with a deferred mechanism to make it
mandatory? If so, is there any thought on how to realize the latter
without the former?
-------- Original Message --------
Subject: Re: [bitcoin-dev] Height based vs block time based thresholds
Local Time: July 5, 2017 8:06 AM
UTC Time: July 5, 2017 8:06 AM
From: bitcoin-dev@lists.linuxfoundation.org
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
On Wed, Jul 5, 2017 at 3:50 AM, Luke Dashjr via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> I"ve already opened a PR almost 2 weeks ago to do this and fix the other
> issues BIP 9 has. https://github.com/bitcoin/bips/pull/550
>
> It just needs your ACK to merge.
These proposals for gratuitous orphaning are reckless and coersive.
We have a professional obligation to first do no harm, and amplifying
orphaning which can otherwise easily be avoided violates it.
It is not anyones position to decide who does and doesn"t need to be
"woken up" with avoidable finical harm, nor is it any of our right to
do so at the risk of monetary losses by any and all users users from
the resulting network instability.
It"s one thing to argue that some disruption is strictly needed for
the sake of advancement, it"s another to see yourself fit as judge,
jury, and executioner to any that does not jump at your command.
(which is exactly the tone I and at least some others extract from
your advocacy of these changes and similar activity around BIP148).
I for one oppose those changes strongly.
> Not having a mandatory signal turned out to be a serious bug in BIP 9,
I have seen no evidence or case for this.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev