From: Andrew C <achow101@gmail•com>
To: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] A Modified Version of Luke-jr's Block Size BIP
Date: Sun, 5 Feb 2017 16:50:26 -0500 [thread overview]
Message-ID: <ea63ed5a-4280-c063-4984-5bc8a4b2aafa@gmail.com> (raw)
Hello all,
Many people have expressed discontent with Luke-jr's proposed block size
BIP, in particular with the decrease in size that would occur if it were
to be activated prior to 2024.
I have decided to modify the proposal to instead begin the increase
steps at the current 1000000 byte limit. The increases and the time spam
of each increase will remain the same, just that the increase begins
from 1000000 bytes instead of 300000 bytes.
Furthermore, instead of a fixed schedule from a fixed point in time, the
increases will instead be calculated off of the MTP of the activation
block (the first block to be in the active state for this fork).
While this proposal shares many of the same issues with the one it
modifies, I hope that it will be slightly less controversial and can
allow us to move forward with scaling Bitcoin.
The full text of the proposal can be found at
https://github.com/achow101/bips/blob/bip-blksize/bip-blksize.mediawiki.
My implementation of it is available at
https://github.com/achow101/bitcoin/tree/bip-blksize
Andrew
next reply other threads:[~2017-02-05 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 21:50 Andrew C [this message]
2017-02-05 23:02 ` Luke Dashjr
2017-02-05 23:53 ` Andrew C
[not found] ` <C5621135-FBC8-44E7-9EC0-AFDEEBB6031E@thomaslerin.io>
2017-02-06 21:00 ` Andrew C
2017-02-06 18:19 ` t. khan
[not found] ` <201702061953.40774.luke@dashjr.org>
2017-02-06 20:25 ` t. khan
2017-02-08 14:44 ` alp alp
2017-02-08 15:51 ` Andrew Johnson
2017-02-08 15:57 ` alp alp
2017-02-08 16:28 ` Andrew Johnson
2017-02-08 18:16 ` alp alp
2017-02-08 19:53 ` t. khan
2017-02-08 19:56 ` Andrew Johnson
2017-02-08 20:13 ` alp alp
2017-02-10 10:33 ` Btc Drak
2017-02-10 4:10 Ryan J Martin
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=ea63ed5a-4280-c063-4984-5bc8a4b2aafa@gmail.com \
--to=achow101@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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