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 1YBUYv-00085F-Ph for bitcoin-development@lists.sourceforge.net; Wed, 14 Jan 2015 20:29:09 +0000 X-ACL-Warn: Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YBUYs-0005mp-2W for bitcoin-development@lists.sourceforge.net; Wed, 14 Jan 2015 20:29:09 +0000 Received: by mail-we0-f175.google.com with SMTP id k11so10946215wes.6 for ; Wed, 14 Jan 2015 12:28:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5hG6v+ZACnB9plq5+04nnED0VpPxReqCJh+oRozkcPE=; b=RVo8GKznlzmGjAGKeTrYOstGowAmGE/SFfLBENCfbkoRXv90eEvpvRFf+1FvfBf9A0 vxVNXlZ8fdHG588WTfmJajv6MIhtLIS/cCV2Oxc4h5pdKtR/1TJYcOyrt1WU2Ngri3xr 3ACJFnVNrISIVbpxMUO3/xGlOi74N1E/WKgk3EQLWSD5XOTTjbxSoVLlPC7iZWxPHFrQ PBRAEoCWgzcIpNIEztm4hiy40g7CuS/G0uaYBe1OT53/bQgVxAdkYsrE13NpUJe5CRa6 mCPEnwQK7X7peiETS4YW/66fuA2wdIx+3yvrP4LIZoVDdZApj7nAOiZ8lActDgKq9lJY pDNg== X-Gm-Message-State: ALoCoQmqZlcFZn+bMuv6GEJqb14VnclMK7jMIZRKwWc0gXEsuEu5a4MHJn0uktSijAT0YbTOGRz0 X-Received: by 10.180.205.163 with SMTP id lh3mr54177962wic.63.1421265538321; Wed, 14 Jan 2015 11:58:58 -0800 (PST) Received: from tetra.site ([185.68.216.100]) by mx.google.com with ESMTPSA id g2sm23347015wjn.11.2015.01.14.11.58.56 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jan 2015 11:58:57 -0800 (PST) Message-ID: <54B6CA7E.3070600@gk2.sk> Date: Wed, 14 Jan 2015 20:58:54 +0100 From: Pavol Rusnak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Jeffrey Paul , devrandom References: <1421257150.8969.4.camel@niftybox.net> <6E575287-887C-4628-834C-282B67AFAA94@eeqj.com> In-Reply-To: <6E575287-887C-4628-834C-282B67AFAA94@eeqj.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1YBUYs-0005mp-2W Cc: bitcoin-development@lists.sourceforge.net, Ruben de Vries 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 20:29:09 -0000 On 14/01/15 20:27, Jeffrey Paul wrote: > To clarify: the raw bytes of the public key itself, not the ascii base58 representation of the pubkey hash - right? Could you give an example of two pubkeys where the following condition is met? raw(pubkey1) > raw(pubkey2) and base58(pubkey1) < base58(pubkey2) -- Best Regards / S pozdravom, Pavol Rusnak