Multisig transactions standard for large M or N #40

1. 
   topynate commented at 4:05 am on March 28, 2014: none

   Spends of BIP16 transactions where the serialized script is a multisignature transaction are treated as standard whatever the value of M or N, subject to the limits imposed by maximum serialized script size.
2. Multisig transactions standard for large M or N

   Spends of BIP16 transactions where the serialized script is a multisignature transaction are treated as standard whatever the value of M or N, subject to the limits imposed by maximum serialized script size.

   50615ee004
3. 
   taariq commented at 4:48 am on March 28, 2014: none

   Interesting. Thank you @topynate topynate. It was my understanding that multisig transactions were only accidentally available for large M of N and were not delivered in the scope of the wiki which was supposed to be limited to 2 of 3. Did I understand this incorrectly?
4. 
   luke-jr commented at 6:18 am on March 28, 2014: member

   BIPs should only cover standardised things, not implementation-specific ones such as Bitcoin Core’s IsStandard qualifier. I suggest reading “standard transaction” as “this is a common accepted way to do things”, rather than “accepted by Bitcoin Core IsStandard”.
5. 
   topynate commented at 7:10 am on March 28, 2014: none

   Having actually looked at the code in question, it seems that this is an edge-case caused by the special handling P2SH redeeming scripts need (i.e. they cannot themselves be P2SH scripts). If it’s implementation-specific weirdness then it probably doesn’t need to be in a BIP.
6. topynate closed this on Mar 28, 2014

   ---

7. luke-jr referenced this in commit 3431ff587b on Jun 6, 2017

Contributors
topynate taariq luke-jr