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-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YOs7t-0001mT-RX
for bitcoin-development@lists.sourceforge.net;
Fri, 20 Feb 2015 18:16:33 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.173 as permitted sender)
client-ip=209.85.212.173; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f173.google.com;
Received: from mail-wi0-f173.google.com ([209.85.212.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YOs29-00047y-Hh
for bitcoin-development@lists.sourceforge.net;
Fri, 20 Feb 2015 18:10:38 +0000
Received: by mail-wi0-f173.google.com with SMTP id bs8so4765759wib.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 20 Feb 2015 10:10:31 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.14.196 with SMTP id r4mr26364888wic.77.1424455830024;
Fri, 20 Feb 2015 10:10:30 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Fri, 20 Feb 2015 10:10:29 -0800 (PST)
In-Reply-To: <CALqxMTE1OANaMAvqrcOLuKtYd_jmqYp5GcB4CX77S8+fR05=jg@mail.gmail.com>
References: <CALqxMTE2doZjbsUxd-e09+euiG6bt_J=_BwKY_Ni3MNK6BiW1Q@mail.gmail.com>
<CANEZrP32M-hSU-a1DA5aTQXsx-6425sTeKW-m-cSUuXCYf+zuQ@mail.gmail.com>
<CALqxMTFNdtUup5MB2Dc_AmQ827sM-t5yx7WQubbfOEd_bO_Ong@mail.gmail.com>
<CANEZrP0cOY5Wt_mvBSdGGmi4NfZi04SQ7d6GLpnRxmqvXNArGA@mail.gmail.com>
<CALqxMTE1OANaMAvqrcOLuKtYd_jmqYp5GcB4CX77S8+fR05=jg@mail.gmail.com>
Date: Fri, 20 Feb 2015 19:10:29 +0100
X-Google-Sender-Auth: ndV14_4cdy5pJmYREr3ko9DOgGA
Message-ID: <CANEZrP3MY=tobQCCT5TE4+HcBOQgXKuFcDZuExbRbewmzajVuQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Adam Back <adam@cypherspace.org>
Content-Type: multipart/alternative; boundary=f46d04138c7dbf3978050f88f71e
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: 1YOs29-00047y-Hh
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bloom filtering, privacy
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: Fri, 20 Feb 2015 18:16:33 -0000
--f46d04138c7dbf3978050f88f71e
Content-Type: text/plain; charset=UTF-8
>
> So now they ask a full node for merkle paths + transactions for the
> addresses from the UTXO set from the block(s) that it was found in.
This is the part where I get lost. How does this improve privacy? If I have
to specify which addresses are mine in this block, to get the tx data, the
node learns which addresses are mine at this point, no?
Also, are you saying each block needs a record of the entire UTXO set at
the time the block was made? I'm not sure how to parse this sentence.
Could you please walk me through precisely what happens and what data is
sent, once I learn that a block has interesting data in it?
--f46d04138c7dbf3978050f88f71e
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">So now they ask a full node for merkle paths + t=
ransactions for the<br>
addresses from the UTXO set from the block(s) that it was found in.</blockq=
uote><div><br></div><div>This is the part where I get lost. How does this i=
mprove privacy? If I have to specify which addresses are mine in this block=
, to get the tx data, the node learns which addresses are mine at this poin=
t, no?</div><div><br></div><div>Also, are you saying each block needs a rec=
ord of the entire UTXO set at the time the block was made? I'm not sure=
how to parse this sentence.</div><div><br></div><div>Could you please walk=
me through precisely what happens and what data is sent, once I learn that=
a block has interesting data in it?=C2=A0</div><div><br></div><div><br></d=
iv></div></div></div>
--f46d04138c7dbf3978050f88f71e--
|
