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 A1148273 for ; 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 ; Mon, 22 Jun 2015 21:05:00 +0000 (UTC) Received: by yhan67 with SMTP id n67so107211986yha.3 for ; 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: <20150622205420.GA8892@savin.petertodd.org> Date: Mon, 22 Jun 2015 17:04:59 -0400 Message-ID: From: Stephen Morse To: Peter Todd 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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

=
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=C2=A0pindex=C2=A0has=C2=A0pindex->GetMedianTimePast() after=C2=A0midnight 11 Jan 2016 = and where a supermajority showing support for the fork has previously been = reached".=C2=A0
--001a114904e86855c7051921a083--