MIME-Version: 1.0
In-Reply-To: <55885DB0.9040709@gmail.com>
References: <CABsx9T2HegqOBqd1jijk1bZBE6N+NH8x6nfwbaoLBACVf8-WBQ@mail.gmail.com>
	<55885DB0.9040709@gmail.com>
Date: Mon, 22 Jun 2015 20:28:49 +0100
Message-ID: <CAE-z3OWqiGPPNVxBVU0mx+TKFuysKrhXpwg6gOFcwGBQx26VtQ@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a1135d7967cc98b051920480b
Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
Precedence: list

--001a1135d7967cc98b051920480b
Content-Type: text/plain; charset=UTF-8

On Mon, 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
> 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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Jun 22, 2015 at 8:10 PM, Martin Schwarz <span dir=3D"ltr">&lt;<a href=
=3D"mailto:martin.schwarz@gmail.com" target=3D"_blank">martin.schwarz@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">Gavin,<br>
<br>
in 2022 your proposal (BIP as well as code) crosses the 32MB maximum<br>
message size limit. In order to avoid deployment of code that deterministic=
ally<br>
fails fatally in 2022, I&#39;d propose to stop the doublings at 32MB for no=
w and fix<br>
the message size limit in the mean time.</blockquote><div><br></div><div>Th=
ere is an exception in the code for &quot;block&quot; messages.=C2=A0 <br><=
/div><div><br><a href=3D"https://github.com/gavinandresen/bitcoinxt/commit/=
c81898ec46e4962daf975e352931b848026fdc34#diff-7ec3c68a81efff79b6ca22ac1f1ea=
bbaR3548">https://github.com/gavinandresen/bitcoinxt/commit/c81898ec46e4962=
daf975e352931b848026fdc34#diff-7ec3c68a81efff79b6ca22ac1f1eabbaR3548</a><br=
><br></div><div>This means 2MB limit for all other messages.=C2=A0 &quot;bl=
ock&quot; messages are limited to the max block size for 2 hours into the f=
uture.<br><br></div><div>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.<br></div></div></div></div>

--001a1135d7967cc98b051920480b--