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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WiLFa-00065k-Jn
for bitcoin-development@lists.sourceforge.net;
Thu, 08 May 2014 10:08:26 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.170 as permitted sender)
client-ip=209.85.214.170; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f170.google.com;
Received: from mail-ob0-f170.google.com ([209.85.214.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WiLFZ-0006Sm-OX
for bitcoin-development@lists.sourceforge.net;
Thu, 08 May 2014 10:08:26 +0000
Received: by mail-ob0-f170.google.com with SMTP id uy5so2740724obc.15
for <bitcoin-development@lists.sourceforge.net>;
Thu, 08 May 2014 03:08:20 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.83.232 with SMTP id t8mr2884522oey.16.1399543700095; Thu,
08 May 2014 03:08:20 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Thu, 8 May 2014 03:08:19 -0700 (PDT)
In-Reply-To: <CA+s+GJDm=J6-SYr4KEZ70f46E3U61Yva36a-gccRFSiT5ia2-g@mail.gmail.com>
References: <536A8592.8010009@gmail.com>
<CA+s+GJASND3OU2e+YxUeLmSOW6pTkMwuzHCHeJnnihg6xK9Caw@mail.gmail.com>
<536A902C.6080602@gmail.com>
<CA+s+GJCaUX3ErgVean0e91CBorPc6RNKgYs08fOOsqNYtbd6RA@mail.gmail.com>
<CANEZrP2aUBFkwx0s_xcS_e4gv1Ao1240NVNNFR3bFUBf9hHqsA@mail.gmail.com>
<CA+s+GJC7p-W6EeGwsPXG7oDccpC_LfjE-mAiZjpkMtRwxH5sMw@mail.gmail.com>
<CAAS2fgR0CtYeLmp8pmMFvtOyqrhNgz0U-BsfBQ7QRr3dM-7J9g@mail.gmail.com>
<CA+s+GJDm=J6-SYr4KEZ70f46E3U61Yva36a-gccRFSiT5ia2-g@mail.gmail.com>
Date: Thu, 8 May 2014 12:08:19 +0200
X-Google-Sender-Auth: 35iboqxKEWCos9pUG5FGDEWlDPM
Message-ID: <CANEZrP243Uq8HKqJ0bedp7CPXzEc01HnwxRAuFfFEAatbAJT3A@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=089e01182c8a17896104f8e0a9db
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WiLFZ-0006Sm-OX
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
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: Thu, 08 May 2014 10:08:26 -0000
--089e01182c8a17896104f8e0a9db
Content-Type: text/plain; charset=UTF-8
>
> In a way it looks similar to how the Bitcoin DNS seeds work, trying to
> find good and stable nodes, although more extensive.
Yeah, it's somewhat similar, except that Tor directory authorities are
authenticated (the public keys are in the source code), whereas DNS seeds
aren't. Also Bitcoin puts way more emphasis on decentralisation than Tor
does. For Tor having a P2P network is just something that's needed in order
to build an anonymity network, but it's not actually the goal. For us,
decentralisation is pretty much the end goal.
--089e01182c8a17896104f8e0a9db
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">In a way it looks similar to how the Bitcoin DNS=
seeds work, trying to<br>
find good and stable nodes, although more extensive.</blockquote><div><br><=
/div><div>Yeah, it's somewhat similar, except that Tor directory author=
ities are authenticated (the public keys are in the source code), whereas D=
NS seeds aren't. Also Bitcoin puts way more emphasis on decentralisatio=
n than Tor does. For Tor having a P2P network is just something that's =
needed in order to build an anonymity network, but it's not actually th=
e goal. For us, decentralisation is pretty much the end goal.</div>
<div><br></div><div>=C2=A0</div></div></div></div>
--089e01182c8a17896104f8e0a9db--
|
