summaryrefslogtreecommitdiff
path: root/5d/beed12584a95bfe13ba91a0872591fe3fd0b33
blob: 879daffe07f2ca51ea32018afbf7d8086076cd17 (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
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 <elombrozo@gmail.com>) id 1YBYwk-0007KV-NG
	for bitcoin-development@lists.sourceforge.net;
	Thu, 15 Jan 2015 01:10:02 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.50 as permitted sender)
	client-ip=209.85.215.50; envelope-from=elombrozo@gmail.com;
	helo=mail-la0-f50.google.com; 
Received: from mail-la0-f50.google.com ([209.85.215.50])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YBYwi-0002wM-UW
	for bitcoin-development@lists.sourceforge.net;
	Thu, 15 Jan 2015 01:10:02 +0000
Received: by mail-la0-f50.google.com with SMTP id pn19so11116511lab.9
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 14 Jan 2015 17:09:54 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.154.70 with SMTP id vm6mr7111106lbb.18.1421284194587;
	Wed, 14 Jan 2015 17:09:54 -0800 (PST)
Received: by 10.112.61.106 with HTTP; Wed, 14 Jan 2015 17:09:54 -0800 (PST)
Received: by 10.112.61.106 with HTTP; Wed, 14 Jan 2015 17:09:54 -0800 (PST)
In-Reply-To: <CALKy-wreXNohc_Pe_DLBS1cXoS-3j8C_F7WsKuU=CYYKF9NB1Q@mail.gmail.com>
References: <CABETNRtquBWEZZ=jOcWojcgMTpjU5nWP9p74DArLxOXqqQT7og@mail.gmail.com>
	<1421257150.8969.4.camel@niftybox.net>
	<6E575287-887C-4628-834C-282B67AFAA94@eeqj.com>
	<CABr1YTdqUxBs3+dMmtZ5dQvxP8MBFgttCdJ9cuvy10LdwAKaYQ@mail.gmail.com>
	<CALKy-wreXNohc_Pe_DLBS1cXoS-3j8C_F7WsKuU=CYYKF9NB1Q@mail.gmail.com>
