From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1VkcWL-0005HC-Lu
	for bitcoin-development@lists.sourceforge.net;
	Sun, 24 Nov 2013 16:26:53 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.50 as permitted sender)
	client-ip=209.85.215.50; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f50.google.com; 
Received: from mail-la0-f50.google.com ([209.85.215.50])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VkcWJ-0006ra-QU
	for bitcoin-development@lists.sourceforge.net;
	Sun, 24 Nov 2013 16:26:53 +0000
Received: by mail-la0-f50.google.com with SMTP id el20so2349285lab.9
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 24 Nov 2013 08:26:45 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.133.104 with SMTP id pb8mr18052329lbb.22.1385310405130; 
	Sun, 24 Nov 2013 08:26:45 -0800 (PST)
Received: by 10.112.63.166 with HTTP; Sun, 24 Nov 2013 08:26:45 -0800 (PST)
In-Reply-To: <CALxbBHWwQXjjET+-GFTKNFPd_yWPjEWGvS-YwUPL+z86J8sw0Q@mail.gmail.com>
References: <CALxbBHWwQXjjET+-GFTKNFPd_yWPjEWGvS-YwUPL+z86J8sw0Q@mail.gmail.com>
Date: Sun, 24 Nov 2013 08:26:45 -0800
Message-ID: <CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Christian Decker <decker.christian@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VkcWJ-0006ra-QU
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Network propagation speeds
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 24 Nov 2013 16:26:53 -0000

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.