summaryrefslogtreecommitdiff
path: root/1d/073b13c0aef33d54e38b2f2fb011b1924e1f0a
blob: eb1cf138f24d7052baf909a7dc9836e05f363981 (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
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
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 <laanwj@gmail.com>) id 1WXwSA-0000bJ-Vw
	for bitcoin-development@lists.sourceforge.net;
	Wed, 09 Apr 2014 17:38:27 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.182 as permitted sender)
	client-ip=209.85.223.182; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f182.google.com; 
Received: from mail-ie0-f182.google.com ([209.85.223.182])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WXwSA-00082w-DE
	for bitcoin-development@lists.sourceforge.net;
	Wed, 09 Apr 2014 17:38:26 +0000
Received: by mail-ie0-f182.google.com with SMTP id y20so2787124ier.13
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 09 Apr 2014 10:38:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.88.79 with SMTP id b15mr2439681icm.65.1397065101159; Wed,
	09 Apr 2014 10:38:21 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Wed, 9 Apr 2014 10:38:21 -0700 (PDT)
In-Reply-To: <CAE28kUSg7BV4=Cm9AoJoQvgyGa=D7Kpj5idodqaOzy9QHpH8gg@mail.gmail.com>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
	<a591551b-1a5b-4fdc-8e4a-1a1dae4242f4@email.android.com>
	<CAE28kUSg7BV4=Cm9AoJoQvgyGa=D7Kpj5idodqaOzy9QHpH8gg@mail.gmail.com>
Date: Wed, 9 Apr 2014 19:38:21 +0200
Message-ID: <CA+s+GJDjESrSFL+ctAp1c=oivu+QGoBPVYn4ES4zSiWK=xiYDw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
Content-Type: multipart/alternative; boundary=90e6ba3fccc31533fc04f69f918e
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
	(laanwj[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: 1WXwSA-00082w-DE
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV
	wallets
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: Wed, 09 Apr 2014 17:38:27 -0000

--90e6ba3fccc31533fc04f69f918e
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 9, 2014 at 7:33 PM, Alex Mizrahi <alex.mizrahi@gmail.com> wrote:

> 1) It's more private. Bloom filters gives away quite accurate statistical
>> information about what coins you own to whom ever you happen to be
>> connected too. An attacker can easily use this to deanonymize you even if
>> you don't reuse addresses; Tor does not help much against this attack.
>>
>
> There is also an option to download everything, but do only a very basic
> surface validation (without keeping track of UTXOs).
> You do not need a full node for that.
>

You may not *need* a full node, but the point of this (which I clearly
explained in my opening post) would be to support the network.

Wladimir

--90e6ba3fccc31533fc04f69f918e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Wed, Apr 9, 2014 at 7:33 PM, Alex Mizrahi <span dir=3D"ltr">&lt;<a href=
=3D"mailto:alex.mizrahi@gmail.com" target=3D"_blank">alex.mizrahi@gmail.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D""><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1) It&#39;s more private. Bloom filters gives away quite accurate statistic=
al information about what coins you own to whom ever you happen to be conne=
cted too. An attacker can easily use this to deanonymize you even if you do=
n&#39;t reuse addresses; Tor does not help much against this attack.<br>

</blockquote><div><br></div></div><div>There is also an option to download =
everything, but do only a very basic surface validation (without keeping tr=
ack of UTXOs).</div><div>You do not need a full node for that.</div></div>
</div></div></blockquote><div><br></div><div>You may not *need* a full node=
, but the point of this (which I clearly explained in my opening post) woul=
d be to support the network.<br><br>Wladimir<br><br></div></div></div></div=
>

--90e6ba3fccc31533fc04f69f918e--