From: Chun Wang <1240902@gmail.com>
To: John Sacco <johnsock@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP - Block size doubles at each reward halving with max block size of 32M
Date: Fri, 13 Nov 2015 10:56:55 +0800 [thread overview]
Message-ID: <CAFzgq-xmXcEKN0_0e8de0UDOJEXuivbz986-dsSC5BCYLA2t1A@mail.gmail.com> (raw)
In-Reply-To: <CAEkt4Xu6vBFtRVEnXCWJa0f9OYi9wLKwToxc3p+KPfMuV5y0GA@mail.gmail.com>
How about these specs:
* 1 MB, height < 210000;
* 2 MB, 210000 <= height < 420000;
* 4 MB, 420000 <= height < 630000;
* 8 MB, 630000 <= height < 840000;
* 16 MB, 840000 <= height < 1050000;
* 32 MB, height >= 1050000.
On Fri, Nov 13, 2015 at 7:47 AM, John Sacco via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi Devs,
>
>
> Please consider the draft proposal below for peer review.
>
>
> Thanks,
>
>
> John
>
>
> BIP
>
> BIP: ?
>
> Title: Block size doubles at each reward halving with max block size of
> 32M
>
> Author: John Sacco <johnsock@gmail.com>
>
> Status: Draft
>
> Type: Standards Track
>
> Created: 2015-11-11
>
> Abstract
>
> Change max block size to 2MB at next block subsidy halving, and double the
> block size at each subsidy halving until reaching 32MB.
>
> Copyright
>
> This proposal belongs in the public domain. Anyone can use this text for any
> purpose with proper attribution to the author.
>
> Motivation
>
> 1. Gradually restores block size to the default 32 MB setting originally
> implemented by Satoshi.
>
> 2. Initial increase to 2MB at block halving in July 2016 would have
> minimal impact to existing nodes running on most hardware and networks.
>
> 3. Long term solution that does not make enthusiastic assumptions
> regarding future bandwidth and storage availability estimates.
>
> 4. Maximum block size of 32MB allows peak usage of ~100 tx/sec by year
> 2031.
>
> 5. Exercise network upgrade procedure during subsidy reward halving, a
> milestone event with the goal of increasing awareness among miners and node
> operators.
>
> Specification
>
> 1. Increase the maximum block size to 2MB when block 630,000 is reached
> and 75% of the last 1,000 blocks have signaled support.
>
> 2. Increase maximum block size to 4MB at block 840,000.
>
> 3. Increase maximum block size to 8MB at block 1,050,000.
>
> 4. Increase maximum block size to 16MB at block 1,260,000.
>
> 5. Increase maximum block size to 32MB at block 1,470,000.
>
> Backward compatibility
>
> All older clients are not compatible with this change. The first block
> larger than 1M will create a network partition excluding not-upgraded
> network nodes and miners.
>
> Rationale
>
> While more comprehensive solutions are developed, an increase to the block
> size is needed to continue network growth. A longer term solution is needed
> to prevent complications associated with additional hard forks. It should
> also increase at a gradual rate that retains and allows a large distribution
> of full nodes. Scheduling this hard fork to occur no earlier than the
> subsidy halving in 2016 has the goal of simplifying the communication
> outreach needed to achieve consensus, while also providing a buffer of time
> to make necessary preparations.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
next prev parent reply other threads:[~2015-11-13 2:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 23:47 [bitcoin-dev] BIP - Block size doubles at each reward halving with max block size of 32M John Sacco
2015-11-13 2:56 ` Chun Wang [this message]
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
[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=CAFzgq-xmXcEKN0_0e8de0UDOJEXuivbz986-dsSC5BCYLA2t1A@mail.gmail.com \
--to=1240902@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=johnsock@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