summaryrefslogtreecommitdiff
path: root/1f/62435639872ea2c3aa5d570773720b0738813f
blob: 3a87ba001efa2fa1dc5b14a6df4406348c94a98b (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WiJ0v-0005iV-Fq
	for bitcoin-development@lists.sourceforge.net;
	Thu, 08 May 2014 07:45:09 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.180 as permitted sender)
	client-ip=209.85.223.180; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f180.google.com; 
Received: from mail-ie0-f180.google.com ([209.85.223.180])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WiJ0u-0000Ld-DP
	for bitcoin-development@lists.sourceforge.net;
	Thu, 08 May 2014 07:45:09 +0000
Received: by mail-ie0-f180.google.com with SMTP id as1so2206553iec.39
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 08 May 2014 00:45:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.50.146 with SMTP id c18mr51478327igo.42.1399535102513;
	Thu, 08 May 2014 00:45:02 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Thu, 8 May 2014 00:45:02 -0700 (PDT)
In-Reply-To: <CAAS2fgR0CtYeLmp8pmMFvtOyqrhNgz0U-BsfBQ7QRr3dM-7J9g@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>
Date: Thu, 8 May 2014 09:45:02 +0200
Message-ID: <CA+s+GJDm=J6-SYr4KEZ70f46E3U61Yva36a-gccRFSiT5ia2-g@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Gregory Maxwell <gmaxwell@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
	(laanwj[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: 1WiJ0u-0000Ld-DP
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 07:45:09 -0000

On Thu, May 8, 2014 at 2:47 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>
> The tor network works based on a centralized (well, in theory,
> federated) trusted directory service. (More info in
> https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=dir-spec.txt).

Thanks!

> Much of data that is not related to relay related is just generated by
> probes, e.g. semi-trusted bandwidth authorities that measure node
> performance back to the directory authorities.

Right, so there is more involved than just adding having nodes provide
measuring points, a third-party is also performing tests on the nodes.

In a way it looks similar to how the Bitcoin DNS seeds work, trying to
find good and stable nodes, although more extensive.

Wladimir