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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eth3rs@gmail.com>) id 1YN1qt-0001Em-Iq
for bitcoin-development@lists.sourceforge.net;
Sun, 15 Feb 2015 16:15:23 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.176 as permitted sender)
client-ip=209.85.212.176; envelope-from=eth3rs@gmail.com;
helo=mail-wi0-f176.google.com;
Received: from mail-wi0-f176.google.com ([209.85.212.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YN1qr-0005Nr-LD
for bitcoin-development@lists.sourceforge.net;
Sun, 15 Feb 2015 16:15:23 +0000
Received: by mail-wi0-f176.google.com with SMTP id h11so21366708wiw.3
for <bitcoin-development@lists.sourceforge.net>;
Sun, 15 Feb 2015 08:15:15 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.228.72 with SMTP id sg8mr36787962wic.48.1424016915625;
Sun, 15 Feb 2015 08:15:15 -0800 (PST)
Received: by 10.180.88.73 with HTTP; Sun, 15 Feb 2015 08:15:15 -0800 (PST)
Date: Sun, 15 Feb 2015 11:15:15 -0500
Message-ID: <CAEM=y+WztW6SdMObCZ1GaPL5i+vwvi4T2ds9yLXj5kFzss1-Nw@mail.gmail.com>
From: Ethan Heilman <eth3rs@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a1134cc4e69051b050f22c6d0
X-Spam-Score: -0.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
(eth3rs[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1YN1qr-0005Nr-LD
Subject: [Bitcoin-development] P2P tests: peers.dat's requested
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, 15 Feb 2015 16:15:23 -0000
--001a1134cc4e69051b050f22c6d0
Content-Type: text/plain; charset=UTF-8
Hi All,
I am currently running some tests on the peering system in Bitcoind for a
research paper. We hope to develop improvements which we can share with the
community. A wide diversity of real peers.dat files would be very helpful.
If you are willing, please email me your peers.dat.
Thanks,
--001a1134cc4e69051b050f22c6d0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hi All,</div>I am currently running some tests on the=
peering system in Bitcoind for a research paper. We hope to develop improv=
ements which we can share with the community.=C2=A0A wide diversity of real=
peers.dat files would be very helpful. If you are willing, please email me=
your peers.dat.<br>Thanks,<br><br></div>
--001a1134cc4e69051b050f22c6d0--
|
