MIME-version: 1.0
Content-type: multipart/alternative;
	boundary="Boundary_(ID_8x5MvtbAqGGKg2SFMMv0lw)"
To: Gavin Andresen <gavinandresen@gmail.com>
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Date: Mon, 22 Jun 2015 19:32:22 +0000 (GMT)
Message-id: <dd09d1e5-57fb-46ef-8bc0-0fdccf9e7abb@me.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev]
 =?utf-8?q?Draft_BIP_=3A_fixed-schedule_block_size_i?=
 =?utf-8?q?ncrease?=
Precedence: list


--Boundary_(ID_8x5MvtbAqGGKg2SFMMv0lw)
Content-type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: quoted-printable

=0A=0AOn Jun 22, 2015, at 11:18 AM, Gavin Andresen <gavinandresen@gmail.co=
m> wrote:=0A=0AThe maximum size shall be 8,000,000 bytes at a timestamp of=
 2016-01-11 00:00:00 UTC (timestamp 1452470400), and shall double every 63=
,072,000 seconds (two years, ignoring leap years), until 2036-01-06 00:00:=
00 UTC (timestamp 2083190400). The maximum size of blocks in between doubl=
ings will increase linearly based on the block's timestamp. The maximum si=
ze of blocks after 2036-01-06 00:00:00 UTC shall be 8,192,000,000 bytes.=0A=
=C2=A0=0ASince it's possible that block timestamps aren't chronological in=
 order, what would happen if a block following a size increase trigger is =
back in the past before the size increase? Would that block have a lower s=
ize restriction again? Would using block height not be a more stable numbe=
r to work with?=0A=0Ajp=

--Boundary_(ID_8x5MvtbAqGGKg2SFMMv0lw)
Content-type: multipart/related;
 boundary="Boundary_(ID_Q5j7gjd7Zgy+cPAiPTmiyA)"; type="text/html"


--Boundary_(ID_Q5j7gjd7Zgy+cPAiPTmiyA)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><body><div><br></div><div><br>On Jun 22, 2015, at 11:18 AM, Gavin Andresen &lt;g=
avinandresen@gmail.com&gt; wrote:<br></div><div><blockquote type=3D"cite">=
<div class=3D"msg-quote"><div dir=3D"ltr"><div><div class=3D"gmail_extra">=
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The maximu=
m size shall be 8,000,000 bytes at a timestamp of 2016-01-11 00:00:00 UTC =
(timestamp 1452470400), and shall double every 63,072,000 seconds (two yea=
rs, ignoring leap years), until 2036-01-06 00:00:00 UTC (timestamp 2083190=
400). The maximum size of blocks in between doublings will increase linear=
ly based on the block's timestamp. The maximum size of blocks after 2036-0=
1-06 00:00:00 UTC shall be 8,192,000,000 bytes.</div><div class=3D"gmail_e=
xtra"></div></div></div></div></div></blockquote><span>&nbsp;</span></div>=
<div><span>Since it's possible that block timestamps aren't chronological =
in order, what would happen if a block following a size increase trigger i=
s back in the past before the size increase? Would that block have a lower=
 size restriction again? Would using block height not be a more stable num=
ber to work with?</span></div><div><span><br></span></div><div><span>jp</s=
pan></div></body></html>=

--Boundary_(ID_Q5j7gjd7Zgy+cPAiPTmiyA)--

--Boundary_(ID_8x5MvtbAqGGKg2SFMMv0lw)--