Message-ID: <554BB61D.1040602@jrn.me.uk>
Date: Thu, 07 May 2015 19:59:41 +0100
From: Ross Nicoll <jrn@jrn.me.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <554A91BE.6060105@bluematt.me>	<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>	<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>	<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>	<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>	<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>	<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>	<554BA032.4040405@bluematt.me>	<CANEZrP3yM9wsSPNgpOsXDk-DjUy5PW2XuRTvK2AyCNbVJ5hZHw@mail.gmail.com>	<CADJgMzti7ROH90APiwg4NOAT5+Av=4i295b8VN0sbSLr4+WWRw@mail.gmail.com>
	<CAEieSeTafYjBCVUotLKBXX=Z3UHBKdi5kU5CFSxXJEmzCudQMg@mail.gmail.com>
In-Reply-To: <CAEieSeTafYjBCVUotLKBXX=Z3UHBKdi5kU5CFSxXJEmzCudQMg@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------030002080602000609090701"
Subject: Re: [Bitcoin-development] Block Size Increase
Precedence: list

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

I'm presuming that schedule is just an example, as you'd end up with 
insanely large block sizes in a few years.

Absolutely, yes, an increase schedule is an option if people agree on 
it, and I think the better option, as the current limit too low, but 
jumping straight to a value big enough for "indefinitely" is a huge jump.

Gave some thought to scaling block size based on transaction fees, but 
suspect it would end up with miners sending huge fees to themselves with 
transactions that aren't relayed (so they only are actioned if they make 
it into a block that miner mines) to make the network allow bigger blocks.

Ross

On 07/05/2015 19:38, Chris Wardell wrote:
> Instead of raising the block size to another static number like 20MB, 
> can we raise it dynamically?
>
> Make the max block size something like:
> pow(2, nHeight/100000) * 1MB;  //double every ~2 years
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--------------030002080602000609090701
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">
    I'm presuming that schedule is just an example, as you'd end up with
    insanely large block sizes in a few years.<br>
    <br>
    Absolutely, yes, an increase schedule is an option if people agree
    on it, and I think the better option, as the current limit too low,
    but jumping straight to a value big enough for "indefinitely" is a
    huge jump.<br>
    <br>
    Gave some thought to scaling block size based on transaction fees,
    but suspect it would end up with miners sending huge fees to
    themselves with transactions that aren't relayed (so they only are
    actioned if they make it into a block that miner mines) to make the
    network allow bigger blocks.<br>
    <br>
    Ross<br>
    <br>
    <div class=3D"moz-cite-prefix">On 07/05/2015 19:38, Chris Wardell
      wrote:<br>
    </div>
    <blockquote
cite=3D"mid:CAEieSeTafYjBCVUotLKBXX=3DZ3UHBKdi5kU5CFSxXJEmzCudQMg@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <div>
            <div>Instead of raising the block size to another static
              number like 20MB, can we raise it dynamically?<br>
              <br>
            </div>
            Make the max block size something like:<br>
          </div>
        </div>
        pow(2, nHeight/100000) * 1MB;=A0 //double every ~2 years<br>
        <br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">----------------------------------------------------=
--------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud=20
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
<a class=3D"moz-txt-link-freetext" href=3D"http://ad.doubleclick.net/ddm/=
clk/290420510;117567292;y">http://ad.doubleclick.net/ddm/clk/290420510;11=
7567292;y</a></pre>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
Bitcoin-development mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Bitcoin-development@=
lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/=
lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/l=
istinfo/bitcoin-development</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030002080602000609090701--