From: Gavin Andresen <gavinandresen@gmail•com>
To: Washington Sanchez <washington.sanchez@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Dynamic limit to the block size - BIP draft discussion
Date: Tue, 8 Sep 2015 13:04:16 -0400 [thread overview]
Message-ID: <CABsx9T1a5kbtw=SQrdXyp32LF7gA9LMShPMYEefP4arb6SQcHw@mail.gmail.com> (raw)
In-Reply-To: <CAG0bcYw=k_z82buUQ_kApmPgSenNy6FEsdXotLaS4Gn-kZbrKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
>
> 3) Let me put it another way, I've read that both Gavin and yourself are
> favorable to a dynamic limit on the block size. In your view, what is
> missing from this proposal, or what variables should be adjusted, to get
> the rules to a place where you and other Core developers would seriously
> consider it?
>
I'm not clear on what problem(s) you're trying to solve.
If you want blocks to be at least 60% full, then just specify a simple rule
like "maximum block size is 1.0/0.6 = 1.666 times the average block size
over the last N blocks (applied at every block or every 2016 blocks or
whatever, details don't really matter)".
If you want an upper limit on growth, then just implement a simple rule
like "Absolute maximum block size is 1 megabyte in 2016, 3.45 megabytes in
2017, and increases by a maximum of 3.45 times every year."
If you want me to take your proposal seriously, you need to justify why 60%
full is a good answer (and why we need a centralized decision on how full
blocks "should" be), and why 3.45 times-per-year is a good answer for
maximum growth (and, again, why we need a centralized decision on that).
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 1605 bytes --]
next prev parent reply other threads:[~2015-09-08 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 7:45 Washington Sanchez
2015-09-08 8:49 ` Btc Drak
2015-09-08 12:28 ` Ivan Brightly
2015-09-08 13:13 ` Adam Back
2015-09-08 13:52 ` Ivan Brightly
2015-09-08 14:02 ` Washington Sanchez
2015-09-08 14:18 ` Adam Back
2015-09-08 15:10 ` Washington Sanchez
2015-09-08 16:46 ` Andrew Johnson
2015-09-08 17:04 ` Gavin Andresen [this message]
2015-09-08 23:11 ` Washington Sanchez
2015-09-09 13:10 ` Washington Sanchez
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='CABsx9T1a5kbtw=SQrdXyp32LF7gA9LMShPMYEefP4arb6SQcHw@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=washington.sanchez@gmail$(echo .)com \
/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