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
|
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 <jgarzik@bitpay.com>) id 1YBUd4-0007eF-JG
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Jan 2015 20:33:27 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.214.177 as permitted sender)
client-ip=209.85.214.177; envelope-from=jgarzik@bitpay.com;
helo=mail-ob0-f177.google.com;
Received: from mail-ob0-f177.google.com ([209.85.214.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YBUd0-0000sW-UJ
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Jan 2015 20:33:26 +0000
Received: by mail-ob0-f177.google.com with SMTP id uy5so9776613obc.8
for <bitcoin-development@lists.sourceforge.net>;
Wed, 14 Jan 2015 12:33:17 -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=dvit681W5PHsmJs1mcYfMR9QEXov/Kv7pC2V1iBuElU=;
b=HTHWcPIwEqgwvtjzagpTQXAWXkvdQPl6iSU99SvVL91fPb98v2cV7uiksc+T3FqkCl
HbBqgsrNmBsfa0esldco3r0v/zfn4WO5emXCsqojaiRRb3iEzGFlXPV7ALhc137axyh6
ZLSoAfnONxw7cNaW5QkpINMstuOb6dnBQ5aUBCE7siOyA2YJjpXGq2467yldQ2JxGUWR
rIK6EoRhT8K3xVWXpKKSsGk2Mw3VcHN81T7vHUdKgfdq9XlF0NktN2dyHasRH/zElq8f
pNhcTEzw5rMahhpHgMtIc+vpD3c8nw+HuexQy8sTy65gjv+6IHOAS77wfltN62LBRkyJ
0dLQ==
X-Gm-Message-State: ALoCoQnLJarKuQm31f+0A//Nsf30Nwj6f1ciu5t7D00YgtBxHhD2LbAiWitHSiG4d9Rm/TxPh2+U
X-Received: by 10.60.52.72 with SMTP id r8mr3664038oeo.75.1421267597475; Wed,
14 Jan 2015 12:33:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.209.9 with HTTP; Wed, 14 Jan 2015 12:32:57 -0800 (PST)
In-Reply-To: <CABETNRtquBWEZZ=jOcWojcgMTpjU5nWP9p74DArLxOXqqQT7og@mail.gmail.com>
References: <CABETNRtquBWEZZ=jOcWojcgMTpjU5nWP9p74DArLxOXqqQT7og@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Wed, 14 Jan 2015 15:32:57 -0500
Message-ID: <CAJHLa0OdLFK+D2WF8UET7WYF_FcXENd_Vqx-7JZ034Zux6qgrA@mail.gmail.com>
To: Ruben de Vries <ruben@blocktrail.com>
Content-Type: multipart/alternative; boundary=001a11333436475b05050ca2a668
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 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: 1YBUd0-0000sW-UJ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: Wed, 14 Jan 2015 20:33:27 -0000
--001a11333436475b05050ca2a668
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Sounds like this warrants a micro-BIP just to get everybody on the same
page.
On Wed, Jan 14, 2015 at 11:37 AM, Ruben de Vries <ruben@blocktrail.com>
wrote:
> For p2sh multisig TXs the order of the public keys affect the hash and
> there doesn't seem to be an agreed upon way of sorting the public keys.
>
> If there would be a standard (recommended) way of sorting the public keys
> that would make it easier for services that implement some form of multis=
ig
> to be compatible with each other without much hassle and making it possib=
le
> to import keys from one service to another.
>
> I'm not suggesting forcing the order, just setting a standard to
> recommend, there doesn't seem to be much reason for (new) services to not
> follow that recommendation.
>
> Ryan from BitPay broad this up before (
> https://sourceforge.net/p/bitcoin/mailman/message/32092958/) and in
> bitcore they've implemented lexicographical sorting on the hex of the
> public key.
> In a short search I can't find any other library that has a sorting
> function, let alone using it by default, so bitcore is currently my only
> reference.
>
>
> =E2=80=8BRuben de Vries
> =E2=80=8BCTO, BlockTrail
>
>
> -------------------------------------------------------------------------=
-----
> 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
>
>
--=20
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--001a11333436475b05050ca2a668
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Sounds like this warrants a micro-BIP just to get everybod=
y on the same page.<div><br></div></div><div class=3D"gmail_extra"><br><div=
class=3D"gmail_quote">On Wed, Jan 14, 2015 at 11:37 AM, Ruben de Vries <sp=
an dir=3D"ltr"><<a href=3D"mailto:ruben@blocktrail.com" target=3D"_blank=
">ruben@blocktrail.com</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verd=
ana,sans-serif">For p2sh multisig TXs the order of the public keys affect t=
he hash and there doesn't seem to be an agreed upon way of sorting the =
public keys.</div><div class=3D"gmail_default" style=3D"font-family:verdana=
,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:ve=
rdana,sans-serif">If there would be a standard (recommended) way of sorting=
the public keys that would make it easier for services that implement some=
form of multisig to be compatible with each other without much hassle and =
making it possible to import keys from one service to another.</div><div cl=
ass=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><br></div><d=
iv class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">I'm=
not suggesting forcing the order, just setting a standard to recommend, th=
ere doesn't seem to be much reason for (new) services to not follow tha=
t recommendation.</div><div class=3D"gmail_default" style=3D"font-family:ve=
rdana,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-fami=
ly:verdana,sans-serif">Ryan from BitPay broad this up before (<a href=3D"ht=
tps://sourceforge.net/p/bitcoin/mailman/message/32092958/" target=3D"_blank=
">https://sourceforge.net/p/bitcoin/mailman/message/32092958/</a>) and in b=
itcore they've implemented lexicographical sorting on the hex of the pu=
blic key.</div><div class=3D"gmail_default" style=3D"font-family:verdana,sa=
ns-serif">In a short search I can't find any other library that has a s=
orting function, let alone using it by default, so bitcore is currently my =
only reference.</div><span class=3D"HOEnZb"><font color=3D"#888888"><div cl=
ass=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><br></div><d=
iv><br></div><div class=3D"gmail_default" style=3D"font-family:verdana,sans=
-serif">=E2=80=8BRuben de Vries</div><div class=3D"gmail_default" style=3D"=
font-family:verdana,sans-serif">=E2=80=8BCTO, BlockTrail</div>
</font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.<br>
GigeNET is offering a free month of service with a new server in Ashburn.<b=
r>
Choose from 2 high performing configs, both with 100TB of bandwidth.<br>
Higher redundancy.Lower latency.Increased capacity.Completely compliant.<br=
>
<a href=3D"http://p.sf.net/sfu/gigenet" target=3D"_blank">http://p.sf.net/s=
fu/gigenet</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><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature">Jeff Garzik<br>Bitcoin core developer and open sourc=
e evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.=
com/" target=3D"_blank">https://bitpay.com/</a></div>
</div>
--001a11333436475b05050ca2a668--
|
