From: Tom Harding <tomh@thinlink•com>
To: Adam Back <adam@cypherspace•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] soft-fork block size increase (extension blocks)
Date: Mon, 01 Jun 2015 17:42:41 -0700 [thread overview]
Message-ID: <556CFC01.9030309@thinlink.com> (raw)
In-Reply-To: <CALqxMTE57mEiG7VuEDSfBDswCeYPWRoa1DEY9iL=P0xLFu8YCA@mail.gmail.com>
On 6/1/2015 10:21 AM, Adam Back wrote:
> if it stays as is for a year, in a wait and see, reduce spam, see
> fee-pressure take effect as it has before, work on improving improve
> decentralisation metrics, relay latency, and do a blocksize increment
> to kick the can if-and-when it becomes necessary and in the mean-time
> try to do something more long-term ambitious about scale rather than
> volume.
What's your estimate of the lead time required to kick the can,
if-and-when it becomes necessary?
The other time-series I've seen all plot an average block size. That's
misleading, because there's a distribution of block sizes. If you bin
by retarget interval and plot every single block, you get this
http://i.imgur.com/5Gfh9CW.png
The max block size has clearly been in play for 8 months already.
next prev parent reply other threads:[~2015-06-02 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 15:40 Adam Back
2015-06-01 16:12 ` Mike Hearn
2015-06-01 17:21 ` Adam Back
2015-06-01 18:01 ` Mike Hearn
2015-06-01 18:39 ` [Bitcoin-development] soft-fork block size increase (extensionblocks) Raystonn .
2015-06-02 0:42 ` Tom Harding [this message]
2015-06-17 16:17 ` [Bitcoin-development] soft-fork block size increase (extension blocks) Richard Moore
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=556CFC01.9030309@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=adam@cypherspace$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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