Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Jeff Garzik
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 ru...@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

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Pavol Rusnak
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)

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Jean-Pierre Rupp
We in Haskoin do the same. On 14/01/15 17: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. -- Be Happy :)

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Jeffrey Paul
On 20150114, at 09:39, devrandom c1.sf-bitc...@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

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Eric Lombrozo
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 j...@eeqj.com wrote: On 20150114, at 09:39, devrandom c1.sf-bitc...@niftybox.net wrote

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Matt Whitlock
On Wednesday, 14 January 2015, at 3:53 pm, Eric Lombrozo wrote: Internally, pubkeys are DER-encoded integers. I thought pubkeys were represented as raw integers (i.e., they're embedded in Script as a push operation whose payload is the raw bytes of the big-endian representation of the

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread devrandom
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. On Wed, 2015-01-14 at 17:37 +0100, Ruben de Vries wrote: For p2sh multisig TXs the order of the public keys affect the hash and there doesn't

Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions

2015-01-14 Thread Eric Lombrozo
I think everyone is pretty much following this standard now. - Eric On Jan 14, 2015 12:58 PM, devrandom c1.sf-bitc...@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.