From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net, ruben@blocktrail.com
Subject: Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses
Date: Fri, 13 Feb 2015 02:53:14 -0500 [thread overview]
Message-ID: <20150213075314.GA2122@savin.petertodd.org> (raw)
In-Reply-To: <201502122213.34765.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Thu, Feb 12, 2015 at 10:13:33PM +0000, 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
000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-02-13 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:42 [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses Thomas Kerin
2015-02-12 22:13 ` Luke Dashjr
2015-02-13 7:53 ` Peter Todd [this message]
2015-02-13 9:01 ` Ruben de Vries
2015-05-24 0:44 ` Eric Lombrozo
2015-02-13 23:43 ` Thomas Kerin
2015-05-22 17:28 ` Thomas Kerin
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=20150213075314.GA2122@savin.petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.org \
--cc=ruben@blocktrail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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