summaryrefslogtreecommitdiff
path: root/56/7ab864925d43ef5d7e45441d3d40f8784c7be5
blob: 26c465991872bfd3c2b991e4fc57e9d0cbc5e802 (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
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
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <g.rowe.froot@gmail.com>) id 1W3gPn-0006ud-0x
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Jan 2014 06:26:55 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.128.49 as permitted sender)
	client-ip=209.85.128.49; envelope-from=g.rowe.froot@gmail.com;
	helo=mail-qe0-f49.google.com; 
Received: from mail-qe0-f49.google.com ([209.85.128.49])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1W3gPl-0003bD-A7
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Jan 2014 06:26:54 +0000
Received: by mail-qe0-f49.google.com with SMTP id w4so2103710qeb.22
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 15 Jan 2014 22:26:47 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.140.31.75 with SMTP id e69mr5048442qge.76.1389853607444;
	Wed, 15 Jan 2014 22:26:47 -0800 (PST)
Sender: g.rowe.froot@gmail.com
Received: by 10.96.26.168 with HTTP; Wed, 15 Jan 2014 22:26:47 -0800 (PST)
In-Reply-To: <CAAf19WoHkzsfkH_U9EdEcJkZ6iy2vHc-50W4y30NQ_Ur7RGAdg@mail.gmail.com>
References: <20140106120338.GA14918@savin>
	<op.w9c5o7vgyldrnw@laptop-air.hsd1.ca.comcast.net>
	<20140110102037.GB25749@savin>
	<op.w9kkxcityldrnw@laptop-air.hsd1.ca.comcast.net>
	<CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com>
	<CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com>
	<CANEZrP0huBWqgvQik9Yc26Tu4CwR0VSXcfC+qfzsZqvoU4VJGA@mail.gmail.com>
	<20140113133746.GI38964@giles.gnomon.org.uk>
	<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>
	<CAAf19WoHkzsfkH_U9EdEcJkZ6iy2vHc-50W4y30NQ_Ur7RGAdg@mail.gmail.com>
