From: gb <kiwigb@yahoo.com>
To: Jeff Garzik <jgarzik@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] The increase of max block size should be determined by block height instead of block time
Date: Sat, 19 Dec 2015 09:58:42 +1300 [thread overview]
Message-ID: <1450472322.15256.7.camel@yahoo.com> (raw)
In-Reply-To: <CADm_Wcah3V7yxCpt97rK89_0GY8HZm6xbCg0yqjKRWak7crt5Q@mail.gmail.com>
On Fri, 2015-12-18 at 15:15 -0500, Jeff Garzik via bitcoin-dev wrote:
> My preference is height activation + one step per block (i.e. also
> height). Height seems KISS.
>
>
Under this scheme the size of the step-per-block increase could be
decreased every 210,000 blocks (at time of reward halvings).
So, a linear growth rate that decreases every ~4 years, ultimately
grandfathering max_block_size increases on the same block-schedule that
reward decreases.
next prev parent reply other threads:[~2015-12-18 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 19:17 [bitcoin-dev] The increase of max block size should be determined by block height instead of block time Chun Wang
2015-12-18 19:52 ` Jorge Timón
2015-12-18 20:02 ` Jeff Garzik
2015-12-18 20:10 ` Jorge Timón
2015-12-18 20:15 ` Jeff Garzik
2015-12-18 20:20 ` Jorge Timón
2015-12-18 20:58 ` gb [this message]
2015-12-18 20:43 ` Peter Todd
2015-12-18 22:58 ` Jorge Timón
2015-12-19 18:20 ` Peter Todd
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=1450472322.15256.7.camel@yahoo.com \
--to=kiwigb@yahoo.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jgarzik@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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