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 ) id 1YBTLv-0005aS-GN for bitcoin-development@lists.sourceforge.net; Wed, 14 Jan 2015 19:11:39 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of haskoin.com designates 192.64.117.33 as permitted sender) client-ip=192.64.117.33; envelope-from=root@haskoin.com; helo=erelay4.ox.registrar-servers.com; Received: from erelay4.ox.registrar-servers.com ([192.64.117.33]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1YBTLu-00057s-24 for bitcoin-development@lists.sourceforge.net; Wed, 14 Jan 2015 19:11:39 +0000 Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 9982E2207EFF; Wed, 14 Jan 2015 18:58:11 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IK5t8Zs3-PtZ; Wed, 14 Jan 2015 13:58:10 -0500 (EST) Received: from imap10.ox.privateemail.com (imap10.ox.privateemail.com [192.64.116.221]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by erelay1.ox.registrar-servers.com (Postfix) with ESMTPS id BDA472207EE0; Wed, 14 Jan 2015 13:58:10 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 2C3E92400AA; Wed, 14 Jan 2015 13:58:10 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id b0ZHU2s4P5WG; Wed, 14 Jan 2015 13:58:10 -0500 (EST) Received: from [192.168.164.57] (unknown [46.7.118.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 475E82400D4; Wed, 14 Jan 2015 13:58:09 -0500 (EST) Message-ID: <54B6BC3F.6050805@haskoin.com> Date: Wed, 14 Jan 2015 18:58:07 +0000 From: Jean-Pierre Rupp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: devrandom , Ruben de Vries References: <1421257150.8969.4.camel@niftybox.net> In-Reply-To: <1421257150.8969.4.camel@niftybox.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.5 (-) 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_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1YBTLu-00057s-24 Cc: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 19:11:39 -0000 We in Haskoin do the same. On 14/01/15 17:39, devrandom wrote: > At CryptoCorp we recommend to our customers that they sort > lexicographically by the public key bytes of the leaf public keys. i.e. > the same as BitPay. -- Be Happy :)