From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1YBjcb-0004Mt-Io for bitcoin-development@lists.sourceforge.net; Thu, 15 Jan 2015 12:33:57 +0000 Received-SPF: pass (sog-mx-1.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-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1YBjcZ-0005w7-Qh for bitcoin-development@lists.sourceforge.net; Thu, 15 Jan 2015 12:33:57 +0000 Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id D69A32205B20; Thu, 15 Jan 2015 12:33:49 +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 BxId2fPGfzuU; Thu, 15 Jan 2015 07:33:46 -0500 (EST) Received: from imap2.ox.privateemail.com (imap2.ox.privateemail.com [198.187.29.234]) (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 7BA0A2205A94; Thu, 15 Jan 2015 07:33:46 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id BE3AF8C0080; Thu, 15 Jan 2015 07:33:45 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at imap2.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap2.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rOgWrZM-TZ_P; Thu, 15 Jan 2015 07:33:45 -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 491FE8C007D; Thu, 15 Jan 2015 07:33:44 -0500 (EST) Message-ID: <54B7B3A3.1000809@haskoin.com> Date: Thu, 15 Jan 2015 12:33:39 +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: Matt Whitlock , bitcoin-development@lists.sourceforge.net References: <6E575287-887C-4628-834C-282B67AFAA94@eeqj.com> <3382316.6TbFyFjyI6@crushinator> In-Reply-To: <3382316.6TbFyFjyI6@crushinator> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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: 1YBjcZ-0005w7-Qh Cc: Ruben de Vries , Jeffrey Paul 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: Thu, 15 Jan 2015 12:33:57 -0000 A public key is a point in the elliptic curve. As such it has an X and a Y component. Its serialization is described very succintly here: https://en.bitcoin.it/wiki/Protocol_specification#Signatures On 15/01/15 01:17, Matt Whitlock wrote: > I thought pubkeys were represented as raw integers (i.e., they're embed= ded in Script as a push operation whose payload is the raw bytes of the b= ig-endian representation of the integer). As far as I know, DER encoding = is only used for signatures. Am I mistaken? --=20 Be Happy :)