From: Jeff Garzik <jgarzik@bitpay•com>
To: Ruben de Vries <ruben@blocktrail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions
Date: Wed, 14 Jan 2015 15:32:57 -0500 [thread overview]
Message-ID: <CAJHLa0OdLFK+D2WF8UET7WYF_FcXENd_Vqx-7JZ034Zux6qgrA@mail.gmail.com> (raw)
In-Reply-To: <CABETNRtquBWEZZ=jOcWojcgMTpjU5nWP9p74DArLxOXqqQT7og@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
Sounds like this warrants a micro-BIP just to get everybody on the same
page.
On Wed, Jan 14, 2015 at 11:37 AM, Ruben de Vries <ruben@blocktrail•com>
wrote:
> For p2sh multisig TXs the order of the public keys affect the hash and
> there doesn't seem to be an agreed upon way of sorting the public keys.
>
> If there would be a standard (recommended) way of sorting the public keys
> that would make it easier for services that implement some form of multisig
> to be compatible with each other without much hassle and making it possible
> to import keys from one service to another.
>
> I'm not suggesting forcing the order, just setting a standard to
> recommend, there doesn't seem to be much reason for (new) services to not
> follow that recommendation.
>
> Ryan from BitPay broad this up before (
> https://sourceforge.net/p/bitcoin/mailman/message/32092958/) and in
> bitcore they've implemented lexicographical sorting on the hex of the
> public key.
> In a short search I can't find any other library that has a sorting
> function, let alone using it by default, so bitcore is currently my only
> reference.
>
>
> Ruben de Vries
> CTO, BlockTrail
>
>
> ------------------------------------------------------------------------------
> 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
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
[-- Attachment #2: Type: text/html, Size: 3521 bytes --]
next prev parent reply other threads:[~2015-01-14 20:33 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
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 [this message]
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=CAJHLa0OdLFK+D2WF8UET7WYF_FcXENd_Vqx-7JZ034Zux6qgrA@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--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