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
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
|
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 <bendavenport@gmail.com>) id 1W4Eyy-0005Rp-Bl
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 19:21:32 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.175 as permitted sender)
client-ip=209.85.214.175; envelope-from=bendavenport@gmail.com;
helo=mail-ob0-f175.google.com;
Received: from mail-ob0-f175.google.com ([209.85.214.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W4Eyw-0003Qv-HC
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 19:21:32 +0000
Received: by mail-ob0-f175.google.com with SMTP id uz6so4777394obc.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Jan 2014 11:21:25 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.74.137 with SMTP id t9mr2804637obv.79.1389986485063;
Fri, 17 Jan 2014 11:21:25 -0800 (PST)
Received: by 10.76.122.80 with HTTP; Fri, 17 Jan 2014 11:21:24 -0800 (PST)
In-Reply-To: <20140117144601.GA8614@petertodd.org>
References: <CANEZrP1KAVhi_-cxCYe0rR9LUSYJ8MyW8=6eSJZ65FeY5ZJNuQ@mail.gmail.com>
<20140114225321.GT38964@giles.gnomon.org.uk>
<CANAnSg0tH_bK_19rsRRHOeZgrGYeWMhW89fXPyS4DQGmS4r_7A@mail.gmail.com>
<CALimQCXgc0eXeOcqFGUaCpSF7gKEe87KzvLqHZwUysV3WyjjGw@mail.gmail.com>
<CAAS2fgShChAQryfUOBp60jB-zxn2tH986fu1HfT+LsNdBYnoYg@mail.gmail.com>
<CAJHLa0P5r2+kxy7w8G=h=TAhdk1jUoW5UOiv-euo47uQY0u9ZA@mail.gmail.com>
<op.w9q6jdsayldrnw@laptop-air.hsd1.ca.comcast.net>
<20140116212805.GA4421@petertodd.org>
<CANAnSg2TY7Zh7RnHkBeTz1s-WutGLayum8q5DhdLhtOBMDT9ng@mail.gmail.com>
<CANEZrP1=PMiJn9BoN50K1wz2tOdxx5L80ngjErCJqj5wm2ESPA@mail.gmail.com>
<20140117144601.GA8614@petertodd.org>
Date: Fri, 17 Jan 2014 11:21:24 -0800
Message-ID: <CALimQCU10asn65q=+VwCVNtgbROu9XQOYKzB7jy-TCFoemjEOQ@mail.gmail.com>
From: Ben Davenport <bendavenport@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=001a11c1fd62af54b604f02f723d
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
(bendavenport[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: 1W4Eyw-0003Qv-HC
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Stealth Addresses
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, 17 Jan 2014 19:21:32 -0000
--001a11c1fd62af54b604f02f723d
Content-Type: text/plain; charset=ISO-8859-1
Well, at least we don't have to worry about cache invalidation.
Ben
On Fri, Jan 17, 2014 at 6:46 AM, Peter Todd <pete@petertodd.org> wrote:
> On Fri, Jan 17, 2014 at 10:15:40AM +0100, Mike Hearn wrote:
> > I must say, this shed is mighty fine looking. It'd be a great place to
> > store our bikes. But, what colour should we paint it?
>
> I think we should paint it this colour:
>
> They had uncovered what seemed to be the side of a large coloured
> globule embedded in the substance. The colour, which resembled some
> of the bands in the meteor's strange spectrum, was almost impossible
> to describe; and it was only by analogy that they called it colour
> at all. Its texture was glossy, and upon tapping it appeared to
> promise both brittle ness and hollowness. One of the professors gave
> it a smart blow with a hammer, and it burst with a nervous little
> pop. Nothing was emitted, and all trace of the thing vanished with
> the puncturing. It left behind a hollow spherical space about three
> inches across, and all thought it probable that others would be
> discovered as the enclosing substance wasted away.
>
> I think it really gets to the core of my feelings about this naming
> discussion.
>
> > How about we split the difference and go with "privacy address"? As Peter
> > notes, that's what people actually like and want. The problem with
> stealth
> > is it's got strong connotations with American military hardware and
> perhaps
> > thieves sneaking around in the night:
> >
> > https://www.google.com/search?tbm=isch&q=stealth
>
> WOW! AWESOME KICK-ASS PICS!
>
> Come to think of it, I could have called it "incognito addresses" - a
> term nice enough that Google and Firefox use it in their browsers - but
> what's done is done and any further discussion about this is just going
> to confuse the public. Remember that in the long run all this stuff will
> be hidden behind payment protocols anyway, and users *won't even know*
> that under the hood a stealth address is being used, making the name
> just a technical detail. For now though, lets use the good PR and get
> some early adopters on board.
>
> However, the term 'incognito' probably would be a good one to use within
> wallet software itself to describe what it's doing when the user clicks
> the "I want my transactions to be private" setting - there are after all
> fundemental bandwidth-privacy trade-offs in the threat model supposed by
> both prefix and bloom filters. In this instance the term isn't going to
> go away.
>
>
> Anyway, back to work: For the actual address format I strongly think we
> need to ensure that it can be upgrading in a backwards compatible way.
> This means we have to be able to add new fields - for instance if
> Gregory's ideas for different ways of doing the SPV-bait came to
> fruition. Given that "addresses" aren't something that should stay
> user-visible forever, thoughts on just making the actual data a protocol
> buffers object?
>
> Second question: Any performance figures yet on how efficient scanning
> the blockchain for matching transactions actually is? I'd like to get an
> idea soon for both desktop and smartphone wallets so we can figure out
> what kind of trade-offs users might be forced into in terms of prefix
> length.
>
> --
> 'peter'[:-1]@petertodd.org
> 0000000000000001c9b372ed519ecc6d41c10b42a7457d1ca5acd560a535596b
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a11c1fd62af54b604f02f723d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Well, at least we don't have to worry about cache inva=
lidation.<div><br></div><div>Ben</div></div><div class=3D"gmail_extra"><br>=
<br><div class=3D"gmail_quote">On Fri, Jan 17, 2014 at 6:46 AM, Peter Todd =
<span dir=3D"ltr"><<a href=3D"mailto:pete@petertodd.org" target=3D"_blan=
k">pete@petertodd.org</a>></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 class=3D"im">On Fri, Jan 17, 2014 at 10=
:15:40AM +0100, Mike Hearn wrote:<br>
> I must say, this shed is mighty fine looking. It'd be a great plac=
e to<br>
> store our bikes. But, what colour should we paint it?<br>
<br>
</div>I think we should paint it this colour:<br>
<br>
=A0 =A0 They had uncovered what seemed to be the side of a large coloured<b=
r>
=A0 =A0 globule embedded in the substance. The colour, which resembled some=
<br>
=A0 =A0 of the bands in the meteor's strange spectrum, was almost impos=
sible<br>
=A0 =A0 to describe; and it was only by analogy that they called it colour<=
br>
=A0 =A0 at all. =A0Its texture was glossy, and upon tapping it appeared to<=
br>
=A0 =A0 promise both brittle ness and hollowness. One of the professors gav=
e<br>
=A0 =A0 it a smart blow with a hammer, and it burst with a nervous little<b=
r>
=A0 =A0 pop. Nothing was emitted, and all trace of the thing vanished with<=
br>
=A0 =A0 the puncturing. It left behind a hollow spherical space about three=
<br>
=A0 =A0 inches across, and all thought it probable that others would be<br>
=A0 =A0 discovered as the enclosing substance wasted away.<br>
<br>
I think it really gets to the core of my feelings about this naming<br>
discussion.<br>
<div class=3D"im"><br>
> How about we split the difference and go with "privacy address&qu=
ot;? As Peter<br>
> notes, that's what people actually like and want. The problem with=
stealth<br>
> is it's got strong connotations with American military hardware an=
d perhaps<br>
> thieves sneaking around in the night:<br>
><br>
> =A0 =A0<a href=3D"https://www.google.com/search?tbm=3Disch&q=3Dste=
alth" target=3D"_blank">https://www.google.com/search?tbm=3Disch&q=3Dst=
ealth</a><br>
<br>
</div>WOW! AWESOME KICK-ASS PICS!<br>
<br>
Come to think of it, I could have called it "incognito addresses"=
- a<br>
term nice enough that Google and Firefox use it in their browsers - but<br>
what's done is done and any further discussion about this is just going=
<br>
to confuse the public. Remember that in the long run all this stuff will<br=
>
be hidden behind payment protocols anyway, and users *won't even know*<=
br>
that under the hood a stealth address is being used, making the name<br>
just a technical detail. For now though, lets use the good PR and get<br>
some early adopters on board.<br>
<br>
However, the term 'incognito' probably would be a good one to use w=
ithin<br>
wallet software itself to describe what it's doing when the user clicks=
<br>
the "I want my transactions to be private" setting - there are af=
ter all<br>
fundemental bandwidth-privacy trade-offs in the threat model supposed by<br=
>
both prefix and bloom filters. In this instance the term isn't going to=
<br>
go away.<br>
<br>
<br>
Anyway, back to work: For the actual address format I strongly think we<br>
need to ensure that it can be upgrading in a backwards compatible way.<br>
This means we have to be able to add new fields - for instance if<br>
Gregory's ideas for different ways of doing the SPV-bait came to<br>
fruition. Given that "addresses" aren't something that should=
stay<br>
user-visible forever, thoughts on just making the actual data a protocol<br=
>
buffers object?<br>
<br>
Second question: Any performance figures yet on how efficient scanning<br>
the blockchain for matching transactions actually is? I'd like to get a=
n<br>
idea soon for both desktop and smartphone wallets so we can figure out<br>
what kind of trade-offs users might be forced into in terms of prefix<br>
length.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
'peter'[:-1]@<a href=3D"http://petertodd.org" target=3D"_blank">pet=
ertodd.org</a><br>
0000000000000001c9b372ed519ecc6d41c10b42a7457d1ca5acd560a535596b<br>
</font></span><br>---------------------------------------------------------=
---------------------<br>
CenturyLink Cloud: The Leader in Enterprise Cloud Services.<br>
Learn Why More Businesses Are Choosing CenturyLink Cloud For<br>
Critical Workloads, Development Environments & Everything In Between.<b=
r>
Get a Quote or Start a Free Trial Today.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D119420431&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D119420431&iu=3D/4140/ostg.clktrk</a><br>__________________=
_____________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
--001a11c1fd62af54b604f02f723d--
|
