@DoNotImplement abstract class AbstractParty : Destination
An AbstractParty contains the common elements of Party and AnonymousParty, specifically the owning key of the party. In most cases Party or AnonymousParty should be used, depending on use-case.
<init> |
An AbstractParty contains the common elements of Party and AnonymousParty, specifically the owning key of the party. In most cases Party or AnonymousParty should be used, depending on use-case. AbstractParty(owningKey: PublicKey) |
owningKey |
val owningKey: PublicKey |
equals |
Anonymised parties do not include any detail apart from owning key, so equality is dependent solely on the key open fun equals(other: Any?): Boolean |
hashCode |
open fun hashCode(): Int |
nameOrNull |
abstract fun nameOrNull(): CordaX500Name? |
ref |
Build a reference to something being stored or issued by a party e.g. in a vault or (more likely) on their normal ledger. abstract fun ref(bytes: OpaqueBytes): PartyAndReference fun ref(vararg bytes: Byte): PartyAndReference |
AnonymousParty |
The AnonymousParty class contains enough information to uniquely identify a Party while excluding private information such as name. It is intended to represent a party on the distributed ledger. class AnonymousParty : Destination, AbstractParty |
Party |
The Party class represents an entity on the network, which is typically identified by a legal name and public key that it can sign transactions under. As parties may use multiple keys for signing and, for example, have offline backup keys, the "public key" of a party can be represented by a composite construct – a CompositeKey, which combines multiple cryptographic public key primitives into a tree structure. class Party : Destination, AbstractParty |