To: bitcoin-dev@lists.linuxfoundation.org
References: <dd09d1e5-57fb-46ef-8bc0-0fdccf9e7abb@me.com>
	<20150622205420.GA8892@savin.petertodd.org>
	<CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmail.com>
From: Ross Nicoll <jrn@jrn.me.uk>
Message-ID: <55887EDF.3070505@jrn.me.uk>
Date: Mon, 22 Jun 2015 22:32:15 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
	Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------070401020302090605090002"
Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
Precedence: list

This is a multi-part message in MIME format.
--------------070401020302090605090002
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Potentially daft question, why not use a minimum height? Yes, it's 
imprecise, but over an extended period of time they're good enough IMHO.

I'd have to do more careful calculations to confirm, but block 388,000 
should be about right as a minimum.

Ross

On 22/06/2015 22:04, Stephen Morse wrote:
>
>     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".
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


--------------070401020302090605090002
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Potentially daft question, why not use a minimum height? Yes, it's
    imprecise, but over an extended period of time they're good enough
    IMHO.<br>
    <br>
    I'd have to do more careful calculations to confirm, but block
    388,000 should be about right as a minimum.<br>
    <br>
    Ross<br>
    <br>
    <div class=3D"moz-cite-prefix">On 22/06/2015 22:04, Stephen Morse
      wrote:<br>
    </div>
    <blockquote
cite=3D"mid:CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmai=
l.com"
      type=3D"cite">
      <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-lef=
t-style:solid;padding-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'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=A0<font face=3D"monospace, monospace">pindex<=
/font>=A0has=A0<font
                face=3D"monospace, monospace">pindex-&gt;GetMedianTimePas=
t(</font>)
              after=A0midnight 11 Jan 2016 and where a supermajority
              showing support for the fork has previously been
              reached".=A0</div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
bitcoin-dev mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:bitcoin-dev@lists.li=
nuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.linuxfoundation.=
org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailm=
an/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070401020302090605090002--