1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <decker.christian@gmail.com>) id 1VkchI-0000Bo-PA
for bitcoin-development@lists.sourceforge.net;
Sun, 24 Nov 2013 16:38:12 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.47 as permitted sender)
client-ip=209.85.219.47;
envelope-from=decker.christian@gmail.com;
helo=mail-oa0-f47.google.com;
Received: from mail-oa0-f47.google.com ([209.85.219.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VkchH-0006e8-0F
for bitcoin-development@lists.sourceforge.net;
Sun, 24 Nov 2013 16:38:12 +0000
Received: by mail-oa0-f47.google.com with SMTP id k1so3342495oag.6
for <bitcoin-development@lists.sourceforge.net>;
Sun, 24 Nov 2013 08:38:05 -0800 (PST)
X-Received: by 10.182.117.195 with SMTP id kg3mr20776369obb.17.1385311085623;
Sun, 24 Nov 2013 08:38:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.130.198 with HTTP; Sun, 24 Nov 2013 08:37:25 -0800 (PST)
In-Reply-To: <CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com>
References: <CALxbBHWwQXjjET+-GFTKNFPd_yWPjEWGvS-YwUPL+z86J8sw0Q@mail.gmail.com>
<CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Sun, 24 Nov 2013 17:37:25 +0100
Message-ID: <CALxbBHX9PACKFJM_-=0Hm7hO7Km7jnLNRk=pRcKYTAcPD4G5qg@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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
(decker.christian[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: 1VkchH-0006e8-0F
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:38:13 -0000
Sure thing, I'm looking for a good way to publish these measurements,
but I haven't found a good option yet. They are rather large in size,
so I'd rather not serve them along with the website as it hasn't got
the capacity. Any suggestions? If the demand is not huge I could
provide them on a per user basis.
--
Christian Decker
On Sun, Nov 24, 2013 at 5:26 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> 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.
|
