From: Gregory Maxwell <greg@xiph•org>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Height based vs block time based thresholds
Date: Wed, 5 Jul 2017 08:06:33 +0000 [thread overview]
Message-ID: <CAAS2fgTko+aszOReFX5Svo4h-qROzdU9+vZLSDoR97do6YJ_cQ@mail.gmail.com> (raw)
In-Reply-To: <201707050350.53122.luke@dashjr.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.
next prev parent reply other threads:[~2017-07-05 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 1:30 shaolinfry
2017-07-05 2:25 ` Troy Benjegerdes
2017-07-05 3:39 ` Bram Cohen
2017-07-05 3:50 ` Luke Dashjr
2017-07-05 4:00 ` shaolinfry
2017-07-05 4:10 ` Luke Dashjr
2017-07-05 19:44 ` Hampus Sjöberg
2017-07-06 17:20 ` Jorge Timón
2017-07-06 17:41 ` Eric Voskuil
2017-07-05 8:06 ` Gregory Maxwell [this message]
2017-07-05 8:54 ` Kekcoin
2017-07-06 20:43 ` Luke Dashjr
2017-07-07 5:52 ` shaolinfry
2017-07-07 9:51 ` Jorge Timón
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=CAAS2fgTko+aszOReFX5Svo4h-qROzdU9+vZLSDoR97do6YJ_cQ@mail.gmail.com \
--to=greg@xiph$(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