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
|
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 <justus.ranvier@monetas.net>) id 1Ylnrh-0001r3-3B
for bitcoin-development@lists.sourceforge.net;
Sat, 25 Apr 2015 00:22:37 +0000
Received: from mail-ig0-f181.google.com ([209.85.213.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ylnrf-0005ZF-JH
for bitcoin-development@lists.sourceforge.net;
Sat, 25 Apr 2015 00:22:37 +0000
Received: by iget9 with SMTP id t9so37766329ige.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 24 Apr 2015 17:22:30 -0700 (PDT)
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:date
:message-id:subject:from:to:content-type;
bh=th3q2BmRlFFdvOWFCbQT8DMcJatNp7nhGjA1aAxiK20=;
b=S4DmVIk0IyI6UN0ziGxe8i/GXTlKiFz/XSHIpj1W8Po8SEFvGv8ttnWnNtDq3iZazD
fzPFqxEeB8fOwhuRLjEQQmOT3tklOuUF4O5ErEbm9NQhlLDPjvQb31JtYObaSXWbdvQB
u4PD9v4iodhFtRX1GC47PZCHXounlL/NJktL984oNQ28wEIUWWVd8yyMXVpDj9FmL1Zj
EAZcW4q6voloONrK4m4FN3rv6qY0dh3OjJb7Lz/z+vj27F3ZdAvBFatbUgoCC5ASG4I1
ATE0IeUkGrK7J7jpDKXviHDHlldH6/99nOEAzDEhgKNfEFgUlQERyPF9zOFBln1eWl6A
IqXQ==
X-Gm-Message-State: ALoCoQkg8zvZUH1QksILQvO5L/RzP1nuPB9mPAUR+QoAY0APhetitgMFC3uFoDG4QONbMYAA8sXt
MIME-Version: 1.0
X-Received: by 10.42.135.131 with SMTP id p3mr1625243ict.81.1429921350204;
Fri, 24 Apr 2015 17:22:30 -0700 (PDT)
Received: by 10.36.205.135 with HTTP; Fri, 24 Apr 2015 17:22:30 -0700 (PDT)
In-Reply-To: <CAHabJ+NDqMN-rQ1BN1TfOjGLQHH-3Wd28LdoF95Agn4HdRrThg@mail.gmail.com>
References: <CAHabJ+Mn0=vfLvTJ+z3tx8cFAAuLD1pLp4rOe3pM6MtCrCxjwg@mail.gmail.com>
<1AE7B0A2-90EE-42EE-9D30-4DC1B5892E53@newcastle.ac.uk>
<CAHabJ+NDqMN-rQ1BN1TfOjGLQHH-3Wd28LdoF95Agn4HdRrThg@mail.gmail.com>
Date: Sat, 25 Apr 2015 02:22:30 +0200
Message-ID: <CAHabJ+PMdQ-f7G8RNz0R7mfGUwBMAsnCyO=NmQhxyq0+gB1aPg@mail.gmail.com>
From: Justus Ranvier <justus.ranvier@monetas.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=90e6ba2121e522df3f05148182e5
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Ylnrf-0005ZF-JH
Subject: [Bitcoin-development] Fwd: Reusable payment codes
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: Sat, 25 Apr 2015 00:22:37 -0000
--90e6ba2121e522df3f05148182e5
Content-Type: text/plain; charset=UTF-8
Taking the hash of the secret would then require an extra step to make sure
the hash is valid for secp256k1.
Using the x value directly avoids the need for that check.
On Fri, Apr 24, 2015 at 10:35 PM, Patrick Mccorry (PGR) <
patrick.mccorry@newcastle.ac.uk> wrote:
> When computing the diffie Hellman secret - why do you choose the x
> co-ordinate instead of the hash of the secret which is standard practice
> for stealth addresses
>
> Sent from my iPhone
>
> On 24 Apr 2015, at 21:27, Justus Ranvier <justus.ranvier@monetas.net>
> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Hash: SHA1
>
>
>
> https://github.com/justusranvier/rfc/blob/payment_code/bips/bip-pc01.mediawiki
>
>
> This link contains an RFC for a new type of Bitcoin address called a
> "payment code"
>
>
> Payment codes are SPV-friendly alternatives to DarkWallet-style stealth
> addresses which provide useful features such as positively identifying
> senders to recipients and automatically providing for transaction refunds.
>
>
> Payment codes can be publicly advertised and associated with a real-life
> identity without causing a loss of financial privacy.
>
>
> Compared to stealth addresses, payment codes require less blockchain
> data storage.
>
>
> Payment codes require 65 bytes of OP_RETURN data per sender-recipient
> pair, while stealth addresses require 40 bytes per transaction.
>
>
> -----BEGIN PGP SIGNATURE-----
>
> Version: GnuPG v1
>
>
> iQIcBAEBAgAGBQJVOqCRAAoJECpf2nDq2eYjluEP/RVJk+miDIihY4ilIvUbKvMd
>
> JLLqHr7Q1dlZyMIG/UqVWdoP5hzg/16B+q2iAB9jXozPnrDp0mggBh6rIGroevAa
>
> Kqfrs+Rrog1w9auhd67LWORDqav6YIrjTJIxdLxe11IEiq5rWbHPNUEDMzdEmHbz
>
> QfTH7KWAP2BasO5ETXcfu6BcccrXZ3XOKLON2h3NGD/cEDizY+uT2k3QN54z+KxG
>
> NB9scKbzVvsJwkyBrgbV+As9H3k6PnFsojYgAaE9gkp7D2+ahjzUiOH5rv6TbbYR
>
> o2X5MOiTY2/YZEqZPG7IR03ZAgeLVCvXXysjPOfzUKbmTF4w849sm8BuhixzDXHo
>
> 2V/HHKoGclIohcODBCWi0tVQXshZt4QkCNJBW5o3nL6Nn2YOp6hmw8YKAHnw3E7h
>
> /wIgk5f+NOLl/iIxoAxAdavEj5P6N4ic+OB6MAjnhEilWfBvCIpqWLGNvrtOhEa9
>
> EnPHcgb4ILBu4OionJhsNpJ/O95C0OEypMm25MIS+rQcV4Uxe5IOS2OuT/GreLET
>
> n/7Y0mJbqYbLBjVsfS+DNjvsgyJl5AxhcMrdVyXJjSYVcCoRhcoX5Ceidd+YkbHI
>
> OMs5f63tM1Rgi/WY4Ct80SD5EbULZuu8j1KJ9HPGuMt081JSBH+L5isiKuazPeO+
>
> SGApMBd4Q89fKzL2djae
>
> =Dypr
>
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--90e6ba2121e522df3f05148182e5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">Taking the has=
h of the secret would then require an extra step to make sure the hash is v=
alid for secp256k1.<br><br>Using the x value directly avoids the need for t=
hat check.</div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Fri, Apr 24, 2015 at 10:35 PM, Pa=
trick Mccorry (PGR) <span dir=3D"ltr"><<a href=3D"mailto:patrick.mccorry=
@newcastle.ac.uk" target=3D"_blank">patrick.mccorry@newcastle.ac.uk</a>>=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"auto">
<div>When computing the diffie Hellman secret - why do you choose the x co-=
ordinate instead of the hash of the secret which is standard practice for s=
tealth addresses=C2=A0<br>
<br>
Sent from my iPhone</div><div><div>
<div><br>
On 24 Apr 2015, at 21:27, Justus Ranvier <<a href=3D"mailto:justus.ranvi=
er@monetas.net" target=3D"_blank">justus.ranvier@monetas.net</a>> wrote:=
<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<p style=3D"margin:0px">-----BEGIN PGP SIGNED MESSAGE-----</p>
<p style=3D"margin:0px">Hash: SHA1</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px"><a href=3D"https://github.com/justusranvier/rfc/blo=
b/payment_code/bips/bip-pc01.mediawiki" target=3D"_blank">https://github.co=
m/justusranvier/rfc/blob/payment_code/bips/bip-pc01.mediawiki</a></p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">This link contains an RFC for a new type of Bitcoin=
address called a "payment code"</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">Payment codes are SPV-friendly alternatives to Dark=
Wallet-style stealth addresses which provide useful features such as positi=
vely identifying senders to recipients and automatically providing for tran=
saction refunds.</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">Payment codes can be publicly advertised and associ=
ated with a real-life identity without causing a loss of financial privacy.=
</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">Compared to stealth addresses, payment codes requir=
e less blockchain data storage.</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">Payment codes require 65 bytes of OP_RETURN data pe=
r sender-recipient pair, while stealth addresses require 40 bytes per trans=
action.</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">-----BEGIN PGP SIGNATURE-----</p>
<p style=3D"margin:0px">Version: GnuPG v1</p>
<p style=3D"margin:0px"><br>
</p>
<p style=3D"margin:0px">iQIcBAEBAgAGBQJVOqCRAAoJECpf2nDq2eYjluEP/RVJk+miDIi=
hY4ilIvUbKvMd</p>
<p style=3D"margin:0px">JLLqHr7Q1dlZyMIG/UqVWdoP5hzg/16B+q2iAB9jXozPnrDp0mg=
gBh6rIGroevAa</p>
<p style=3D"margin:0px">Kqfrs+Rrog1w9auhd67LWORDqav6YIrjTJIxdLxe11IEiq5rWbH=
PNUEDMzdEmHbz</p>
<p style=3D"margin:0px">QfTH7KWAP2BasO5ETXcfu6BcccrXZ3XOKLON2h3NGD/cEDizY+u=
T2k3QN54z+KxG</p>
<p style=3D"margin:0px">NB9scKbzVvsJwkyBrgbV+As9H3k6PnFsojYgAaE9gkp7D2+ahjz=
UiOH5rv6TbbYR</p>
<p style=3D"margin:0px">o2X5MOiTY2/YZEqZPG7IR03ZAgeLVCvXXysjPOfzUKbmTF4w849=
sm8BuhixzDXHo</p>
<p style=3D"margin:0px">2V/HHKoGclIohcODBCWi0tVQXshZt4QkCNJBW5o3nL6Nn2YOp6h=
mw8YKAHnw3E7h</p>
<p style=3D"margin:0px">/wIgk5f+NOLl/iIxoAxAdavEj5P6N4ic+OB6MAjnhEilWfBvCIp=
qWLGNvrtOhEa9</p>
<p style=3D"margin:0px">EnPHcgb4ILBu4OionJhsNpJ/O95C0OEypMm25MIS+rQcV4Uxe5I=
OS2OuT/GreLET</p>
<p style=3D"margin:0px">n/7Y0mJbqYbLBjVsfS+DNjvsgyJl5AxhcMrdVyXJjSYVcCoRhco=
X5Ceidd+YkbHI</p>
<p style=3D"margin:0px">OMs5f63tM1Rgi/WY4Ct80SD5EbULZuu8j1KJ9HPGuMt081JSBH+=
L5isiKuazPeO+</p>
<p style=3D"margin:0px">SGApMBd4Q89fKzL2djae</p>
<p style=3D"margin:0px">=3DDypr</p>
<p style=3D"margin:0px">-----END PGP SIGNATURE-----</p>
</div>
</div>
</blockquote>
</div></div><blockquote type=3D"cite">
<div><span>----------------------------------------------------------------=
--------------</span><br>
<span>One dashboard for servers and applications across Physical-Virtual-Cl=
oud </span>
<br>
<span>Widest out-of-the-box monitoring support with 50+ applications</span>=
<br>
<span>Performance metrics, stats and reports that give you Actionable Insig=
hts</span><br>
<span>Deep dive visibility with transaction tracing using APM Insight.</spa=
n><br>
<span><a href=3D"http://ad.doubleclick.net/ddm/clk/290420510;117567292;y" t=
arget=3D"_blank">http://ad.doubleclick.net/ddm/clk/290420510;117567292;y</a=
></span></div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Bitcoin-development mailing list</span><br>
<span><a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=
=3D"_blank">Bitcoin-development@lists.sourceforge.net</a></span><br>
<span><a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-devel=
opment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitc=
oin-development</a></span><br>
</div>
</blockquote>
</div>
</blockquote></div><br></div>
</div></div></div><br></div>
--90e6ba2121e522df3f05148182e5--
|