From 5eea37679f77b08bc7e86e1f2f7ab1d66ac6e62e Mon Sep 17 00:00:00 2001 From: josecoll Date: Fri, 22 Mar 2019 13:48:09 +0000 Subject: [PATCH] Minor clarification on implication of setting 'checkSufficientSignatures' parameter. (#4919) --- .../main/kotlin/net/corda/core/flows/ReceiveTransactionFlow.kt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/core/src/main/kotlin/net/corda/core/flows/ReceiveTransactionFlow.kt b/core/src/main/kotlin/net/corda/core/flows/ReceiveTransactionFlow.kt index 41b61ff15e..b45f70d767 100644 --- a/core/src/main/kotlin/net/corda/core/flows/ReceiveTransactionFlow.kt +++ b/core/src/main/kotlin/net/corda/core/flows/ReceiveTransactionFlow.kt @@ -18,7 +18,8 @@ import java.security.SignatureException * [SignedTransaction] and perform the resolution back-and-forth required to check the dependencies and download any missing * attachments. The flow will return the [SignedTransaction] after it is resolved and then verified using [SignedTransaction.verify]. * - * Please note that it will *not* store the transaction to the vault unless that is explicitly requested. + * Please note that it will *not* store the transaction to the vault unless that is explicitly requested and checkSufficientSignatures is true. + * Setting statesToRecord to anything else when checkSufficientSignatures is false will *not* update the vault. * * @property otherSideSession session to the other side which is calling [SendTransactionFlow]. * @property checkSufficientSignatures if true checks all required signatures are present. See [SignedTransaction.verify].