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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bendavenport@gmail.com>) id 1W3Wyw-0002IY-FQ
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Jan 2014 20:22:34 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.181 as permitted sender)
client-ip=209.85.214.181; envelope-from=bendavenport@gmail.com;
helo=mail-ob0-f181.google.com;
Received: from mail-ob0-f181.google.com ([209.85.214.181])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W3Wys-0003mt-MN
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Jan 2014 20:22:34 +0000
Received: by mail-ob0-f181.google.com with SMTP id uy5so1689394obc.26
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Jan 2014 12:22:25 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.47.116 with SMTP id c20mr3486807oen.60.1389817345257;
Wed, 15 Jan 2014 12:22:25 -0800 (PST)
Received: by 10.76.122.80 with HTTP; Wed, 15 Jan 2014 12:22:25 -0800 (PST)
In-Reply-To: <CANAnSg0tH_bK_19rsRRHOeZgrGYeWMhW89fXPyS4DQGmS4r_7A@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>
Date: Wed, 15 Jan 2014 12:22:25 -0800
Message-ID: <CALimQCXgc0eXeOcqFGUaCpSF7gKEe87KzvLqHZwUysV3WyjjGw@mail.gmail.com>
From: Ben Davenport <bendavenport@gmail.com>
To: Drak <drak@zikula.org>
Content-Type: multipart/alternative; boundary=047d7b450dc02ac7dc04f0081155
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: 1W3Wys-0003mt-MN
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: Wed, 15 Jan 2014 20:22:34 -0000
--047d7b450dc02ac7dc04f0081155
Content-Type: text/plain; charset=ISO-8859-1
Love what's happening here, and how quickly things are moving, from initial
concept, to first implementation, to first transaction.
But may I suggest we consider changing the name "stealth address" to
something more neutral?
Already, many people on Reddit and elsewhere are misinterpreting the
purpose of such addresses, whether for tax evasion, criminal activity, or
who knows what. Bitcoin already has plenty of political hurdles based
sheerly on the technology. We don't need to make life harder for ourselves.
Even forgetting about politics, the "stealth" association just seems to
imply something secretive going on. Is a Fortune 500 company or worldwide
charity going to want to use something called a "stealth address"?
I'd propose the alternate term "routing address".
- It's a descriptive, neutral term
- It accurately describes what the address is: it's a way to route payment
to a recipient, but not the actual final address
- It can be analogized to a bank's routing number: It is uniquely, publicly
and persistently tied to the receiving institution. The payor and payee
knows when payment is made using it, but it's not publicly visible.
That's the best I've got, but here are some alternate terms in case that
doesn't work:
- reusable public address
- permanent public address
- permanent address
- static address
I don't like these quite as much because they're not as clear. Normal
addresses are all reusable, permanent and static -- they just _shouldn't_
be used that way.
Ben
On Tue, Jan 14, 2014 at 4:19 PM, Drak <drak@zikula.org> wrote:
> Sorry this is possibly OT, but someone posted this thread to r/bitcoin and
> it's gone straight to position 1. People are really enthusiastic about this
> feature.
>
> Drak
>
>
> ------------------------------------------------------------------------------
> 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
>
>
--047d7b450dc02ac7dc04f0081155
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Love what's happening here, and how quickly things are=
moving, from initial concept, to first implementation, to first transactio=
n.<div><br></div><div>But may I suggest we consider changing the name "=
;stealth address" to something more neutral?</div>
<div><br></div><div>Already, many people on Reddit and elsewhere are misint=
erpreting the purpose of such addresses, whether for tax evasion, criminal =
activity, or who knows what. Bitcoin already has plenty of political hurdle=
s based sheerly on the technology. We don't need to make life harder fo=
r ourselves. Even forgetting about politics, the "stealth" associ=
ation just seems to imply something secretive going on. Is a Fortune 500 co=
mpany or worldwide charity going to want to use something called a "st=
ealth address"?</div>
<div><br></div><div>I'd propose the alternate term "routing addres=
s".</div><div><br></div><div>- It's a descriptive, neutral term</d=
iv><div>- It accurately describes what the address is: it's a way to ro=
ute payment to a recipient, but not the actual final address</div>
<div>- It can be analogized to a bank's routing number: It is uniquely,=
publicly and persistently tied to the receiving institution. The payor and=
payee knows when payment is made using it, but it's not publicly visib=
le.</div>
<div><br></div><div>That's the best I've got, but here are some alt=
ernate terms in case that doesn't work:</div><div><br></div><div>- reus=
able public address</div><div>- permanent public address</div><div>- perman=
ent address</div>
<div>- static address</div><div><br></div><div>I don't like these quite=
as much because they're not as clear. Normal addresses are all reusabl=
e, permanent and static -- they just _shouldn't_ be used that way.</div=
>
<div><br></div><div>Ben</div></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Tue, Jan 14, 2014 at 4:19 PM, Drak <span dir=3D"lt=
r"><<a href=3D"mailto:drak@zikula.org" target=3D"_blank">drak@zikula.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 dir=3D"ltr"><div class=3D"gmail_extra">=
Sorry this is possibly OT, but someone posted this thread to r/bitcoin and =
it's gone straight to position 1. People are really enthusiastic about =
this feature.</div>
<span class=3D"HOEnZb"><font color=3D"#888888"><div class=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Drak</div></font></span></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 & 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>
--047d7b450dc02ac7dc04f0081155--
|
