From 9485db40e84559b7222cf59de6540f2923f5f124 Mon Sep 17 00:00:00 2001 From: Oscar Guindzberg Date: Tue, 27 Nov 2018 17:22:04 -0300 Subject: [PATCH] MarriedKeyChain: Clarify that just bare (non-P2SH) multisig txs which require more than 3 public keys are non-standard. --- core/src/main/java/org/bitcoinj/wallet/MarriedKeyChain.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/java/org/bitcoinj/wallet/MarriedKeyChain.java b/core/src/main/java/org/bitcoinj/wallet/MarriedKeyChain.java index 5e4cb63c..f2fb1f71 100644 --- a/core/src/main/java/org/bitcoinj/wallet/MarriedKeyChain.java +++ b/core/src/main/java/org/bitcoinj/wallet/MarriedKeyChain.java @@ -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 * total number of keys involved (one followed key plus number of following keys), otherwise IllegalArgumentException * will be thrown.

- *

IMPORTANT: As of Bitcoin Core 0.9 all multisig transactions which require more than 3 public keys are non-standard + *

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 * nonspendable

*

This method will throw an IllegalStateException, if the keychain is already married or already has leaf keys