Date: Thu, 16 Jan 2014 06:26:47 +0000
X-Google-Sender-Auth: FqnvYIFo7oY83osW71EeBRMrjsE
Message-ID: <CAKm8k+3hYOEVDO+jRKLihDHbjYSVbeNMto5JvqgEy3XcK_zP4w@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a113a96ca8fc73604f010821e
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
	(g.rowe.froot[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: 1W3gPl-0003bD-A7
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: Thu, 16 Jan 2014 06:26:55 -0000

--001a113a96ca8fc73604f010821e
Content-Type: text/plain; charset=UTF-8

I like "reusable address".

It is very clear what the intended purpose is and gives a subtle hint that
other types of address should not be re-used.



On 16 January 2014 00:44, Eric Martindale <eric@ericmartindale.com> wrote:

> One variation of this, "recycled address", might avert misconceptions that
> the "re-use" is exclusive to one's own identity.
>
>
> Eric Martindale, relentless maker.
> http://www.ericmartindale.com
> +1 (919) 374-2020 | *BitMessage: *BM-2cWCmYBpV64FRSJpHHKWi1Cfc9W52jydwe
> *Note:* Beginning December 11th, 2013, I will only be intermittently
> available via email, SMS, and BitMessage.  As a courtesy, please leave a
> detailed message so that I can respond in kind.  Thanks!
>
>
> On Wed, Jan 15, 2014 at 7:05 PM, Jeremy Spilman <jeremy@taplink.co> wrote:
>
>>  Might I propose "reusable address".
>>
>> I think that describes it best to any non-programmer, and even more so
>> encourages wallets to present options as 'one time use' vs 'reusable'.
>>
>> It definitely packs a marketing punch which could help drive adoption.
>> The feature is only useful if/when broadly adopted.
>>
>> I think it meets all the criteria required:
>>
>>   - Communication between parties is a single message from the payee,
>> which may be public
>>   - Multiple payments to the same address are not publicly linkable on
>> the blockchain
>>   - The payee has explicitly designated they expect to receive more than
>> one payment at that address
>>   - Payer can publicly prove they made a payment to the reusable address
>> by revealing a secret
>>
>> I have high hopes for this feature. The war *against* address reuse may
>> soon be a distant memory.
>>
>> On Wed, 15 Jan 2014 12:44:17 -0800, Jeff Garzik <jgarzik@bitpay.com>
>> wrote:
>>
>> "static address" seems like a reasonable attempt at describing intended
>> use/direction.
>>
>> On Wed, Jan 15, 2014 at 3:38 PM, Gregory Maxwell <gmaxwell@gmail.com>wrote:
>>
>>> On Wed, Jan 15, 2014 at 12:22 PM, Ben Davenport <bendavenport@gmail.com>
>>> wrote:
>>> > But may I suggest we consider changing the name "stealth address" to
>>> > something more neutral?
>>>
>>> ACK.  Regardless of the 'political' overtones, I think stealth is a
>>> little cringe-worthy.
>>>
>>> "Private address" would be fine if not for confusion with private-keys.
>>>
>>> "Static address" is perhaps the best in my view. (also helps improve
>>>  awareness that normal addresses are intended to be more one-use-ness)
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>
>
> ------------------------------------------------------------------------------
> 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
>
>

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

<div dir=3D"ltr">I like &quot;reusable address&quot;.=C2=A0<div><br></div><=
div>It is very clear what the intended purpose is and gives a subtle hint t=
hat other types of address should not be re-used.<div><br></div></div></div=
><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On 16 January 2014 00:44, Eric Martindal=
e <span dir=3D"ltr">&lt;<a href=3D"mailto:eric@ericmartindale.com" target=
=3D"_blank">eric@ericmartindale.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<div dir=3D"ltr">One variation of this, &quot;recycled address&quot;, might=
 avert misconceptions that the &quot;re-use&quot; is exclusive to one&#39;s=
 own identity.</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div =
dir=3D"ltr">

<div style=3D"font-family:arial;font-size:small"><br>Eric Martindale, relen=
tless maker.</div><div style=3D"font-family:arial;font-size:small"><a href=
=3D"http://www.ericmartindale.com/" style=3D"color:rgb(17,85,204)" target=
=3D"_blank">http://www.ericmartindale.com</a></div>

<div><a href=3D"tel:%2B1%20%28919%29%20374-2020" value=3D"+19193742020" tar=
get=3D"_blank">+1 (919) 374-2020</a><font face=3D"arial">=C2=A0|=C2=A0</fon=
t><b style=3D"font-family:arial;font-size:small">BitMessage:=C2=A0</b><a st=
yle=3D"font-family:arial;font-size:small;color:rgb(17,85,204)">BM-2cWCmYBpV=
64FRSJpHHKWi1Cfc9W52jydwe</a></div>

<div style=3D"font-family:arial;font-size:small"><b>Note:</b>=C2=A0Beginnin=
g December 11th, 2013, I will only be intermittently available via email, S=
MS, and BitMessage. =C2=A0As a courtesy, please leave a detailed message so=
 that I can respond in kind. =C2=A0Thanks!</div>

</div></div>
<br><br><div class=3D"gmail_quote"><div class=3D"im">On Wed, Jan 15, 2014 a=
t 7:05 PM, Jeremy Spilman <span dir=3D"ltr">&lt;<a href=3D"mailto:jeremy@ta=
plink.co" target=3D"_blank">jeremy@taplink.co</a>&gt;</span> wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div><div class=3D"h5">
<u></u>


<div><div>Might I propose &quot;reusable address&quot;.<br><br>I think that=
 describes it best to any non-programmer, and even more so encourages walle=
ts to present options as &#39;one time use&#39; vs &#39;reusable&#39;.</div=
>

<div><br></div><div>It definitely packs a marketing punch which could help =
drive adoption. The feature is only useful if/when broadly adopted.<br><br>=
I think it meets all the criteria required:</div><div><br></div><div>=C2=A0=
 - Communication between parties is a single message from the payee, which =
may be public</div>

<div>=C2=A0 - Multiple payments to the same address are not publicly linkab=
le on the blockchain</div><div>=C2=A0 - The payee has explicitly designated=
 they expect to receive more than one payment at that address</div><div>=C2=
=A0 - Payer can publicly prove they made a payment to the reusable address =
by revealing a secret</div>

<div><br></div><div>I have high hopes for this feature. The war *against* a=
ddress reuse may soon be a distant memory.</div><div><div><br></div><div>On=
 Wed, 15 Jan 2014 12:44:17 -0800, Jeff Garzik &lt;<a href=3D"mailto:jgarzik=
@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>&gt; wrote:<br>

</div><blockquote style=3D"margin:0 0 0.80ex;border-left:#0000ff 2px solid;=
padding-left:1ex"><div dir=3D"ltr">&quot;static address&quot; seems like a =
reasonable attempt at describing intended use/direction.<br><br><div class=
=3D"gmail_quote">

On Wed, Jan 15, 2014 at 3:38 PM, Gregory Maxwell <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:gmaxwell@gmail.com" target=3D"_blank">gmaxwell@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>On Wed, Jan 15, 2014 at 12:22 PM, Ben D=
avenport &lt;<a href=3D"mailto:bendavenport@gmail.com" target=3D"_blank">be=
ndavenport@gmail.com</a>&gt; wrote:<br>



&gt; But may I suggest we consider changing the name &quot;stealth address&=
quot; to<br>
&gt; something more neutral?<br>
<br>
</div>ACK. =C2=A0Regardless of the &#39;political&#39; overtones, I think s=
tealth is a<br>
little cringe-worthy.<br>
<br>
&quot;Private address&quot; would be fine if not for confusion with private=
-keys.<br>
<br>
&quot;Static address&quot; is perhaps the best in my view. (also helps impr=
ove<br>=C2=A0awareness that normal addresses are intended to be more one-us=
e-ness)</blockquote></div></div></blockquote></div></div><br></div></div><d=
iv class=3D"im">
---------------------------------------------------------------------------=
---<br>

CenturyLink Cloud: The Leader in Enterprise Cloud Services.<br>
Learn Why More Businesses Are Choosing CenturyLink Cloud For<br>
Critical Workloads, Development Environments &amp; 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&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D119420431&amp;iu=3D/4140/ostg.clktrk</a><br>__________________=
_____________________________<br>


Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@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></div></blockquote></div><br></div>
<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 &amp; 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&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D119420431&amp;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>

--001a113a96ca8fc73604f010821e--