Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-05-23 Thread Eric Lombrozo
A few months back, William Swanson and I had worked on a more general script 
template format. Unfortunately, other work has prevented us from being able to 
fully complete it - but here’s the start:

https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXvGGHWxoKmDSkiIsPI 
https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXvGGHWxoKmDSkiIsPI/

- Eric Lombrozo

 On Feb 12, 2015, at 11:53 PM, Peter Todd p...@petertodd.org wrote:
 
 On Thu, Feb 12, 2015 at 10:13:33PM +, Luke Dashjr wrote:
 Where is the Specification section?? Does this support arbitrary scripts, or
 only the simplest CHECKMULTISIG case?
 
 It might be enough to rewrite this BIP to basically say all pubkeys
 executed by all CHECKMULTISIG opcodes will be in the following canonical
 order, followed by some explanatory examples of how to apply this
 simple rule.
 
 OTOH we don't yet have a standard way of even talking about arbitrary
 scripts, so it may very well turn out to be the case that the above rule
 is too restrictive in many cases - I certainly would not want to do a
 soft-fork to enforce this, or even make it an IsStandard() rule.
 
 --
 'peter'[:-1]@petertodd.org
 13cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1
 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. 
 http://goparallel.sourceforge.net/___
 Bitcoin-development mailing list
 Bitcoin-development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bitcoin-development



signature.asc
Description: Message signed with OpenPGP using GPGMail
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-05-22 Thread Thomas Kerin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I wonder are there any other blockers or modifications that need to be
made for this to be merged?

Latest version of the document:
https://github.com/afk11/bips/blob/213e8a27a3a2eaaf44f79221a9f9f888af002801/bip-0067.mediawiki



On 13/02/15 23:43, Thomas Kerin wrote:

 On 12/02/15 22:13, Luke Dashjr wrote:
 Where is the Specification section?? Does this support arbitrary
scripts, or
 only the simplest CHECKMULTISIG case?

 The BIP is a process for deriving only the type of scripts you would
encounter doing addmultisigaddress. More complicated scripts would
require more metadata to be shared, but the only case we describe is
when given public keys and the number of signatures required.

 You're right, we're missing a Specification. I have tweaked the
document to cover this now.



 On 13/02/15 07:53, Peter Todd wrote:
 It might be enough to rewrite this BIP to basically say all pubkeys
executed by all CHECKMULTISIG opcodes will be in the following canonical
order, followed by some explanatory examples of how to apply this
simple rule. OTOH we don't yet have a standard way of even talking about
arbitrary scripts, so it may very well turn out to be the case that the
above rule is too restrictive in many cases - I certainly would not want
to do a soft-fork to enforce this, or even make it an IsStandard() rule.

 It would be interesting, but I agree it should not be brought into
these validation rules - just a convention for people to follow for now.
I think it's fair that implementers are free to order them however they
please. But I think there is good reason for wallets to opt in to the
convention and declare this, for ease of recovery, and for
interoperability reasons.


 --
 Thomas Kerin
 -
 My PGP key can be found here
http://pgp.mit.edu/pks/lookup?op=getsearch=0x3F0D2F83A2966155



--
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media,
is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/


 ___
 Bitcoin-development mailing list
 Bitcoin-development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bitcoin-development

- -- 
Thomas Kerin
- -

My PGP key can be found here
http://pgp.mit.edu/pks/lookup?op=getsearch=0x3F0D2F83A2966155
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQJ8BAEBCgBmBQJVX2ciXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2MzI1MzM4QjJGOTU5OEUzREMzQzc0MzAz
RjBEMkY4M0EyOTY2MTU1AAoJED8NL4OilmFVlOwP/1w/Omr/6jGyi7spqW22HQ7P
4+lNNzcsWp5/pv8e6YelUOSYiHuh/KxRoFfWL+wF+PNS2EtjRxSsXxg/R2nMft7B
JQLNmIG6zTzVg/lhVObeSslXaia7repZxZ1S4nyEcs8rDVt7kkNnNguFOeONF95O
3usCnrch+QbQacIt9StySAz155u1SuHeSmGmA/fRGLfArndXDdN0fYwE1KGyv5wm
LqZ1PQfmYaCc0TUKRvpDRuc/+KF7q1fDMzuP9mZ3WiPdvTDKCXSRxYfbQYJdxplg
AC0CFiOne+DXgiBdTOIcs9pcp1/6SyZs75Bkpv71AxBCmTlRTuYpsfH7O3VuZBGP
FrN/4BMYnzMbGnNmvZwerUKH59MmzZTAzLSwZlpvj7ZxRks6KOp1CHInFWQlHAXJ
O5c5McvqSdQ0rPHLcQ4DwB00Q1els18NRULjxdsTfLrT32birIXn3M1Hn/Q9d8Sa
N+Y/cfXkojf4rJt75+XwjLyHECwS378ZFC8lfs1m/B3VSQxTtTZWA8905a1IRv/F
nPQ2eaxBrFjm4OatE5lx+I/xmVAQuybG54UdcZGaKVXJbMg3sOslcYg7eA77pmR5
7jRoRU+q7GhiRsUmxSkD+57FfhaMzX7iUl4xe3YK14KUS/pONuv0USC9to8a62kA
gz9kb4pJMEhTtZNv7z9C
=iq37
-END PGP SIGNATURE-

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-02-13 Thread Ruben de Vries
The idea is more like BIP44/45 to have a 'standard' that software can
comply by and express they do
so that it makes a step towards compatibility between (wallet) software.

