From: Richard Moore <me@ricmoo•com>
To: Tom Harding <tomh@thinlink•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] soft-fork block size increase (extension blocks)
Date: Wed, 17 Jun 2015 12:17:22 -0400 [thread overview]
Message-ID: <3FBD7273-9A22-49EA-902C-0EE1F1F5940E@ricmoo.com> (raw)
In-Reply-To: <556CFC01.9030309@thinlink.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
Awesome graph!
It would be interesting if you could use your Excel voodoo (or whatever graph app you use) to add density as a heat map, making areas with more blocks red and regions with less blocks blue…
> On Jun 1, 2015, at 8:42 PM, Tom Harding <tomh@thinlink•com> wrote:
>
> 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.
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸><(((º>
Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo@geneticmistakes•com <mailto:ricmoo@geneticmistakes•com>
www: http://GeneticMistakes.com <http://geneticmistakes.com/>
[-- Attachment #2: Type: text/html, Size: 3314 bytes --]
prev parent reply other threads:[~2015-06-17 16:48 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 ` [Bitcoin-development] soft-fork block size increase (extension blocks) Tom Harding
2015-06-17 16:17 ` Richard Moore [this message]
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=3FBD7273-9A22-49EA-902C-0EE1F1F5940E@ricmoo.com \
--to=me@ricmoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tomh@thinlink$(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