From: Upal Chakraborty <bitcoin@upalc•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP 106 : Graphs Required
Date: Thu, 17 Sep 2015 23:19:47 +0530 [thread overview]
Message-ID: <CAED3CWjwOszaFQart02hVRvbmC4L_+J7CDz5cx6-8aaLZ5hgWg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Hello,
First of all, I'm not sure if it is the right place to ask for such help.
But, I thought, someone might just help out.
I'm looking for two graphs to analyze the effectiveness of BIP 106, which
can be found at
https://github.com/bitcoin/bips/blob/master/bip-0106.mediawiki.
Blockchain.info currently provides a graph plotting the historical data of
block size for each block, which can be found at...
https://blockchain.info/charts/avg-block-size?timespan=all&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
I need two similar graphs plotting max block size cap against each block,
calculated as per my two proposals in BIP 106. Is it possible for anyone to
provide these two graphs assuming max block size cap for block 1 was 1mb ?
Thanks & Regards,
Upal Chakraborty
[-- Attachment #2: Type: text/html, Size: 1335 bytes --]
reply other threads:[~2015-09-17 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAED3CWjwOszaFQart02hVRvbmC4L_+J7CDz5cx6-8aaLZ5hgWg@mail.gmail.com \
--to=bitcoin@upalc$(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