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; 
MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] convention/standard for sorting public
 keys for p2sh multisig transactions
Precedence: list

--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">&lt;<a href=3D"mailto:ruben@blocktrail.com" target=3D"_blank=
">ruben@blocktrail.com</a>&gt;</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&#39;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&#39;m=
 not suggesting forcing the order, just setting a standard to recommend, th=
ere doesn&#39;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&#39;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&#39;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--