From: joe2015@openmailbox•org
To: Jeff Garzik <jgarzik@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Mon, 21 Dec 2015 11:58:50 +0800 [thread overview]
Message-ID: <489826397e6b36bf68391508952042f4@openmailbox.org> (raw)
In-Reply-To: <CADm_WcYXU6VXG034j=mD8zkmqNLB96sjvBc6qo8Sx2NepHJk8A@mail.gmail.com>
On 2015-12-21 11:39, Jeff Garzik wrote:
> On Sun, Dec 20, 2015 at 12:21 PM, joe2015--- via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Current hard fork implementations include / will include miner
> lock-in, just like any soft fork. They will not activate if global
> consensus is not reached.
That's not true at all. They activate with a miner majority (e.g. 75%,
95%, etc.), not global consensus. Here global really means global, i.e.
miner, economic, all clients, etc. In the case of a hardfork there is
nothing stopping the miner minority from continuing the old chain. With
a softfork the miner minority is forced to upgrade otherwise their
blocks will be eventually orphaned.
My proposal achieves a hardfork-like blocksize limit increase but, like
a softfork, also forces the miner minority to upgrade.
--joe.
next prev parent reply other threads:[~2015-12-21 3:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 17:21 joe2015
2015-12-21 3:39 ` Jeff Garzik
2015-12-21 3:58 ` joe2015 [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-20 10:56 joe2015
2015-12-20 15:22 ` joe2015
2015-12-20 15:50 ` Tier Nolan
2015-12-20 18:17 ` Bryan Bishop
2015-12-21 3:04 ` joe2015
2015-12-21 4:23 ` jl2012
2015-12-21 4:41 ` joe2015
2015-12-30 19:00 ` Bob McElrath
2015-12-30 23:49 ` Jonathan Toomim
2015-12-30 23:56 ` Jonathan Toomim
2015-12-31 0:04 ` Bob McElrath
2015-12-31 4:39 ` joe2015
2015-12-31 10:39 ` David Chan
2015-12-31 11:32 ` joe2015
2016-01-04 21:53 ` 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=489826397e6b36bf68391508952042f4@openmailbox.org \
--to=joe2015@openmailbox$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jgarzik@gmail$(echo .)com \
/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