public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tier Nolan <tier.nolan@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap
Date: Mon, 17 Aug 2015 13:43:46 +0100	[thread overview]
Message-ID: <CAE-z3OVgQuFsXNEe0ccXXS=pzxhHzZNJiuFJ3tc=5QD=D4oDSg@mail.gmail.com> (raw)
In-Reply-To: <CABerxhEwA7Pz0hdSuOf+RwWZiZpY1fSArB+UiyVUwr6S2fr3vQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On Mon, Aug 17, 2015 at 12:57 PM, Rodney Morris via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I haven't run any statistics or simulations, but I'm concerned that the
> interplay between the random distribution of transaction arrival and the
> random distribution of block times may lead to false signals.
>

You could just take the average of all the block sizes for the last 2016
window.

If average of last 2016 > 50% of the limit, then increase by 6.25%
Otherwise, decrease by 6.25%

This means that the average would be around 50% of the limit.  This gives
margin to create larger blocks when blocks are happening slowly.

A majority of miners could force the limit upwards by creating spam but
full blocks.

It could be coupled with a hard limit that grows at whatever is seen as the
maximum reasonable.  This would be both a maximum and a minimum.

All of these schemes add state to the system.  If the schedule is
predictable, then you can check determine the maximum block size purely
from the header and coinbase.

[-- Attachment #2: Type: text/html, Size: 1595 bytes --]

  parent reply	other threads:[~2015-08-17 12:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 11:57 [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap Rodney Morris
2015-08-17 12:38 ` Angel Leon
2015-08-17 12:43 ` Tier Nolan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-21 21:45 Upal Chakraborty
2015-08-20 15:02 Upal Chakraborty
2015-08-18 12:13 Upal Chakraborty
2015-08-18 17:26 ` Chris Wardell
2015-08-20  7:31   ` Jorge Timón
2015-08-20 10:23     ` Milly Bitcoin
2015-08-21  0:25       ` Tom Harding
2015-08-21  0:37         ` Peter Todd
2015-08-21 16:52           ` Tom Harding
2015-08-21 22:21             ` Peter Todd
2015-08-21 23:16               ` Tom Harding
2015-08-22  0:01                 ` Peter Todd
2015-08-22  3:21                   ` Jorge Timón
2015-08-22  6:26                     ` Peter Todd
2015-08-23 23:41                   ` Tom Harding
2015-08-24  2:27                     ` Jorge Timón
2015-08-21  0:45         ` Milly Bitcoin
2015-08-21  0:58           ` Peter Todd
2015-08-21  1:30             ` Milly Bitcoin
2015-08-21 20:28       ` Jorge Timón
2015-08-21 12:13     ` Sriram Karra
2015-08-21 20:09       ` Jorge Timón
2015-08-18 19:44 ` cedric perronnet
2015-08-18 20:58 ` Danny Thorpe
2015-08-18 21:17   ` Chris Wardell
2015-08-19 17:21   ` Upal Chakraborty
2015-08-17  9:44 Upal Chakraborty
2015-08-17  9:54 ` Levin Keller
2015-08-17  9:59 ` Patrick Strateman
2015-08-17 10:51   ` Btc Drak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE-z3OVgQuFsXNEe0ccXXS=pzxhHzZNJiuFJ3tc=5QD=D4oDSg@mail.gmail.com' \
    --to=tier.nolan@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox