summaryrefslogtreecommitdiff
path: root/bb/a36248c776b3b1b69b5c1fc54e54e13c754dd7
blob: 9e1ce5d680e5e8b4d14a91b14993ed25a8d76221 (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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <drak@zikula.org>) id 1W3jyT-0007Vl-KE
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Jan 2014 10:14:57 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of zikula.org
	designates 209.85.212.174 as permitted sender)
	client-ip=209.85.212.174; envelope-from=drak@zikula.org;
	helo=mail-wi0-f174.google.com; 
Received: from mail-wi0-f174.google.com ([209.85.212.174])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1W3jyR-0000E8-Pc
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Jan 2014 10:14:57 +0000
Received: by mail-wi0-f174.google.com with SMTP id g10so5358301wiw.7
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 16 Jan 2014 02:14:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=CX924s2p9b/M3yS2GOYlBLdfLoBlqw0unlJPrukaqc8=;
	b=VWK0GZkyESbDOPNVTjr8KA4c2vQyhtS4B/swoEtJOABTNQJM4UrCdgNqJv7kPD1zcf
	hC0EFl11K7u6FE1RKwCuzW1TtC2vfEbgRJw+w+ID4KwIpiV5FpwTLLbYFM/KIQNImi0p
	WB/17uP3/tUscC82iDLm/qwBF1Iqw0wrUxqr3S+rFrfRAsbKVAfjVbjfQCWW2dP6ocXy
	gNnlmLhB8JgkiIeA+lNp4NHdHo2X6VNHPeV88G142W1z1rwGKZ6RZj/CdtKouFzQSc1k
	r00/HwuXmAnay3BSMImE9OrXSyDx2l1mPoPm/0QuQ3VXwyY4QhLsyg/Ovw7kS9cWJT/m
	hYUA==
X-Gm-Message-State: ALoCoQmtcHUsPoX2YxTWZ0T0h403JQev5wb93HfCuVQHflIDu++m59svOZLLaqHsskQLz9WfdwrD
X-Received: by 10.180.211.101 with SMTP id nb5mr9490225wic.0.1389867284156;
	Thu, 16 Jan 2014 02:14:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.30.8 with HTTP; Thu, 16 Jan 2014 02:14:24 -0800 (PST)
In-Reply-To: <op.w9q6jdsayldrnw@laptop-air.hsd1.ca.comcast.net>
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>
From: Drak <drak@zikula.org>
Date: Thu, 16 Jan 2014 10:14:24 +0000
Message-ID: <CANAnSg0iE_ZdbXbkBwsafUJ6_ck4jETQM0o0RY-0am-o7=6Xbg@mail.gmail.com>
To: Jeremy Spilman <jeremy@taplink.co>
Content-Type: multipart/alternative; boundary=001a11c37cc6c1e69a04f013b18d
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 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1W3jyR-0000E8-Pc
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: Thu, 16 Jan 2014 10:14:57 -0000

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

On 16 January 2014 00:05, 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'.
>

The problem is all addresses are reusable and to an average user, addresses
are already reusable so there is little to distinguish the address format.
It might be better to call it a "public address" in common terminology.

Drak

--001a11c37cc6c1e69a04f013b18d
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">On 1=
6 January 2014 00:05, Jeremy Spilman <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:jeremy@taplink.co" target=3D"_blank">jeremy@taplink.co</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:=
solid;padding-left:1ex">

<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></blockquote><div><br></div><div>The problem is all addresses are reu=
sable and to an average user, addresses are already reusable so there is li=
ttle to distinguish the address format.</div><div>It might be better to cal=
l it a &quot;public address&quot; in common terminology.</div>

<div><br></div><div>Drak<br></div><div>=C2=A0</div></div></div></div>

--001a11c37cc6c1e69a04f013b18d--