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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ruben@blockcorp.com>) id 1YBRKD-0008Nx-W3
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Jan 2015 17:01:46 +0000
Received: from mail-wg0-f54.google.com ([74.125.82.54])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YBRK8-0006bD-Sa
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Jan 2015 17:01:45 +0000
Received: by mail-wg0-f54.google.com with SMTP id z12so10086696wgg.13
for <bitcoin-development@lists.sourceforge.net>;
Wed, 14 Jan 2015 09:01:34 -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:date:message-id:subject:from:to
:content-type;
bh=0DSeEk6DDI6arSgJvqxyAEn4fHA7ZcXqCgeZStAkK6Q=;
b=cjPAEOBagfSxnzwYgNHPESgtwpBMZCkflZOcrUJYQuucHRLgTTqdW4GktPfXEYHe0A
uHBFJeRmwUcBk6880Dwx5NY7vpEX7NObvn65hyxvqfQ72GcpYL5yC5AmlH33t0zcYw55
9jPh/gExmJyJ8rFzRsYT41CIn3ARtvL8NR+9pDyE/e0nYQ6XRhNtrVcI1Dl0Y7MDF2Gs
CWY+lUOZliqDWq6u5dKEEDe0ZKN0qfY0SIoxDbL6qt5jmlrfOkx0+ExaY7aSWuGlvs6b
7QanvH7Tap3tNA0gwo6w2Anq5A6Mu9t4SqA0Jv/TIvFHizBq7t/20lC2iCFyYx7fTs1Y
Uicg==
X-Gm-Message-State: ALoCoQl4JZVZfmLK7vCMSVKCxGyjytqyOfSAoVgmK+s2VuuhtHOyHdHC9AofLyck/VgxFzrPzk8f
MIME-Version: 1.0
X-Received: by 10.181.12.17 with SMTP id em17mr52040635wid.45.1421253430783;
Wed, 14 Jan 2015 08:37:10 -0800 (PST)
Received: by 10.27.11.34 with HTTP; Wed, 14 Jan 2015 08:37:10 -0800 (PST)
Date: Wed, 14 Jan 2015 17:37:10 +0100
Message-ID: <CABETNRtquBWEZZ=jOcWojcgMTpjU5nWP9p74DArLxOXqqQT7og@mail.gmail.com>
From: Ruben de Vries <ruben@blocktrail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=f46d043893c3e0c874050c9f592e
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: 1YBRK8-0006bD-Sa
Subject: [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 17:01:46 -0000
--f46d043893c3e0c874050c9f592e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 multisig
to be compatible with each other without much hassle and making it possible
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
--f46d043893c3e0c874050c9f592e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">For p2sh multisig TXs the order of the public keys affect the h=
ash and there doesn't seem to be an agreed upon way of sorting the publ=
ic keys.</div><div class=3D"gmail_default" style=3D"font-family:verdana,san=
s-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:verdan=
a,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 for=
m of multisig to be compatible with each other without much hassle and maki=
ng it possible to import keys from one service to another.</div><div class=
=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><br></div><div =
class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">I'm no=
t 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 r=
ecommendation.</div><div class=3D"gmail_default" style=3D"font-family:verda=
na,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:=
verdana,sans-serif">Ryan from BitPay broad this up before (<a href=3D"https=
://sourceforge.net/p/bitcoin/mailman/message/32092958/">https://sourceforge=
.net/p/bitcoin/mailman/message/32092958/</a>) and in bitcore they've im=
plemented lexicographical sorting on the hex of the public key.</div><div c=
lass=3D"gmail_default" style=3D"font-family:verdana,sans-serif">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.</div>=
<div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><br><=
/div><div><br></div><div class=3D"gmail_default" style=3D"font-family:verda=
na,sans-serif">=E2=80=8BRuben de Vries</div><div class=3D"gmail_default" st=
yle=3D"font-family:verdana,sans-serif">=E2=80=8BCTO, BlockTrail</div>
</div>
--f46d043893c3e0c874050c9f592e--
|
