From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YBYwk-0007KV-NG for bitcoin-development@lists.sourceforge.net; Thu, 15 Jan 2015 01:10:02 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.50 as permitted sender) client-ip=209.85.215.50; envelope-from=elombrozo@gmail.com; helo=mail-la0-f50.google.com; Received: from mail-la0-f50.google.com ([209.85.215.50]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YBYwi-0002wM-UW for bitcoin-development@lists.sourceforge.net; Thu, 15 Jan 2015 01:10:02 +0000 Received: by mail-la0-f50.google.com with SMTP id pn19so11116511lab.9 for ; Wed, 14 Jan 2015 17:09:54 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.154.70 with SMTP id vm6mr7111106lbb.18.1421284194587; Wed, 14 Jan 2015 17:09:54 -0800 (PST) Received: by 10.112.61.106 with HTTP; Wed, 14 Jan 2015 17:09:54 -0800 (PST) Received: by 10.112.61.106 with HTTP; Wed, 14 Jan 2015 17:09:54 -0800 (PST) In-Reply-To: References: <1421257150.8969.4.camel@niftybox.net> <6E575287-887C-4628-834C-282B67AFAA94@eeqj.com> Date: Wed, 14 Jan 2015 17:09:54 -0800 Message-ID: From: Eric Lombrozo To: Andy Alness Content-Type: multipart/alternative; boundary=089e0115f5a48b19c1050ca68366 X-Spam-Score: -0.6 (/) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (elombrozo[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1YBYwi-0002wM-UW Cc: Bitcoin Dev , 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 01:10:02 -0000 --089e0115f5a48b19c1050ca68366 Content-Type: text/plain; charset=UTF-8 Ciphrex was using this convention well before BitPay...and BitPay's BIP32 implementation was at least partly taken from ours. - Eric On Jan 14, 2015 8:03 PM, "Andy Alness" wrote: > Doing same (BitPay convention) for our multisig support. > > On Wed, Jan 14, 2015 at 3:53 PM, Eric Lombrozo > wrote: > > I would highly recommend NOT using Base58 for anything except stuff that > is > > to be copy/pasted by the enduser. > > > > Internally, pubkeys are DER-encoded integers. > > > > - Eric > > > > On Jan 14, 2015 2:54 PM, "Jeffrey Paul" wrote: > >> > >> > >> > On 20150114, at 09: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. > >> > >> To clarify: the raw bytes of the public key itself, not the ascii base58 > >> representation of the pubkey hash - right? > >> > >> -jp > >> > >> -- > >> Jeffrey Paul EEQJ > >> jp@eeqj.com https://eeqj.com > >> +1-800-403-1126 (America) +1-312-361-0355 (Worldwide) > >> 5539 AD00 DE4C 42F3 AFE1 1575 0524 43F4 DF2A 55C2 > >> > >> > >> > >> > ------------------------------------------------------------------------------ > >> 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 > > > > > > > ------------------------------------------------------------------------------ > > 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 > > > > > > -- > Andy Alness > Software Engineer > Coinbase > San Francisco, CA > --089e0115f5a48b19c1050ca68366 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ciphrex was using this convention well before BitPay...and B= itPay's BIP32 implementation was at least partly taken from ours.

- Eric

On Jan 14, 2015 8:03 PM, "Andy Alness"= <andy@coinbase.com> wrote:<= br type=3D"attribution">
Doing same (BitPay c= onvention) for our multisig support.

On Wed, Jan 14, 2015 at 3:53 PM, Eric Lombrozo <elombrozo@gmail.com> wrote:
> I would highly recommend NOT using Base58 for anything except stuff th= at is
> to be copy/pasted by the enduser.
>
> Internally, pubkeys are DER-encoded integers.
>
> - Eric
>
> On Jan 14, 2015 2:54 PM, "Jeffrey Paul" <jp@eeqj.com> wrote:
>>
>>
>> > On 20150114, at 09:39, devrandom <c1.sf-bitcoin@niftybox.net> wrote:
>> >
>> > At CryptoCorp we recommend to our customers that they sort >> > lexicographically by the public key bytes of the leaf public = keys.=C2=A0 i.e.
>> > the same as BitPay.
>>
>> To clarify: the raw bytes of the public key itself, not the ascii = base58
>> representation of the pubkey hash - right?
>>
>> -jp
>>
>> --
>> Jeffrey Paul=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 EEQJ
>> jp@eeqj.com=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://eeqj.com
>> +1-800-40= 3-1126 (America)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 +1-312-361= -0355 (Worldwide)
>> 5539 AD00 DE4C 42F3 AFE1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1575 0524 43F4 DF2A 55C2
>>
>>
>>
>> ------------------------------------------------------------------= ------------
>> 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 A= shburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidt= h.
>> Higher redundancy.Lower latency.Increased capacity.Completely comp= liant.
>> http://p= .sf.net/sfu/gigenet
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitco= in-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/b= itcoin-development
>
>
> ----------------------------------------------------------------------= --------
> 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 Ashbu= rn.
> Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely complian= t.
> http://p.sf.= net/sfu/gigenet
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-d= evelopment@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitco= in-development
>



--
Andy Alness
Software Engineer
Coinbase
San Francisco, CA
--089e0115f5a48b19c1050ca68366--