From: Eric Lombrozo <elombrozo@gmail•com>
To: Andy Alness <andy@coinbase•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Ruben de Vries <ruben@blocktrail•com>, Jeffrey Paul <jp@eeqj•com>
Subject: Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions
Date: Wed, 14 Jan 2015 17:09:54 -0800 [thread overview]
Message-ID: <CABr1YTc+vBVmn5PgW1b8udg2YCFwaUOAMS8dfRRtO-OrxNSn-w@mail.gmail.com> (raw)
In-Reply-To: <CALKy-wreXNohc_Pe_DLBS1cXoS-3j8C_F7WsKuU=CYYKF9NB1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]
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" <andy@coinbase•com> wrote:
> Doing same (BitPay convention) 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 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" <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.
> 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
>
[-- Attachment #2: Type: text/html, Size: 4245 bytes --]
next prev parent reply other threads:[~2015-01-15 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 16:37 Ruben de Vries
2015-01-14 17:39 ` devrandom
2015-01-14 18:00 ` Eric Lombrozo
2015-01-14 18:58 ` Jean-Pierre Rupp
2015-01-14 19:27 ` Jeffrey Paul
2015-01-14 19:58 ` Pavol Rusnak
2015-01-14 23:53 ` Eric Lombrozo
[not found] ` <CALKy-wreXNohc_Pe_DLBS1cXoS-3j8C_F7WsKuU=CYYKF9NB1Q@mail.gmail.com>
2015-01-15 1:09 ` Eric Lombrozo [this message]
2015-01-15 1:17 ` Matt Whitlock
2015-01-15 12:33 ` Jean-Pierre Rupp
[not found] ` <CA+s+GJCsta-FesGv7zW_i2pEtZM5U20ZqP2V_Oog_LBtQBbe-w@mail.gmail.com>
2015-01-16 10:16 ` Ruben de Vries
2015-01-16 16:34 ` Thomas Kerin
2015-01-16 17:09 ` Alan Reiner
2015-01-14 20:32 ` Jeff Garzik
2015-01-15 11:59 ` Jonathan Brown
2015-01-16 18:40 Jean-Pierre Rupp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABr1YTc+vBVmn5PgW1b8udg2YCFwaUOAMS8dfRRtO-OrxNSn-w@mail.gmail.com \
--to=elombrozo@gmail$(echo .)com \
--cc=andy@coinbase$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jp@eeqj$(echo .)com \
--cc=ruben@blocktrail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox