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
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
Return-Path: <decker.christian@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C7090483
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 14 Apr 2018 16:14:17 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com
[209.85.215.46])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id ED2373CC
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 14 Apr 2018 16:14:16 +0000 (UTC)
Received: by mail-lf0-f46.google.com with SMTP id d20-v6so16480135lfe.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 14 Apr 2018 09:14:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=QozD6AeCdepN1PDDFJxgCwKzO0gZs9FTj65+KX+hVpY=;
b=T/qTzNK2neVslWns/2jsValotpgoiAaK6CGWD0Qlabj4v9N7LHCW5GVKsfChcIvKTR
mFrr4HyrPeFiGoXsY9/0laZVKPbjAGMI8sCkqS1gkODMzsBc8/1reZ8eAvFkrXjNpXHt
OkKFlZdAkinnWMI4PSNwPXxkpbhh+yx9GEdZPLMSuNGAzeNS94mQiObsCXd2vA8aa0y2
dEF75jiuwDARQ4DbinPHEq6PYmcL1STj+tUQWX5NrJnYCCEGV6DIPiP/uwqYjelyhS06
1s2OB0BqxB+tblDtvI0m4wyrI0SYKfOMKgH84IGy/5rpfcrTP/5+dAI3TX2qo+jtIOUT
+1OA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=QozD6AeCdepN1PDDFJxgCwKzO0gZs9FTj65+KX+hVpY=;
b=YYjJ/EnTCw5Sl6VgiKVUnZf3suiOppFeGrQvn1s1Dge809qoJC4t7InUdbJo5BiaAD
qN/WvwzCsVRYjGdp2T97mOhUu+DzprMc1ySdJUypCOlS597KBQ8DZa6VhDNydOTHfnb9
TLTboyz+hhtbbB0Ffu1P8uOETeO7B8Hmz0ED7cerc3K2ezM49WkEeMAUd7PYKwMlFD27
Ij7izFGt7cZwEyWLsaEqrEg+L1hGN8QcciHT/L+l+i3tVZ5kEol9xcPM7BCTwxCSn3KN
HuB3mUQ9crtMhg7UyPcbZYyYBC9K/LUd7I10ia3cOW4pH9e3JLLnqhl2IzGibt44s6CQ
fDRg==
X-Gm-Message-State: ALQs6tDLfdb0m3GlGBoJY2DNSpE5e5gLAMXJJvI4FvXiw3PkuzQgpOoC
rznUZ5IZkY6k/yBmXN0jIff+fVg/CwI4yxrkUwY=
X-Google-Smtp-Source: AIpwx4+YdEeXsHNThdUMJnJz6m2Q80jomwrDDFdnDCins500uZIvq3IKB/I9ARYTsz6PkoRgPHCNDZcPeCYBWfRD6TI=
X-Received: by 10.46.114.25 with SMTP id n25mr6039646ljc.128.1523722455256;
Sat, 14 Apr 2018 09:14:15 -0700 (PDT)
MIME-Version: 1.0
References: <paqids$e14$1@blaine.gmane.org>
<4A0CD31A-8745-4425-99FC-5DF12FA3B917@jonasschnelli.ch>
<CADZtCSjsLSr_A-cBG5weAgstW9RG0sDL1txHC_E9ksVL=xJ4uA@mail.gmail.com>
In-Reply-To: <CADZtCSjsLSr_A-cBG5weAgstW9RG0sDL1txHC_E9ksVL=xJ4uA@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Sat, 14 Apr 2018 16:14:04 +0000
Message-ID: <CALxbBHV=xpzu8iL-S=EKBc39QWvAiicVixM_j3Ve1TH+sngPoQ@mail.gmail.com>
To: Jim Posen <jim.posen@gmail.com>, Bitcoin development mailing list
<bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="f4f5e807ac4cae92b20569d14722"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] BloomFilter issue with segwit addresses
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Apr 2018 16:14:17 -0000
--f4f5e807ac4cae92b20569d14722
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Note that this would compound the privacy leak that Jonas Nick used to
identify address clusters via the bloom filters in one of his publications.
By reducing the false positives when matching you can get very detailed
clusters. Then again we know that bloom filters aren't good for privacy
anyway, so this might be a non-issue.
On Sat, Apr 14, 2018, 00:17 Jim Posen via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Why not add the outpoints owned by the wallet to the filter and watch for
> those instead of elements in the input script or witness data?
>
> On Fri, Apr 13, 2018 at 12:12 PM, Jonas Schnelli via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Hi Andreas
>>
>> Thanks for bringing this up and this seems indeed to be suboptimal.
>>
>> > I wonder if Bitcoin Core would be willing to extend the BIP37 matching
>> > rules such that data elements in the witness are also matched against?
>>
>> Bitcoin Core is not an identity that can be =E2=80=9Ewilling to extend=
=E2=80=9C (or
>> reject) a feature.
>> Someone needs to come up with a proposal (pull request).
>>
>> Maybe an extension for BIP37 would make sense (*meh*).
>> Just inserting the witness data into the bloom filter seems to be an eas=
y
>> solution (CBloomFilter::IsRelevantAndUpdate())
>>
>> /jonas
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--f4f5e807ac4cae92b20569d14722
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Note that this would compound the privacy leak that Jonas=
Nick used to identify address clusters via the bloom filters in one of his=
publications. By reducing the false positives when matching you can get ve=
ry detailed clusters. Then again we know that bloom filters aren't good=
for privacy anyway, so this might be a non-issue.</div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr">On Sat, Apr 14, 2018, 00:17 Jim Posen via bitc=
oin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoi=
n-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr">Why not add the outpoints owned by the walle=
t to the filter and watch for those instead of elements in the input script=
or witness data?</div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Fri, Apr 13, 2018 at 12:12 PM, Jonas Schnelli via bitcoin-dev <spa=
n dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
target=3D"_blank" rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org<=
/a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Andreas<br>
<br>
Thanks for bringing this up and this seems indeed to be suboptimal.<br>
<span><br>
> I wonder if Bitcoin Core would be willing to extend the BIP37 matching=
<br>
> rules such that data elements in the witness are also matched against?=
<br>
<br>
</span>Bitcoin Core is not an identity that can be =E2=80=9Ewilling to exte=
nd=E2=80=9C (or reject) a feature.<br>
Someone needs to come up with a proposal (pull request).<br>
<br>
Maybe an extension for BIP37 would make sense (*meh*).<br>
Just inserting the witness data into the bloom filter seems to be an easy s=
olution (CBloomFilter::IsRelevantAndUpdate())<br>
<br>
/jonas<br>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--f4f5e807ac4cae92b20569d14722--
|
