public TransactionWithSignatures extends NamedByHash
An interface for transactions containing signatures, with logic for signature verification.
Modifier and Type | Interface and Description |
---|---|
static class |
TransactionWithSignatures.DefaultImpls
An interface for transactions containing signatures, with logic for signature verification.
|
Modifier and Type | Method and Description |
---|---|
void |
checkSignaturesAreValid()
Mathematically validates the signatures that are present on this transaction. This does not imply that
the signatures are by the right keys, or that there are sufficient signatures, just that they aren't
corrupt. If you use this function directly you'll need to do the other checks yourself. Probably you
want
TransactionWithSignatures.verifyRequiredSignatures instead. |
java.util.List<java.lang.String> |
getKeyDescriptions(java.util.Set<? extends java.security.PublicKey> keys)
Get a human readable description of where signatures are required from, and are missing, to assist in debugging
the underlying cause.
|
java.util.Set<java.security.PublicKey> |
getMissingSigners()
Return the PublicKeys for which we still need signatures.
|
java.util.Set<java.security.PublicKey> |
getRequiredSigningKeys()
Specifies all the public keys that require signatures for the transaction to be valid.
|
java.util.List<net.corda.core.crypto.TransactionSignature> |
getSigs()
List of signatures on this transaction.
|
NonExistentClass |
verifyRequiredSignatures()
Verifies the signatures on this transaction and throws if any are missing. In this context, "verifying" means
checking they are valid signatures and that their public keys are in the
TransactionWithSignatures.getRequiredSigningKeys set. |
void |
verifySignaturesExcept(java.security.PublicKey allowedToBeMissing)
Verifies the signatures on this transaction and throws if any are missing which aren't passed as parameters.
In this context, "verifying" means checking they are valid signatures and that their public keys are in
the
TransactionWithSignatures.getRequiredSigningKeys set. |
void |
verifySignaturesExcept(java.util.Collection<? extends java.security.PublicKey> allowedToBeMissing)
Verifies the signatures on this transaction and throws if any are missing which aren't passed as parameters.
In this context, "verifying" means checking they are valid signatures and that their public keys are in
the
TransactionWithSignatures.getRequiredSigningKeys set. |
getId
java.util.List<net.corda.core.crypto.TransactionSignature> getSigs()
List of signatures on this transaction.
java.util.Set<java.security.PublicKey> getRequiredSigningKeys()
Specifies all the public keys that require signatures for the transaction to be valid.
NonExistentClass verifyRequiredSignatures()
Verifies the signatures on this transaction and throws if any are missing. In this context, "verifying" means
checking they are valid signatures and that their public keys are in the TransactionWithSignatures.getRequiredSigningKeys
set.
TransactionWithSignatures.getRequiredSigningKeys
void verifySignaturesExcept(java.security.PublicKey allowedToBeMissing)
Verifies the signatures on this transaction and throws if any are missing which aren't passed as parameters.
In this context, "verifying" means checking they are valid signatures and that their public keys are in
the TransactionWithSignatures.getRequiredSigningKeys
set.
Normally you would not provide any keys to this function, but if you're in the process of building a partial transaction and you want to access the contents before you've signed it, you can specify your own keys here to bypass that check.
TransactionWithSignatures.getRequiredSigningKeys
void verifySignaturesExcept(java.util.Collection<? extends java.security.PublicKey> allowedToBeMissing)
Verifies the signatures on this transaction and throws if any are missing which aren't passed as parameters.
In this context, "verifying" means checking they are valid signatures and that their public keys are in
the TransactionWithSignatures.getRequiredSigningKeys
set.
Normally you would not provide any keys to this function, but if you're in the process of building a partial transaction and you want to access the contents before you've signed it, you can specify your own keys here to bypass that check.
TransactionWithSignatures.getRequiredSigningKeys
void checkSignaturesAreValid()
Mathematically validates the signatures that are present on this transaction. This does not imply that
the signatures are by the right keys, or that there are sufficient signatures, just that they aren't
corrupt. If you use this function directly you'll need to do the other checks yourself. Probably you
want TransactionWithSignatures.verifyRequiredSignatures
instead.
TransactionWithSignatures.verifyRequiredSignatures
java.util.List<java.lang.String> getKeyDescriptions(java.util.Set<? extends java.security.PublicKey> keys)
Get a human readable description of where signatures are required from, and are missing, to assist in debugging the underlying cause.
Note that the results should not be serialised, parsed or expected to remain stable between Corda versions.