Quote from: thorjag on August 28, 2014, 03:41:20 PM

Great! Is the increase in ScriptSig length to account for greater M and N values of M-of-N multisig transactions?

Correct:
commit 84fe0ffd685627689bbbcd14cf419938f2a100b2 Author: Peter Todd <pete@petertodd.org> Date: Mon Mar 10 16:38:44 2014 -0400 Increase IsStandard() scriptSig length Removes the limits on number of pubkeys for P2SH CHECKMULTISIG outputs. Previously with the 500 byte scriptSig limit there were odd restrictions where even a 1-of-12 P2SH could be spent in a standard transaction(1), yet multisig scriptPubKey's requiring more signatures quickly ran out of scriptSig space. From a "stuff-data-in-the-blockchain" point of view not much has changed as with the prior commit now only allowing the dummy value to be null the newly allowed scriptSig space can only be used for signatures. In any case, just using more outputs is trivial and doesn't cost much. 1) See 779b519480d8c5346de6e635119c7ee772e97ec872240c45e558f582a37b4b73 Mined by BTC Guild.