MIME-Version: 1.0
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
Subject: [Bitcoin-development] convention/standard for sorting public keys
	for p2sh multisig transactions
Precedence: list

--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&#39;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&#39;m no=
t suggesting forcing the order, just setting a standard to recommend, there=
 doesn&#39;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&#39;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&#39;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--