On Fri, Feb 13, 2015 at 8:53 AM, Peter Todd p...@petertodd.org wrote:

 On Thu, Feb 12, 2015 at 10:13:33PM +, Luke Dashjr wrote:
  Where is the Specification section?? Does this support arbitrary
 scripts, or
  only the simplest CHECKMULTISIG case?

 It might be enough to rewrite this BIP to basically say all pubkeys
 executed by all CHECKMULTISIG opcodes will be in the following canonical
 order, followed by some explanatory examples of how to apply this
 simple rule.

 OTOH we don't yet have a standard way of even talking about arbitrary
 scripts, so it may very well turn out to be the case that the above rule
 is too restrictive in many cases - I certainly would not want to do a
 soft-fork to enforce this, or even make it an IsStandard() rule.

 --
 'peter'[:-1]@petertodd.org
 13cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1




-- 
BlockTrail B.V.
Barbara Strozzilaan 201
1083HN Amsterdam
The Netherlands

Phone: +31 (0)612227277
E-mail: ru...@blocktrail.com
Web: www.blocktrail.com
Github: www.github.com/rubensayshi

BlockTrail B.V. Is registered with the Dutch Chamber of Commerce in
Amsterdam with registration No.:60262060 and VAT No.:NL853833035B01
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-02-13 Thread Thomas Kerin

On 12/02/15 22:13, Luke Dashjr wrote:
 Where is the Specification section?? Does this support arbitrary scripts, or 
 only the simplest CHECKMULTISIG case?

The BIP is a process for deriving only the type of scripts you would
encounter doing addmultisigaddress. More complicated scripts would
require more metadata to be shared, but the only case we describe is
when given public keys and the number of signatures required.

You're right, we're missing a Specification. I have tweaked the document
to cover this now.



On 13/02/15 07:53, Peter Todd wrote:
 It might be enough to rewrite this BIP to basically say all pubkeys
 executed by all CHECKMULTISIG opcodes will be in the following
 canonical order, followed by some explanatory examples of how to
 apply this simple rule. OTOH we don't yet have a standard way of even
 talking about arbitrary scripts, so it may very well turn out to be
 the case that the above rule is too restrictive in many cases - I
 certainly would not want to do a soft-fork to enforce this, or even
 make it an IsStandard() rule.

It would be interesting, but I agree it should not be brought into these
validation rules - just a convention for people to follow for now. I
think it's fair that implementers are free to order them however they
please. But I think there is good reason for wallets to opt in to the
convention and declare this, for ease of recovery, and for
interoperability reasons. 


-- 
Thomas Kerin


My PGP key can be found here 
http://pgp.mit.edu/pks/lookup?op=getsearch=0x3F0D2F83A2966155



0xA2966155.asc
Description: application/pgp-keys
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-02-12 Thread Luke Dashjr
Where is the Specification section?? Does this support arbitrary scripts, or 
only the simplest CHECKMULTISIG case?

