MarriedKeyChain: Clarify that just bare (non-P2SH) multisig txs which require more than 3 public keys are non-standard.

This commit is contained in:
Oscar Guindzberg
2018-11-27 17:22:04 -03:00
committed by Andreas Schildbach
parent d953ced801
commit 9485db40e8

View File

@@ -49,7 +49,7 @@ import static com.google.common.collect.Lists.newArrayList;
* specifies how many signatures required to spend transactions for this married keychain. This value should not exceed * specifies how many signatures required to spend transactions for this married keychain. This value should not exceed
* total number of keys involved (one followed key plus number of following keys), otherwise IllegalArgumentException * total number of keys involved (one followed key plus number of following keys), otherwise IllegalArgumentException
* will be thrown.</p> * will be thrown.</p>
* <p>IMPORTANT: As of Bitcoin Core 0.9 all multisig transactions which require more than 3 public keys are non-standard * <p>IMPORTANT: As of Bitcoin Core 0.9 all bare (non-P2SH) multisig transactions which require more than 3 public keys are non-standard
* and such spends won't be processed by peers with default settings, essentially making such transactions almost * and such spends won't be processed by peers with default settings, essentially making such transactions almost
* nonspendable</p> * nonspendable</p>
* <p>This method will throw an IllegalStateException, if the keychain is already married or already has leaf keys * <p>This method will throw an IllegalStateException, if the keychain is already married or already has leaf keys