From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Gregory Maxwell <greg@xiph•org>
Subject: Re: [bitcoin-dev] Height based vs block time based thresholds
Date: Thu, 6 Jul 2017 20:43:28 +0000 [thread overview]
Message-ID: <201707062043.30569.luke@dashjr.org> (raw)
In-Reply-To: <CAAS2fgTko+aszOReFX5Svo4h-qROzdU9+vZLSDoR97do6YJ_cQ@mail.gmail.com>
On Wednesday 05 July 2017 8:06:33 AM Gregory Maxwell via bitcoin-dev wrote:
> 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.
Nothing is "orphaned" unless miners are acting negligently or maliciously.
Incentivising honest behaviour from miners is inherently part of Bitcoin's
design, and these changes are necessary for both that and keeping the network
secure. This doesn't do harm; it reduces risk of harm.
> 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 don't appreciate the uncalled-for character assassination, and it doesn't
belong on this mailing list.
> 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.
Since you apparently have a drastically different opinion on this subject, I
think it may be best to wait until after BIP148 to continue the discussion
(thereby having more real-world information to work from).
Therefore, I have opened a new pull request with just the parts you seem to be
objecting to removed. Please let us know if this version is satisfactory.
https://github.com/bitcoin/bips/pull/551
Luke
next prev parent reply other threads:[~2017-07-06 20:43 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
2017-07-05 8:54 ` Kekcoin
2017-07-06 20:43 ` Luke Dashjr [this message]
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=201707062043.30569.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)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