From: Gregory Maxwell <gmaxwell@gmail•com>
To: Christian Decker <decker.christian@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Network propagation speeds
Date: Sun, 24 Nov 2013 08:26:45 -0800 [thread overview]
Message-ID: <CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com> (raw)
In-Reply-To: <CALxbBHWwQXjjET+-GFTKNFPd_yWPjEWGvS-YwUPL+z86J8sw0Q@mail.gmail.com>
On Sun, Nov 24, 2013 at 8:20 AM, Christian Decker
<decker.christian@gmail•com> wrote:
> Since this came up again during the discussion of the Cornell paper I
> thought I'd dig up my measurement code from the Information
> Propagation paper and automate it as much as possible.
Could you publish the block ids and timestamp sets for each block?
It would be useful in correlating propagation information against
block characteristics.
next prev parent reply other threads:[~2013-11-24 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 16:20 Christian Decker
2013-11-24 16:26 ` Gregory Maxwell [this message]
2013-11-24 16:37 ` Christian Decker
2013-11-25 8:51 ` Michael Gronager
2013-11-25 19:27 ` Christian Decker
2013-11-27 19:35 ` Mike Hearn
2013-11-27 20:46 ` Christian Decker
2013-11-24 16:38 ` Mike Hearn
2013-11-24 17:13 ` 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=CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=decker.christian@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