From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, "Jorge Timón" <jtimon@jtimon•cc>
Cc: John Sacco <johnsock@gmail•com>
Subject: Re: [bitcoin-dev] BIP - Block size doubles at each reward halving with max block size of 32M
Date: Sat, 14 Nov 2015 21:11:22 +0000 [thread overview]
Message-ID: <201511142111.24046.luke@dashjr.org> (raw)
In-Reply-To: <CABm2gDo7D1rrsjRef173HVkwBrDQ0uJAhtWKk0SmRFaqzX5VTw@mail.gmail.com>
On Saturday, November 14, 2015 10:52:12 AM Jorge Timón via bitcoin-dev wrote:
> Currently bip99 recommends 95% miner upgrade confirmation with version bits
> (bip9) for uncontroversial hardforks just like it does for uncontroversial
> softforks. It is true that in the case of hardforks miners don't decide and
> it's the whole economy who has to upgrade before activation, but "the whole
> economy" and "all users" includes miners, so why not use the only upgrade
> confirmation mechanism that we have available?
Actually, the economy does not necessarily include miners, and in fact the
present miner community for the most part does not overlap significantly with
economic activity. And at the same time, miners also have a tendency to
upgrade at a different rate than the economy. It might make sense to
incorporate a miner-trigger, but *only if* the flag is enabled in nodes by an
option disabled by default, and the BIP clearly specifies that miners must not
enable it until they perceive complete economic adoption of the change.
Luke
next prev parent reply other threads:[~2015-11-14 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 23:47 John Sacco
2015-11-13 2:56 ` Chun Wang
2015-11-13 3:37 ` John Sacco
2015-11-13 7:49 ` Btc Drak
2015-11-13 9:50 ` John Sacco
2015-11-13 10:52 ` Luke Dashjr
[not found] ` <1447430469019.e0ee1956@Nodemailer>
2015-11-13 22:28 ` Luke Dashjr
2015-11-14 0:02 ` digitsu
2015-11-14 9:31 ` Adam Back
2015-11-14 10:52 ` Jorge Timón
2015-11-14 21:11 ` Luke Dashjr [this message]
[not found] ` <CADZB0_Z3Kf4GW0VATjb10kJF0aFgyFOcqX_=y+LFoUpsi+TRUA@mail.gmail.com>
2015-11-14 21:27 ` Luke Dashjr
2015-11-15 12:16 ` Jorge Timón
[not found] ` <CABEog-XUNt9kDS7Mc0XYFjm5ePUT0m1YaAoG9VypTCiGLBongQ@mail.gmail.com>
2015-11-18 10:15 ` Jorge Timón
2015-11-13 6:39 ` Luke Dashjr
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=201511142111.24046.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=johnsock@gmail$(echo .)com \
--cc=jtimon@jtimon$(echo .)cc \
/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