On Thursday, February 12, 2015 9:42:23 PM Thomas Kerin wrote:
 Hi all,
 
 I have drafted a BIP with Jean Pierre and Ruben after the last
 discussion, related to a standard for deriving a canonical
 pay-to-script-hash address given a set of public keys and the number of
 signatures required. There have been two or three discussions about it
 on the mailing list to date, and various services already carry out this
 process. I hope a BIP to describe this process will allow services to
 declare themselves as BIPXX compliant, working towards interoperability
 of services and simplifying the derivation of scripts and their
 addresses by all parties.
 
 
   BIP: XX
   Title: Deterministic Pay-to-script-hash multi-signature addresses
 through public key sorting
   Author: Thomas Kerin, Jean-Pierre Rupp, Ruben de Vries
   Status: Draft
   Type: Standards Track
   Created: 8 February 2015
 
 ==Abstract==
 
 This BIP describes a method to deterministically generate
 multi-signature transaction scripts.  It focuses on defining how the
 public keys must be encoded and sorted so that the redeem script and
 corresponding P2SH address are always the same for a given set of keys
 and number of required signatures.
 
 ==Motivation==
 
 Most multi-signature transactions are addressed to P2SH
 (pay-to-script-hash) addresses, as defined in BIP-0016.
 
 Multi-signature redeem scripts do not require a particular ordering or
 encoding for public keys.  This means that for a given set of keys and
 number of required signatures, there are as many as 2(n!) possible
 standard redeem scripts, each with its separate P2SH address.  Adhering
 to a an ordering scheme and key encoding would ensure that a
 multi-signature “account” (set of public keys and required signature
 count) has a canonical P2SH address.
 
 By adopting a sorting and encoding standard, compliant wallets will
 always produce the same P2SH address for the same given set of keys and
 required signature count, making it easier to recognize transactions
 involving that multi-signature account.  This is particularly attractive
 for multisignature hierarchical-deterministic wallets, as less state is
 required to setup multi-signature accounts:  only the number of required
 signatures and master public keys of participants need to be shared, and
 all wallets will generate the same addresses.
 
 While most web wallets do not presently facilitate the setup of
 multisignature accounts with users of a different service, conventions
 which ensure cross-compatibility should make it easier to achieve this.
 
 Many wallet as a service providers use a 2of3 multi-signature schema
 where the user stores 1 of the keys (offline) as backup while using the
 other key for daily use and letting the service cosign his transactions.
 This standard will help in enabling a party other than the service
 provider to recover the wallet without any help from the service provider.
 
 ==Implementation==
 
 For a set of public keys, ensure that they have been received in
 compressed form, sort them lexicographically according to their binary
 representation before using the resulting list of keys in a standard
 multisig redeem script.  Hash the redeem script according to BIP-0016 to
 get the P2SH address.
 
 ==Compatibility==
 
 * Uncompressed keys are incompatible with this specificiation. A
 compatible implementation should not automatically compress keys.
 Receiving an uncompressed key from a multisig participant should be
 interpreted as a sign that the user has an incompatible implementation.
 * P2SH addressses do not reveal information about the script that is
 receiving the funds. For this reason it is not technically possible to
 enforce this BIP as a rule on the network.  Also, it would cause a hard
 fork.
 * Implementations that do not conform with this BIP will have
 compatibility issues with strictly-compliant wallets.
 * Implementations which do adopt this standard will be cross-compatible
 when choosing multisig addressses.
 * If a group of users were not entirely compliant, there is the
 possibility that a participant will derive an address that the others
 will not recognize as part of the common multisig account.
 
 ==Test vectors==
 The required number of signatures in each case is 2.
 
 Vector 1
 * List
 ** 02ff12471208c14bd580709cb2358d98975247d8765f92bc25eab3b2763ed605f8
 ** 02fe6f0a5a297eb38c391581c4413e084773ea23954d93f7753db7dc0adc188b2f
 * Sorted
 ** 02fe6f0a5a297eb38c391581c4413e084773ea23954d93f7753db7dc0adc188b2f
 ** 02ff12471208c14bd580709cb2358d98975247d8765f92bc25eab3b2763ed605f8
 * Script
 **
 522102fe6f0a5a297eb38c391581c4413e084773ea23954d93f7753db7dc0adc188b2f2102f
 f12471208c14bd580709cb2358d98975247d8765f92bc25eab3b2763ed605f852ae *
 Address
 ** 39bgKC7RFbpoCRbtD5KEdkYKtNyhpsNa3Z
 
 Vector 2 (Already sorted, no action required)
 * List:
 ** 

Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-02-12 Thread Peter Todd
On Thu, Feb 12, 2015 at 10:13:33PM +, Luke Dashjr wrote:
 Where is the Specification section?? Does this support arbitrary scripts, or 
 only the simplest CHECKMULTISIG case?

It might be enough to rewrite this BIP to basically say all pubkeys
executed by all CHECKMULTISIG opcodes will be in the following canonical
order, followed by some explanatory examples of how to apply this
simple rule.

OTOH we don't yet have a standard way of even talking about arbitrary
scripts, so it may very well turn out to be the case that the above rule
is too restrictive in many cases - I certainly would not want to do a
soft-fork to enforce this, or even make it an IsStandard() rule.

-- 
'peter'[:-1]@petertodd.org
13cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1


signature.asc
Description: Digital signature
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development