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
|
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 <etotheipi@gmail.com>) id 1W2nfH-0002yF-UG
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jan 2014 19:59:15 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.50 as permitted sender)
client-ip=209.85.128.50; envelope-from=etotheipi@gmail.com;
helo=mail-qe0-f50.google.com;
Received: from mail-qe0-f50.google.com ([209.85.128.50])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W2nfG-0003Av-Va
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jan 2014 19:59:15 +0000
Received: by mail-qe0-f50.google.com with SMTP id 1so7595512qec.37
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Jan 2014 11:59:09 -0800 (PST)
X-Received: by 10.49.15.202 with SMTP id z10mr43002448qec.46.1389643149559;
Mon, 13 Jan 2014 11:59:09 -0800 (PST)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
[76.111.96.126]) by mx.google.com with ESMTPSA id
t10sm16171882qef.23.2014.01.13.11.59.09
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 13 Jan 2014 11:59:09 -0800 (PST)
Message-ID: <52D4458C.6010909@gmail.com>
Date: Mon, 13 Jan 2014 14:59:08 -0500
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.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> <20140113194049.GJ38964@giles.gnomon.org.uk>
<CANAnSg30V01B_3LCJ09sTwcsYa4_WOg3sKd-=p6COZS6w0b-uA@mail.gmail.com>
In-Reply-To: <CANAnSg30V01B_3LCJ09sTwcsYa4_WOg3sKd-=p6COZS6w0b-uA@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative;
boundary="------------080904050301060403060505"
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
(etotheipi[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: 1W2nfG-0003Av-Va
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: Mon, 13 Jan 2014 19:59:16 -0000
This is a multi-part message in MIME format.
--------------080904050301060403060505
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
How is this different from the proposal I have made?
You distribute the root public key (but not chaincode!) of a BIP32
branch. You can put your root key on a business card if you want. Then
when someone wants to pay you, you simply give them the multiplier and
root key (they already have the root key, but should verify). The
multiplier does not reveal the chaincode, thus keeping it private, but
it does allow them to confirm that the final address they are paying is
derived from that root key they know belongs to you ("Please pay address
X; oh btw, X=rootKey*mult").
You can /choose/ to reveal that a given payment address is linked to
your root key without any compromise of privacy. Or you can choose to
ignore it and just give them a bare address the old way and still
maintain privacy. What advantages does "stealth addresses" have over
this scheme? You could extend it using some kind of deterministic
sub-branching and/or ECDH to create multiple payment addresses without
querying the payee.
I had planned to implement this system and push for people to accept it
because I don't see any downsides to it. It can easily be integrated
into a WoT (with signed root keys), or CA system piggybacking on SSL.
-Alan
On 01/13/2014 02:44 PM, Drak wrote:
> On 13 January 2014 19:40, Roy Badami <roy@gnomon.org.uk
> <mailto:roy@gnomon.org.uk>> wrote:
>
> At the moment, I can give them a business card with a Bitcoin address.
> Being able to give out a business card with a stealth address would be
> a major advance.
>
>
> My thoughts exactly.
>
> 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
--------------080904050301060403060505
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
How is this different from the proposal I have made?<br>
<br>
You distribute the root public key (but not chaincode!) of a BIP32
branch. You can put your root key on a business card if you want.
Then when someone wants to pay you, you simply give them the
multiplier and root key (they already have the root key, but should
verify). The multiplier does not reveal the chaincode, thus keeping
it private, but it does allow them to confirm that the final address
they are paying is derived from that root key they know belongs to
you ("Please pay address X; oh btw, X=rootKey*mult"). <br>
<br>
You can <i>choose</i> to reveal that a given payment address is
linked to your root key without any compromise of privacy. Or you
can choose to ignore it and just give them a bare address the old
way and still maintain privacy. What advantages does "stealth
addresses" have over this scheme? You could extend it using some
kind of deterministic sub-branching and/or ECDH to create multiple
payment addresses without querying the payee. <br>
<br>
I had planned to implement this system and push for people to accept
it because I don't see any downsides to it. It can easily be
integrated into a WoT (with signed root keys), or CA system
piggybacking on SSL.<br>
<br>
-Alan<br>
<br>
<br>
<div class="moz-cite-prefix">On 01/13/2014 02:44 PM, Drak wrote:<br>
</div>
<blockquote
cite="mid:CANAnSg30V01B_3LCJ09sTwcsYa4_WOg3sKd-=p6COZS6w0b-uA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 13 January 2014 19:40, Roy Badami
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:roy@gnomon.org.uk" target="_blank">roy@gnomon.org.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><span style="color:rgb(34,34,34)">At the
moment, I can give them a business card with a Bitcoin
address.</span><br>
</div>
Being able to give out a business card with a stealth
address would be<br>
a major advance.</blockquote>
<div><br>
</div>
<div>My thoughts exactly.</div>
<div><br>
</div>
<div>Drak </div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
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.
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bitcoin-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------080904050301060403060505--
|
