Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5DF968CC for ; Tue, 28 Mar 2017 20:46:16 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx-out02.mykolab.com (mx.kolabnow.com [95.128.36.1]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A2A5712A for ; Tue, 28 Mar 2017 20:46:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at kolabnow.com X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101]) by mx-out02.mykolab.com (Postfix) with ESMTPS id DC38561765; Tue, 28 Mar 2017 22:46:12 +0200 (CEST) From: Tom Zander To: bitcoin-dev@lists.linuxfoundation.org, Wang Chun <1240902@gmail.com> Date: Tue, 28 Mar 2017 22:48:44 +0200 Message-ID: <1610530.cSCeZjVRYh@cherry> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 28 Mar 2017 20:49:04 +0000 Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 20:46:16 -0000 On Tuesday, 28 March 2017 18:59:32 CEST Wang Chun via bitcoin-dev wrote: > Despite spam tx on the network, the block capacity is approaching its > limit, and we must think ahead. Shall we code a patch right now, to > remove the block size limit of 1MB, but not activate it until far in > the future. I would propose to remove the 1MB limit at the next block > halving in spring 2020, only limit the block size to 32MiB which is > the maximum size the current p2p protocol allows. This patch must be > in the immediate next release of Bitcoin Core. ... > We don't yet have an agreement on how to increase the block size > limit. There have been many proposals over the past years, like > BIP100, 101, 102, 103, 104, 105, 106, 107, 109, 148, 248, BU, and so > on. These hard fork proposals, with this patch already in Core's > release, they all become soft fork. I think that is a very smart idea, thank you for making it. -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel