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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <c1.sf-bitcoin@niftybox.net>) id 1W3eaj-0001U0-Gg
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jan 2014 04:30:05 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of niftybox.net
designates 95.142.167.147 as permitted sender)
client-ip=95.142.167.147;
envelope-from=c1.sf-bitcoin@niftybox.net; helo=i3.hyper.to;
Received: from i3.hyper.to ([95.142.167.147])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1W3eah-0005iS-9j for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jan 2014 04:30:05 +0000
Received: from localhost (localhost [127.0.0.1])
by i3.hyper.to (Postfix) with ESMTP id 184AFE0129
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 Jan 2014 05:29:57 +0100 (CET)
Received: from i3.hyper.to ([127.0.0.1])
by localhost (i3.hyper.to [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id vHDj5l3Q1-LW
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 Jan 2014 05:29:56 +0100 (CET)
Received: from [10.1.10.188] (50-1-105-185.dsl.dynamic.sonic.net
[50.1.105.185]) by i3.hyper.to (Postfix) with ESMTPSA id F15ECE0100
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 Jan 2014 05:29:55 +0100 (CET)
Message-ID: <1389846587.19590.22.camel@mimiz>
From: Miron <c1.sf-bitcoin@niftybox.net>
To: bitcoin-development@lists.sourceforge.net
Date: Wed, 15 Jan 2014 20:29:47 -0800
In-Reply-To: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net>
References: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.4-0ubuntu1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1W3eah-0005iS-9j
Subject: Re: [Bitcoin-development] Tor / SPV
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, 16 Jan 2014 04:30:05 -0000
On Wed, 2014-01-15 at 23:51 +0100, Mike Hearn wrote:
...
> 3) SPV wallets that want to get a good mix of nodes for measuring
> pending transactions identify nodes on the clearnet via their addr
> announcements+service flag, in the normal way. They select some of
> these nodes using the standard clearnet anti-sybil heuristics and
> connect without using Tor. They proceed to query them for their hidden
The SPV node could connect to the IP using Tor. It would preserve the
privacy of the SPV node - hard to see it's running Bitcoin. It also
reduces the ability of an attacker to MITM because the routing varies
with each exit node.
|
