[Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses
Ruben de Vries
ruben at blocktrail.com
Fri Feb 13 09:01:41 UTC 2015
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 <pete at petertodd.org> wrote:
> 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.
Barbara Strozzilaan 201
Phone: +31 (0)612227277
E-mail: ruben at blocktrail.com
BlockTrail B.V. Is registered with the Dutch Chamber of Commerce in
Amsterdam with registration No.:60262060 and VAT No.:NL853833035B01
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bitcoin-dev