A tree data structure that enables the representation of composite public keys, which are used to represent the signing requirements for multi-signature scenarios such as RAFT notary services. A composite key is a list of leaf keys and their contributing weight, and each leaf can be a conventional single key or a composite key. Keys contribute their weight to the total if they are matched by the signature.
Factory for generating composite keys from ASN.1 format key specifications. This is used by
Dedicated class for storing a set of signatures that comprise
Custom class for holding signature data. This exists for later extension work to provide a standardised cross-platform serialization format.
This object controls and provides the available and supported signature schemes for Corda. Any implemented
A wrapper around a digital signature.
Creation and verification of a Merkle tree for a WireTransaction.
Building and verification of Partial Merkle Tree. Partial Merkle Tree is a minimal tree needed to check that a given set of leaves belongs to a full Merkle Tree.
Container for a cryptographically secure hash value. Provides utilities for generating a cryptographic hash using different algorithms (currently only SHA-256 supported).
SignatureMeta is required to add extra meta-data to a transaction's signature. It currently supports platformVersion only, but it can be extended to support a universal digital signature model enabling partial signatures and attaching extra information, such as a user's timestamp or other application-specific fields.
This class is used to define a digital signature scheme.
A serialized piece of data and its signature. Enforces signature validity in order to deserialize the data contained within.
A wrapper over the signature output accompanied by signer's public key and signature metadata. This is similar to
Cryptography data and utility classes used for signing, verifying, key management and data integrity checks.