Date: Wed, 14 Jan 2015 17:09:54 -0800
Message-ID: <CABr1YTc+vBVmn5PgW1b8udg2YCFwaUOAMS8dfRRtO-OrxNSn-w@mail.gmail.com>
From: Eric Lombrozo <elombrozo@gmail.com>
To: Andy Alness <andy@coinbase.com>
Content-Type: multipart/alternative; boundary=089e0115f5a48b19c1050ca68366
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
	(elombrozo[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: 1YBYwi-0002wM-UW
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Ruben de Vries <ruben@blocktrail.com>, Jeffrey Paul <jp@eeqj.com>
Subject: Re: [Bitcoin-development] convention/standard for sorting public
 keys for p2sh multisig transactions
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, 15 Jan 2015 01:10:02 -0000

--089e0115f5a48b19c1050ca68366
Content-Type: text/plain; charset=UTF-8

Ciphrex was using this convention well before BitPay...and BitPay's BIP32
implementation was at least partly taken from ours.

- Eric
On Jan 14, 2015 8:03 PM, "Andy Alness" <andy@coinbase.com> wrote:

> Doing same (BitPay convention) for our multisig support.
>
> On Wed, Jan 14, 2015 at 3:53 PM, Eric Lombrozo <elombrozo@gmail.com>
> wrote:
> > I would highly recommend NOT using Base58 for anything except stuff that
> is
> > to be copy/pasted by the enduser.
> >
> > Internally, pubkeys are DER-encoded integers.
> >
> > - Eric
> >
> > On Jan 14, 2015 2:54 PM, "Jeffrey Paul" <jp@eeqj.com> wrote:
> >>
> >>
> >> > On 20150114, at 09:39, devrandom <c1.sf-bitcoin@niftybox.net> wrote:
> >> >
> >> > At CryptoCorp we recommend to our customers that they sort
> >> > lexicographically by the public key bytes of the leaf public keys.
> i.e.
> >> > the same as BitPay.
> >>
> >> To clarify: the raw bytes of the public key itself, not the ascii base58
> >> representation of the pubkey hash - right?
> >>
> >> -jp
> >>
> >> --
> >> Jeffrey Paul                                                      EEQJ
> >> jp@eeqj.com                                           https://eeqj.com
> >> +1-800-403-1126 (America)                  +1-312-361-0355 (Worldwide)
> >> 5539 AD00 DE4C 42F3 AFE1                      1575 0524 43F4 DF2A 55C2
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> >> GigeNET is offering a free month of service with a new server in
> Ashburn.
> >> Choose from 2 high performing configs, both with 100TB of bandwidth.
> >> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> >> http://p.sf.net/sfu/gigenet
> >> _______________________________________________
> >> Bitcoin-development mailing list
> >> Bitcoin-development@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
> >
> >
> ------------------------------------------------------------------------------
> > New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> > GigeNET is offering a free month of service with a new server in Ashburn.
> > Choose from 2 high performing configs, both with 100TB of bandwidth.
> > Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> > http://p.sf.net/sfu/gigenet
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
>
>
> --
> Andy Alness
> Software Engineer
> Coinbase
> San Francisco, CA
>

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

<p dir=3D"ltr">Ciphrex was using this convention well before BitPay...and B=
itPay&#39;s BIP32 implementation was at least partly taken from ours.</p>
<p dir=3D"ltr">- Eric</p>
<div class=3D"gmail_quote">On Jan 14, 2015 8:03 PM, &quot;Andy Alness&quot;=
 &lt;<a href=3D"mailto:andy@coinbase.com">andy@coinbase.com</a>&gt; wrote:<=
br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Doing same (BitPay c=
onvention) for our multisig support.<br>
<br>
On Wed, Jan 14, 2015 at 3:53 PM, Eric Lombrozo &lt;<a href=3D"mailto:elombr=
ozo@gmail.com">elombrozo@gmail.com</a>&gt; wrote:<br>
&gt; I would highly recommend NOT using Base58 for anything except stuff th=
at is<br>
&gt; to be copy/pasted by the enduser.<br>
&gt;<br>
&gt; Internally, pubkeys are DER-encoded integers.<br>
&gt;<br>
&gt; - Eric<br>
&gt;<br>
&gt; On Jan 14, 2015 2:54 PM, &quot;Jeffrey Paul&quot; &lt;<a href=3D"mailt=
o:jp@eeqj.com">jp@eeqj.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; &gt; On 20150114, at 09:39, devrandom &lt;<a href=3D"mailto:c1.sf-=
bitcoin@niftybox.net">c1.sf-bitcoin@niftybox.net</a>&gt; wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; At CryptoCorp we recommend to our customers that they sort<br=
>
&gt;&gt; &gt; lexicographically by the public key bytes of the leaf public =
keys.=C2=A0 i.e.<br>
&gt;&gt; &gt; the same as BitPay.<br>
&gt;&gt;<br>
&gt;&gt; To clarify: the raw bytes of the public key itself, not the ascii =
base58<br>
&gt;&gt; representation of the pubkey hash - right?<br>
&gt;&gt;<br>
&gt;&gt; -jp<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Jeffrey Paul=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 EEQJ<br>
&gt;&gt; <a href=3D"mailto:jp@eeqj.com">jp@eeqj.com</a>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https=
://eeqj.com" target=3D"_blank">https://eeqj.com</a><br>
&gt;&gt; <a href=3D"tel:%2B1-800-403-1126" value=3D"+18004031126">+1-800-40=
3-1126</a> (America)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 <a href=3D"tel:%2B1-312-361-0355" value=3D"+13123610355">+1-312-361=
-0355</a> (Worldwide)<br>
&gt;&gt; 5539 AD00 DE4C 42F3 AFE1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1575 0524 43F4 DF2A 55C2<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------------------------------------------=
------------<br>
&gt;&gt; New Year. New Location. New Benefits. New Data Center in Ashburn, =
VA.<br>
&gt;&gt; GigeNET is offering a free month of service with a new server in A=
shburn.<br>
&gt;&gt; Choose from 2 high performing configs, both with 100TB of bandwidt=
h.<br>
&gt;&gt; Higher redundancy.Lower latency.Increased capacity.Completely comp=
liant.<br>
&gt;&gt; <a href=3D"http://p.sf.net/sfu/gigenet" target=3D"_blank">http://p=
.sf.net/sfu/gigenet</a><br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Bitcoin-development mailing list<br>
&gt;&gt; <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitco=
in-development@lists.sourceforge.net</a><br>
&gt;&gt; <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/b=
itcoin-development</a><br>
&gt;<br>
&gt;<br>
&gt; ----------------------------------------------------------------------=
--------<br>
&gt; New Year. New Location. New Benefits. New Data Center in Ashburn, VA.<=
br>
&gt; GigeNET is offering a free month of service with a new server in Ashbu=
rn.<br>
&gt; Choose from 2 high performing configs, both with 100TB of bandwidth.<b=
r>
&gt; Higher redundancy.Lower latency.Increased capacity.Completely complian=
t.<br>
&gt; <a href=3D"http://p.sf.net/sfu/gigenet" target=3D"_blank">http://p.sf.=
net/sfu/gigenet</a><br>
&gt; _______________________________________________<br>
&gt; Bitcoin-development mailing list<br>
&gt; <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
&gt; <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
&gt;<br>
<br>
<br>
<br>
--<br>
Andy Alness<br>
Software Engineer<br>
Coinbase<br>
San Francisco, CA<br>
</blockquote></div>

--089e0115f5a48b19c1050ca68366--