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 94F80273 for ; Mon, 22 Jun 2015 19:28:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 13F8A17D for ; Mon, 22 Jun 2015 19:28:50 +0000 (UTC) Received: by qcji3 with SMTP id i3so10358216qcj.1 for ; Mon, 22 Jun 2015 12:28:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=R8B+wuTvvAS8/TxX87gxK+Mick5O6JtXES4FnhszHDk=; b=MbB0Bhp1Zi4ma76TcmSD/hkjt8Q8dOP58CTCtYgTACeT6j1ohmj4cMz8mQOh8Ia+Fj FyBiQpUVbCEduWgn7WXHmEwMdpf1LWvrMwis5blnl8daGi1iybhCrN3cM/7RPyyJVO+H uk4QVgMMNVt/uQmmpNuacbXcLL0+mrUqIrHwWlaVfSSabtVEIXWK/+5P3WAVdpDsb/2a PVEv8vCGuEt6CFK2YzZKZun8tYZQlFOTFmr2vwWGvlKdtmfxt19B1GbIN9ZzNRBEEj4F 9nircmP3bFhRYdKhW+gjbEb0kJm/l7YdntiMWbrA8XJwnMhi8PBJFo/uNlInAlj8SnGq PmJA== MIME-Version: 1.0 X-Received: by 10.140.216.208 with SMTP id m199mr41735962qhb.69.1435001329336; Mon, 22 Jun 2015 12:28:49 -0700 (PDT) Received: by 10.140.85.241 with HTTP; Mon, 22 Jun 2015 12:28:49 -0700 (PDT) In-Reply-To: <55885DB0.9040709@gmail.com> References: <55885DB0.9040709@gmail.com> Date: Mon, 22 Jun 2015 20:28:49 +0100 Message-ID: From: Tier Nolan Cc: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary=001a1135d7967cc98b051920480b X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MISSING_HEADERS, 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 Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase 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: Mon, 22 Jun 2015 19:28:50 -0000 --001a1135d7967cc98b051920480b Content-Type: text/plain; charset=UTF-8 On Mon, Jun 22, 2015 at 8:10 PM, Martin Schwarz wrote: > Gavin, > > in 2022 your proposal (BIP as well as code) crosses the 32MB maximum > message size limit. In order to avoid deployment of code that > deterministically > fails fatally in 2022, I'd propose to stop the doublings at 32MB for now > and fix > the message size limit in the mean time. There is an exception in the code for "block" messages. https://github.com/gavinandresen/bitcoinxt/commit/c81898ec46e4962daf975e352931b848026fdc34#diff-7ec3c68a81efff79b6ca22ac1f1eabbaR3548 This means 2MB limit for all other messages. "block" messages are limited to the max block size for 2 hours into the future. I think setting it to a week into the future might be better, since it is only a DOS protection. This would guarantee that message sizes are reasonable. The size check would still be done anyway. --001a1135d7967cc98b051920480b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jun 22, 2015 at 8:10 PM, Martin Schwarz <martin.schwarz@gmail= .com> wrote:
Gavin,

in 2022 your proposal (BIP as well as code) crosses the 32MB maximum
message size limit. In order to avoid deployment of code that deterministic= ally
fails fatally in 2022, I'd propose to stop the doublings at 32MB for no= w and fix
the message size limit in the mean time.

Th= ere is an exception in the code for "block" messages.=C2=A0
<= /div>
This means 2MB limit for all other messages.=C2=A0 "bl= ock" messages are limited to the max block size for 2 hours into the f= uture.

I think setting it to a week into the future might= be better, since it is only a DOS protection.=C2=A0 This would guarantee t= hat message sizes are reasonable.=C2=A0 The size check would still be done = anyway.
--001a1135d7967cc98b051920480b--