From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9D9FFFDD for ; Fri, 5 Feb 2016 23:04:29 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1570E195 for ; Fri, 5 Feb 2016 23:04:29 +0000 (UTC) Received: by mail-qg0-f53.google.com with SMTP id u30so80245135qge.1 for ; Fri, 05 Feb 2016 15:04:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8Z0GpEcmNUHnN+WjYt9fgjyJ+dT1mqDHEt/DEu+jHu8=; b=0gYVvfwOZhSPkW2dbzs9cBGjm3HN1vQX7P+p8RSG1REaQIESjTgoTacw9y02a8qlOw 8rHOyZEPgtuI63GXv3tWVBE/7GGQtZyMKYBhwQevYDkCnVmJ0zoBbHe4iwWDuCLzBCcQ 4TiOfd/rw3VjcFhmWnfdMkiNoF4m3YCnMNloSKKbh+Ws8OPEWf44QJVQq1EHuZy1iC3N BF+jnihWpHTMFl7wh3jSc/n09L+ai8ZD0NgCbn5aFLgFH3DN46Qo6Twe3f/6RQbmQwbi UcVfAvgi3KgF2AD5icrxhrY/5bT5sxgseNxf6dfdjNdGx6sbOSjYK5yKYfMMEf1AYsfJ FPhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=8Z0GpEcmNUHnN+WjYt9fgjyJ+dT1mqDHEt/DEu+jHu8=; b=P+iVdfE5cwCC75BIIPc3JOfmOBIkIsGdfyedSoz0XSwUxYvzovHCrjGN9Dz32xfX1I 0ECjapts6C5ncBN+mpl12ACbtZCrbce9b1073DPIRCIjcQOjNXjuxXnyHw/L0rKrQZe8 xA6FRMqv96977corGlseh6zJwTbVo+VVtoVbwW/jnnY6okE2sUfewL3ARhoOKBycQaT5 UvU3xmHC7fVsAXrtzS5utKxxbHyuTjGn9ux0DoK+a8BF16f0wT7+3+DOalDwaBaIuRMy eY1MMy1ZJB5HYg8cBuMVmctXvY5cnjazwgDgQWLyLvOOMOeunZYUyqXffj6+rFC+XgiB Mxlg== X-Gm-Message-State: AG10YORnbvUzyfwrWfZJm0GBZmujs+dblIbwDMPLUXnTpZ9bWdZ+Wz9FqPbWTpR4FZg8SVfuno+MyfdJvMbjWQ== X-Received: by 10.141.6.130 with SMTP id i124mr20931293qhd.90.1454713468380; Fri, 05 Feb 2016 15:04:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.65.210 with HTTP; Fri, 5 Feb 2016 15:04:09 -0800 (PST) In-Reply-To: References: From: Btc Drak Date: Fri, 5 Feb 2016 23:04:09 +0000 Message-ID: To: Gavin Andresen Content-Type: multipart/alternative; boundary=001a113a6538886b03052b0ddfd9 X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM, HK_RANDOM_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Fri, 05 Feb 2016 23:14:01 +0000 Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2 megabytes X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 23:04:29 -0000 --001a113a6538886b03052b0ddfd9 Content-Type: text/plain; charset=UTF-8 On Fri, Feb 5, 2016 at 8:51 PM, Gavin Andresen via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > This has been reviewed by merchants, miners and exchanges for a couple of > weeks, and has been implemented and tested as part of the Bitcoin Classic > and Bitcoin XT implementations. > > Constructive feedback welcome; argument about whether or not it is a good > idea to roll out a hard fork now will be unproductive, so I vote we don't > go there. > > Draft BIP: > https://github.com/gavinandresen/bips/blob/bump2mb/bip-bump2mb.mediawiki > > Summary: > Increase block size limit to 2,000,000 bytes. > After 75% hashpower support then 28-day grace period. > With accurate sigop counting, but existing sigop limit (20,000) > And a new, high limit on signature hashing > > Blog post walking through the code: > http://gavinandresen.ninja/a-guided-tour-of-the-2mb-fork > > Blog post on a couple of the constants chosen: > http://gavinandresen.ninja/seventyfive-twentyeight > It's great to finally see a BIP, although seems strange to ask for feedback after releasing binaries. In any case, the issue isn't about "whether or not it is a good idea to roll out a hard fork", the question has always been about how to do safe hard fork deployment and what the technological requirements are for doing so. Your BIP/blogs do not actually address any of this. 75% miner signalling with a 28 day flag day thereafter gives virtually no time for the entire ecosystem to migrate and is widely considered unsafe. It's plainly obvious that an entire ecosystem of 5000 full nodes cannot be prepared in a month. --001a113a6538886b03052b0ddfd9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Feb 5, 2016 at 8:51 PM, Gavin Andresen via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
This has been reviewed by merchants, miners and= exchanges for a couple of weeks, and has been implemented and tested as pa= rt of the Bitcoin Classic and Bitcoin XT implementations.

Constructive feedback welcome; argument about whether or not it is a good= idea to roll out a hard fork now will be unproductive, so I vote we don= 9;t go there.

Draft BIP:

Summary: =C2=A0
=C2=A0 Increase block size limit to 2,000,000 bytes.
=C2=A0 Af= ter 75% hashpower support then 28-day grace period.
=C2=A0 With a= ccurate sigop counting, but existing sigop limit (20,000)
=C2=A0 = And a new, high limit on signature hashing

Blog po= st walking through the code:

It's great to f= inally see a BIP, although seems strange to ask for feedback after releasin= g binaries.

In any case, the issue isn't about "whet= her or not it is a good idea to roll out a hard fork", the question ha= s always been about how to do safe hard fork deployment and what the techno= logical requirements are for doing so. Your BIP/blogs do not actually addre= ss any of this. 75% miner signalling with a 28 day flag day thereafter give= s virtually no time for the entire ecosystem to migrate and is widely consi= dered unsafe. It's plainly obvious that an entire ecosystem of 5000 ful= l nodes cannot be prepared in a month.

--001a113a6538886b03052b0ddfd9--