public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris Kleeschulte <laconia@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Proposed BIP: Maximum block size consensus rule based on median block size (adaptive block size)
Date: Fri, 25 Mar 2016 13:27:30 -0400	[thread overview]
Message-ID: <CAO1Z-eMxRfM8O+uTFbK0rb-zuL0KKLgYFJex35Rk8UJgGYd4RA@mail.gmail.com> (raw)

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

The following draft BIP proposes changing the MAX_BLOCK_SIZE consensus rule
to be a function of the median block size over the last 12,960 blocks
(about three months) multiplied by 2 and calculated when a block is
connected to the blockchain.

Motivation:

The purpose of this consensus rule change is to allow the maximum block
size to increase or decrease based on actual network usage. A block size
limit, as discussed here, prevents certain types of denial of service
attacks on the Bitcoin network, however a fixed limit does not allow the
capacity of the network to increase as advancements in scaling are
realized.  By adjusting the limit based on the sizes of blocks in the
recent past, the throughput of the network can adjust to changes in user
demand and scaling related technology advancements while still being
protected from denial of service attacks.


Full proposal here:

https://github.com/bitpay/bips/blob/master/bip-adaptiveblocksize.mediawiki

I look forward to your consideration.

thank you,
-- 
Chris Kleeschulte

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

             reply	other threads:[~2016-03-25 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 17:27 Chris Kleeschulte [this message]
2016-03-25 18:48 ` [bitcoin-dev] Proposed BIP: Maximum block size consensus rule based on median block size (adaptive block size) Tier Nolan

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=CAO1Z-eMxRfM8O+uTFbK0rb-zuL0KKLgYFJex35Rk8UJgGYd4RA@mail.gmail.com \
    --to=laconia@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