From: Pieter Wuille <pieter.wuille@gmail•com>
To: Michael Gronager <gronager@ceptacle•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] On the optimal block size and why transaction fees are 8 times too low (or transactions 8 times too big)
Date: Thu, 7 Nov 2013 16:19:24 +0100 [thread overview]
Message-ID: <CAPg+sBhJqavKYW5TkW4N49FDiR-iRFrTaAEeeXL8rRtAOKjupQ@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBimHp-dSPLvyq_P0aspu_Mr3wFTox0-yKWs+USRwV3Wnw@mail.gmail.com>
Correcting myself:
On Thu, Nov 7, 2013 at 4:00 PM, Pieter Wuille <pieter.wuille@gmail•com> wrote:
> I believe that C. Decker's paper used measurements for propagation
> delays for blocks 180000-190000, which happened between may and juli
> 2012. The latest bitcoind/bitcoin-qt release at the time was 0.6.3.
They did use data from blocks 20000-210000, september-november 2012.
That was still before the 0.8 release, however.
--
Pieter
next prev parent reply other threads:[~2013-11-07 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 14:11 Michael Gronager
2013-11-07 15:00 ` Pieter Wuille
2013-11-07 15:19 ` Pieter Wuille [this message]
2013-11-07 15:22 ` Mike Hearn
2013-11-07 15:53 ` Michael Gronager
2013-11-07 20:31 ` Peter Todd
2013-11-07 21:58 ` Michael Gronager
2013-11-15 10:52 ` Peter Todd
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=CAPg+sBhJqavKYW5TkW4N49FDiR-iRFrTaAEeeXL8rRtAOKjupQ@mail.gmail.com \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gronager@ceptacle$(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