Return-Path: <stephencalebmorse@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id A1148273
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 21:05:00 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yh0-f45.google.com (mail-yh0-f45.google.com
	[209.85.213.45])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 32897118
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 21:05:00 +0000 (UTC)
Received: by yhan67 with SMTP id n67so107211986yha.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 14:04:59 -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:to
	:cc:content-type;
	bh=EB8ED/efuj5TzhKGQoic/J5rGQD5paGZUp6Q8HUwDVw=;
	b=t00GHC1k8bLH9OxBz+sZv5GTVMBaHwHrv6DG4GbXAmddljJ6O3AiHE+pOIqrhvt76g
	16JQTn912tP5/rxDlB/pu7t/rMr/7ygPsiDqWeY95tO36Vakd6Rfzk4Ywv48JeFCRNAd
	QcljMFrdXtuui/UienRFhyFCYzDInbloXGpJ3aqOVH8yy/JcfkxK6uYbb0b/KjAQfOy1
	J1jntgj4hVLGO0Kq4PmHxYzFLobPcPpwZHwq7xRUA8Qv/7va39OZQ/wSo6p056soFwLz
	Gh9PjallU+a7BOC+NAJ1aNSpoeE6+NL5iSCfdMf7fAYz7lgQk8ub33sCIwbxhhfjXYDi
	U9VA==
MIME-Version: 1.0
X-Received: by 10.129.102.9 with SMTP id a9mr30409786ywc.19.1435007099359;
	Mon, 22 Jun 2015 14:04:59 -0700 (PDT)
Received: by 10.37.203.13 with HTTP; Mon, 22 Jun 2015 14:04:59 -0700 (PDT)
In-Reply-To: <20150622205420.GA8892@savin.petertodd.org>
References: <dd09d1e5-57fb-46ef-8bc0-0fdccf9e7abb@me.com>
	<20150622205420.GA8892@savin.petertodd.org>
Date: Mon, 22 Jun 2015 17:04:59 -0400
Message-ID: <CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmail.com>
From: Stephen Morse <stephencalebmorse@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=001a114904e86855c7051921a083
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jun 2015 21:05:00 -0000

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

> In the nVersion bits proposal that I co-authored we solved that issue by
> comparing the timestamp against the median time, which is guaranteed by
> the protocol rules to monotonically advance.
>

I'm also a fan of using the median time to ensure that there is a clear
point where the protocol change starts. Something like "blocks only allow
the larger block size if the associate pindex has pindex->GetMedianTimePast()
after midnight 11 Jan 2016 and where a supermajority showing support for
the fork has previously been reached".

--001a114904e86855c7051921a083
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"><br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D""><div class=3D"h5"><span style=3D"color:rgb=
(34,34,34)">In the nVersion bits proposal that I co-authored we solved that=
 issue by</span><br></div></div>
comparing the timestamp against the median time, which is guaranteed by<br>
the protocol rules to monotonically advance.<br></blockquote><div><br></div=
><div>I&#39;m also a fan of using the median time to ensure that there is a=
 clear point where the protocol change starts. Something like &quot;blocks =
only allow the larger block size if the associate=C2=A0<font face=3D"monosp=
ace, monospace">pindex</font>=C2=A0has=C2=A0<font face=3D"monospace, monosp=
ace">pindex-&gt;GetMedianTimePast(</font>) after=C2=A0midnight 11 Jan 2016 =
and where a supermajority showing support for the fork has previously been =
reached&quot;.=C2=A0</div></div></div></div>

--001a114904e86855c7051921a083--