Subject: Re: [Bitcoin-development] New standard transaction types: time to schedule a blockchain split?

From: Gavin Andresen <[email-masked]>
Date: Fri, 26 Aug 2011 15:44:59 -0400

> Whitelisting the basic CHECKMULTISIG form (assuming it can be made to
> work) seems uncontroversial, why not do it today?

That seems like the right way forward.

I just wrote a unit test and stepped through the CHECKMULTISIG code to
see exactly what the bug is, and the offending line is:
   797	                    int isig = ++i;
   798	                    i += nSigsCount;

It should be just   int isig = i;

The result is CHECKMULTISIG expects one extra item on the stack, so
the workaround would be a standard transaction type of the form:

scriptSig: OP_0 sig1...m
scriptPubKey: m pubkey1...n  n OP_CHECKMULTISIG

-- 
--
Gavin Andresen