Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jbrown@bluedroplet.com>) id 1YBjRT-0003tC-4B
	for bitcoin-development@lists.sourceforge.net;
	Thu, 15 Jan 2015 12:22:27 +0000
X-ACL-Warn: 
Received: from mail-ig0-f171.google.com ([209.85.213.171])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YBjRR-0005Pf-5w
	for bitcoin-development@lists.sourceforge.net;
	Thu, 15 Jan 2015 12:22:26 +0000
Received: by mail-ig0-f171.google.com with SMTP id z20so27650485igj.4
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 15 Jan 2015 04:22:19 -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:date
	:message-id:subject:from:to:cc:content-type;
	bh=3nlmOfR3hz1XWnOdXdVs/c5apGrmJSM9/xsw4eXJ6JQ=;
	b=gjNRy8XphFpCjF6gdBZEVlqHchrFOSiP1oKW1BA91llVzCX1mNr5I3TLLaMlupXryS
	rt2xAY9iZOJ1WSxuVswtQ8GCrpmSCEa2V8EioitxpIvkNaLaSOff2m2E3cKbZqVXMK5H
	cdvHVAoUNBwpZLxmw0ysNeu1XWqJLf4vtbjcCggJI8q4RJ+PNSc4Xo6SM5Dz4BxBJj7G
	8doMuQvWbzM67NvACPXeykXm9EhcqlG/dGQo2lEE+EQTVpBWkwPS5BzJ4QYeDmPE5Q8p
	9MdXQydH1jSZjIrnLKsh6Z2XsPN/SA1ykJUCVT4JQ7cubtg0p8Wf4I7l00BcD/YGan0A
	1fLw==
X-Gm-Message-State: ALoCoQlZBVQg6Euabp+8DwlfNQoi98f1/PigseqttxCI+VLneUKEGqNYJUalIg9HMQPta9DRl0mM
MIME-Version: 1.0
X-Received: by 10.107.12.214 with SMTP id 83mr9397422iom.61.1421323155419;
	Thu, 15 Jan 2015 03:59:15 -0800 (PST)
Received: by 10.64.12.131 with HTTP; Thu, 15 Jan 2015 03:59:15 -0800 (PST)
X-Originating-IP: [118.69.18.61]
In-Reply-To: <CAJHLa0OdLFK+D2WF8UET7WYF_FcXENd_Vqx-7JZ034Zux6qgrA@mail.gmail.com>
References: <CABETNRtquBWEZZ=jOcWojcgMTpjU5nWP9p74DArLxOXqqQT7og@mail.gmail.com>
	<CAJHLa0OdLFK+D2WF8UET7WYF_FcXENd_Vqx-7JZ034Zux6qgrA@mail.gmail.com>
Date: Thu, 15 Jan 2015 18:59:15 +0700
Message-ID: <CABaYTy9U41_chiD-+MCY+ixKO-eA_Ch7LDv7uLvEgqzWy0x1xg@mail.gmail.com>
From: Jonathan Brown <jbrown@bluedroplet.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a113fc0eeca3fb2050caf9502
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: 1YBjRR-0005Pf-5w
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Ruben de Vries <ruben@blocktrail.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 12:22:27 -0000

--001a113fc0eeca3fb2050caf9502
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In BIP45 it mentions "lexicographically sorting the public keys".

https://github.com/bitcoin/bips/blob/master/bip-0045.mediawiki#Address_Gene=
ration_Procedure

On 15 January 2015 at 03:32, Jeff Garzik <jgarzik@bitpay.com> wrote:

> 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 key=
s
>> that would make it easier for services that implement some form of multi=
sig
>> to be compatible with each other without much hassle and making it possi=
ble
>> 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 no=
t
>> 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
>>
>>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>
>
> -------------------------------------------------------------------------=
-----
> 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
>
>

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

<div dir=3D"ltr">In BIP45 it mentions &quot;lexicographically sorting the p=
ublic keys&quot;.<br><br><a href=3D"https://github.com/bitcoin/bips/blob/ma=
ster/bip-0045.mediawiki#Address_Generation_Procedure">https://github.com/bi=
tcoin/bips/blob/master/bip-0045.mediawiki#Address_Generation_Procedure</a><=
br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 15 Ja=
nuary 2015 at 03:32, Jeff Garzik <span dir=3D"ltr">&lt;<a href=3D"mailto:jg=
arzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Sounds like this warra=
nts a micro-BIP just to get everybody on the same page.<div><br></div></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div><div class=
=3D"h5">On Wed, Jan 14, 2015 at 11:37 AM, Ruben de Vries <span dir=3D"ltr">=
&lt;<a href=3D"mailto:ruben@blocktrail.com" target=3D"_blank">ruben@blocktr=
ail.com</a>&gt;</span> wrote:<br></div></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div><div class=3D"h5"><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 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" sty=
le=3D"font-family:verdana,sans-serif">If there would be a standard (recomme=
nded) 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 with=
out much hassle and making it possible to import keys from one service to a=
nother.</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 not suggesting forcing the order, just setting a stand=
ard to recommend, there doesn&#39;t seem to be much reason for (new) servic=
es to not follow that recommendation.</div><div class=3D"gmail_default" sty=
le=3D"font-family:verdana,sans-serif"><br></div><div class=3D"gmail_default=
" style=3D"font-family:verdana,sans-serif">Ryan from BitPay broad this up b=
efore (<a href=3D"https://sourceforge.net/p/bitcoin/mailman/message/3209295=
8/" target=3D"_blank">https://sourceforge.net/p/bitcoin/mailman/message/320=
92958/</a>) and in bitcore they&#39;ve implemented lexicographical sorting =
on the hex of the public key.</div><div class=3D"gmail_default" style=3D"fo=
nt-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 bitc=
ore is currently my only reference.</div><span><font color=3D"#888888"><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:verdana,s=
ans-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></div></div><span class=3D"">------------------------------------------=
------------------------------------<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" target=3D"_bla=
nk">Bitcoin-development@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></span></blockquote></div><span class=3D"HOEnZb"><font color=3D"#888888=
"><br><br clear=3D"all"><div><br></div>-- <br><div>Jeff Garzik<br>Bitcoin c=
ore developer and open source evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=
=A0<a href=3D"https://bitpay.com/" target=3D"_blank">https://bitpay.com/</a=
></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></div>

--001a113fc0eeca3fb2050caf9502--