### All Types

com.r3corda.node.utilities.ANSIProgressObserver | This observes the StateMachineManager and follows the progress of ProtocolLogics until they complete in the order they are added to the StateMachineManager.
com.r3corda.node.utilities.ANSIProgressRenderer | Knows how to render a ProgressTracker to the terminal using coloured, emoji-fied output. Useful when writing small command line tools, demos, tests etc. Just set the progressTracker field and it will go ahead and start drawing if the terminal supports it. Otherwise it just prints out the name of the step whenever it changes.
com.r3corda.node.api.APIServer | Top level interface to external interaction with the distributed ledger.
com.r3corda.node.internal.APIServerImpl |
com.r3corda.contracts.clause.AbstractConserveAmount | Standardised clause for checking input/output balances of fungible assets. Requires that a Move command is provided, and errors if absent. Must be the last clause under a grouping clause; errors on no-match, ends on match.
com.r3corda.contracts.clause.AbstractIssue | Standard issue clause for contracts that issue fungible assets.
com.r3corda.node.utilities.AbstractJDBCHashMap | A base class for a JDBC table backed hash map that iterates in insertion order by using an ever increasing sequence number on entries. Iterators supports remove() but entries are not really mutable and do not support setValue() method from MutableMap.MutableEntry.
com.r3corda.node.utilities.AbstractJDBCHashSet | Base class for JDBC backed hash set that delegates to a JDBC backed hash map where the values are all Unit and not actually persisted. Iteration order is order of insertion. Iterators can remove().
com.r3corda.node.services.network.AbstractNetworkMapService | Abstracted out core functionality as the basis for a persistent implementation, as well as existing in-memory implementation.
com.r3corda.node.internal.AbstractNode | A base node implementation that can be customised either for production (with real implementations that do real I/O), or a mock implementation suitable for unit test environments.
com.r3corda.node.services.api.AbstractNodeService | Abstract superclass for services that a node can host, which provides helper functions.
com.r3corda.protocols.AbstractStateReplacementProtocol | Abstract protocol to be used for replacing one state with another, for example when changing the notary of a state. Notably this requires a one to one replacement of states, states cannot be split, merged or issued as part of these protocols.
com.r3corda.node.services.api.AcceptsFileUpload | A service that implements AcceptsFileUpload can have new binary data provided to it via an HTTP upload.
com.r3corda.core.contracts.AccrualAdjustment | Simple enum for returning accurals adjusted or unadjusted. We dont actually do anything with this yet though, so its ignored for now.
com.r3corda.core.messaging.Ack | A general Ack message that conveys no content other than its presence for use when you want an acknowledgement from a recipient. Using Unit can be ambiguous as it is similar to Void and so could mean no response.
com.r3corda.node.utilities.AddOrRemove | Enum for when adding/removing something, for example adding or removing an entry in a directory.
com.r3corda.node.utilities.AffinityExecutor | An extended executor interface that supports thread affinity assertions and short circuiting. This can be useful for ensuring code runs on the right thread, and also for unit testing.
com.r3corda.client.fxutils.AggregatedList | Given an ObservableList<E> and a grouping key K, AggregatedList groups the elements by the key into a fresh ObservableList<E> for each group and exposes the groups as an observable list of As by calling assemble on each.
com.r3corda.core.contracts.clauses.AllComposition | Compose a number of clauses, such that all of the clauses must run for verification to pass.
com.r3corda.core.messaging.AllPossibleRecipients | A special base class for the set of all possible recipients, without having to identify who they all are.
com.r3corda.core.contracts.Amount | Amount represents a positive quantity of some token (currency, asset, etc.), measured in quantity of the smallest representable units. Note that quantity is not necessarily 1/100ths of a currency unit, but are the actual smallest amount used in whatever underlying thing the amount represents.
com.r3corda.client.fxutils.AmountBindings | Utility bindings for the Amount type, similar in spirit to Bindings
com.r3corda.core.testing.AmountGenerator |
com.r3corda.core.contracts.clauses.AnyComposition | Compose a number of clauses, such that any number of the clauses can run.
com.r3corda.core.utilities.ApiUtils | Utility functions to reduce boilerplate when developing HTTP APIs
com.r3corda.core.protocols.AppContext | This is just some way to track what attachments need to be in the class loader, but may later include some app properties loaded from the attachments. And perhaps the authenticated user for an API call?
com.r3corda.node.services.messaging.ArtemisMessagingComponent | The base class for Artemis services that defines shared data structures and transport configuration
com.r3corda.node.services.messaging.ArtemisMessagingServer | This class configures and manages an Apache Artemis message queue broker.
com.r3corda.client.fxutils.AssociatedList | AssociatedList creates an ObservableMap from an ObservableList by associating each list element with a unique key. It is not allowed to have several elements map to the same value
com.r3corda.core.contracts.Attachment | An attachment is a ZIP (or an optionally signed JAR) that contains one or more files. Attachments are meant to contain public static data which can be referenced from transactions and utilised from contracts. Good examples of how attachments are meant to be used include:
com.r3corda.node.servlets.AttachmentDownloadServlet | Allows the node administrator to either download full attachment zips, or individual files within those zips.
com.r3corda.core.node.services.AttachmentStorage | An attachment store records potentially large binary objects, identified by their hash.
com.r3corda.core.node.AttachmentsClassLoader | A custom ClassLoader that knows how to load classes from a set of attachments. The attachments themselves only need to provide JAR streams, and so could be fetched from a database, local disk, etc. Constructing an AttachmentsClassLoader is somewhat expensive, as every attachment is scanned to ensure that there are no overlapping file paths.
com.r3corda.core.contracts.AuthenticatedObject | Wraps an object that was signed by a public key, which may be a well known/recognised institutional key.
com.r3corda.core.transactions.BaseTransaction | An abstract class defining fields shared by all transaction types in the system.
com.r3corda.contracts.clause.BilateralNetState | Subset of state, containing the elements which must match for two obligation transactions to be nettable. If two obligation state objects produce equal bilateral net states, they are considered safe to net directly. Bilateral states are used in close-out netting.
com.r3corda.core.contracts.BilateralNettableState | Interface for state objects that support being netted with other state objects.
com.r3corda.protocols.BroadcastTransactionProtocol | Notify all involved parties about a transaction, including storing a copy. Normally this would be called via FinalityProtocol.
com.r3corda.core.contracts.BusinessCalendar | A business calendar performs date calculations that take into account national holidays and weekends. This is a typical feature of financial contracts, in which a business may not want a payment event to fall on a day when no staff are around to handle problems.
kotlin.ByteArray (extensions in package com.r3corda.core.crypto) |
kotlin.ByteArray (extensions in package com.r3corda.core.serialization) |
com.r3corda.contracts.asset.Cash | A cash transaction may split and merge money represented by a set of (issuer, depositRef) pairs, across multiple input and output states. Imagine a Bitcoin transaction but in which all UTXOs had a colour (a blend of issuer+depositRef) and you couldnt merge outputs of two colours together, but you COULD put them in the same transaction.
com.r3corda.node.services.vault.CashBalanceAsMetricsObserver | This class observes the vault and reflect current cash balances as exposed metrics in the monitoring service.
com.r3corda.schemas.CashSchema | An object used to fully qualify the CashSchema family name (i.e. independent of version).
com.r3corda.schemas.CashSchemaV1 | First version of a cash contract ORM schema that maps all fields of the Cash contract state as it stood at the time of writing.
com.r3corda.node.utilities.certsigning.CertificateSigner | This check the certificatePath for certificates required to connect to the Corda network. If the certificates are not found, a PKCS10CertificationRequest will be submitted to Corda network permissioning server using CertificateSigningService. This process will enter a slow polling loop until the request has been approved, and then the certificate chain will be downloaded and stored in KeyStore reside in certificatePath.
com.r3corda.node.utilities.certsigning.CertificateSigningService |
com.r3corda.node.services.api.Checkpoint |
com.r3corda.node.services.api.CheckpointStorage | Thread-safe storage of fiber checkpoints.
com.r3corda.client.fxutils.ChosenList | ChosenList manages an ObservableList that may be changed by the wrapping ObservableValue. Whenever the underlying ObservableValue changes the exposed list changes to the new value. Changes to the list are simply propagated.
com.r3corda.core.node.CityDatabase | A simple lookup table of city names to their coordinates. Lookups are case insensitive.
com.r3corda.core.contracts.clauses.Clause | A clause of a contract, containing a chunk of verification logic. That logic may be delegated to other clauses, or provided directly by this clause.
com.r3corda.node.services.messaging.ClientRPCRequestMessage | The contents of an RPC request message, separated from the MQ layer.
com.r3corda.core.contracts.ClientToServiceCommand | A command from the monitoring client, to the node.
java.time.Clock (extensions in package com.r3corda.node.utilities) |
kotlin.collections.Collection (extensions in package com.r3corda.core.contracts) |
kotlin.collections.Collection (extensions in package com.r3corda.client.fxutils) |
com.r3corda.core.contracts.Command | Command data/content plus pubkey pair: the signature is stored at the end of the serialized bytes
com.r3corda.core.contracts.CommandData | Marker interface for classes that represent commands
com.r3corda.contracts.testing.CommandDataGenerator |
com.r3corda.contracts.testing.CommandGenerator |
com.r3corda.contracts.CommercialPaper |
com.r3corda.contracts.CommercialPaperLegacy |
com.r3corda.schemas.CommercialPaperSchema | An object used to fully qualify the CommercialPaperSchema family name (i.e. independent of version).
com.r3corda.schemas.CommercialPaperSchemaV1 | First version of a commercial paper contract ORM schema that maps all fields of the CommercialPaper contract state as it stood at the time of writing.
com.r3corda.core.contracts.Commodity | Class representing a commodity, as an equivalent to the Currency class. This exists purely to enable the CommodityContract contract, and is likely to change in future.
com.r3corda.contracts.asset.CommodityContract | A commodity contract represents an amount of some commodity, tracked on a distributed ledger. The design of this contract is intentionally similar to the Cash contract, and the same commands (issue, move, exit) apply, the differences are in representation of the underlying commodity. Issuer in this context means the party who has the commodity, or is otherwise responsible for delivering the commodity on demand, and the deposit reference is use for internal accounting by the issuer (it might be, for example, a warehouse and/or location within a warehouse).
com.r3corda.core.contracts.clauses.CompositeClause | Abstract supertype for clauses which compose other clauses together in some logical manner.
com.r3corda.client.fxutils.ConcatenatedList | ConcatenatedList takes a list of lists and concatenates them. Any change to the underlying lists or the outer list is propagated as expected.
com.r3corda.node.servlets.Config | Primary purpose is to install Kotlin extensions for Jackson ObjectMapper so data classes work and to organise serializers / deserializers for java.time.* classes as necessary.
com.r3corda.node.services.config.ConfigHelper |
com.r3corda.node.internal.ConfigurationException |
com.r3corda.core.contracts.Contract | Implemented by a program that implements business logic on the shared ledger. All participants run this code for every LedgerTransaction they see on the network, for every input and output state. All contracts must accept the transaction for it to be accepted: failure of any aborts the entire thing. The time is taken from a trusted timestamp attached to the transaction itself i.e. it is NOT necessarily the current time.
com.r3corda.node.api.ContractClassRef |
com.r3corda.node.api.ContractDefRef | Encapsulates the contract type. e.g. Cash or CommercialPaper etc.
com.r3corda.node.api.ContractLedgerRef |
com.r3corda.core.contracts.ContractState | A contract state (or just "state") contains opaque data used by a contract program. It can be thought of as a disk file that the program can use to persist data across transactions. States are immutable: once created they are never updated, instead, any changes must generate a new successor state. States can be updated (consumed) only once: the notary is responsible for ensuring there is no "double spending" by only signing a transaction if the input states are all free.
com.r3corda.contracts.testing.ContractStateGenerator | This file contains generators for quickcheck style testing. The idea is that we can write random instance generators for each type we have in the code and test against those instead of predefined mock data. This style of testing can catch corner case bugs and test algebraic properties of the code, for example deserialize(serialize(generatedThing)) == generatedThing
com.r3corda.client.model.ContractStateModel | This model exposes the list of owned contract states.
com.r3corda.core.node.CordaPluginRegistry | Implement this interface on a class advertised in a META-INF/services/com.r3corda.core.node.CordaPluginRegistry file to extend a Corda node with additional application services.
com.r3corda.client.CordaRPCClient | An RPC client connects to the specified server and allows you to make calls to the server that perform various useful tasks. See the documentation for proxy or review the docsite to learn more about how this API works.
com.r3corda.node.services.messaging.CordaRPCOps | RPC operations that the node exposes to clients using the Java client library. These can be called from client apps and are implemented by the node in the ServerRPCOps class.
com.r3corda.node.internal.CordaRPCOpsImpl | Server side implementations of RPCs available to MQ based client tools. Execution takes place on the server thread (i.e. serially). Arguments are serialised and deserialised automatically.
com.r3corda.core.math.CubicSplineInterpolator | Interpolates values between the given data points using a SplineFunction.
java.util.Currency (extensions in package com.r3corda.core.contracts) |
com.r3corda.core.testing.CurrencyGenerator |
com.r3corda.node.services.persistence.DBCheckpointStorage | Simple checkpoint key value storage in DB using the underlying JDBCHashMap and transactional context of the call sites.
com.r3corda.node.services.persistence.DBTransactionMappingStorage | Database storage of a txhash -> state machine id mapping.
com.r3corda.node.services.persistence.DBTransactionStorage |
com.r3corda.node.servlets.DataUploadServlet | Accepts binary streams, finds the right AcceptsFileUpload implementor and hands the stream off to it.
com.r3corda.node.services.persistence.DataVending |
com.r3corda.core.contracts.DateRollConvention | This reflects what happens if a date on which a business event is supposed to happen actually falls upon a non-working day. Depending on the accounting requirement, we can move forward until we get to a business day, or backwards. There are some additional rules which are explained in the individual cases below.
com.r3corda.core.contracts.DateRollDirection | This is utilised in the DateRollConvention class to determine which way we should initially step when finding a business day.
com.r3corda.core.contracts.DayCountBasisDay | This forms the day part of the "Day Count Basis" used for interest calculation. Note that the first character cannot be a number (enum naming constraints), so we drop that in the toString lest some people get confused.
com.r3corda.core.contracts.DayCountBasisYear | This forms the year part of the "Day Count Basis" used for interest calculation.
com.r3corda.core.contracts.DealState | Interface representing an agreement that exposes various attributes that are common. Implementing it simplifies implementation of general protocols that manipulate many agreement types.
com.r3corda.core.serialization.DeserializeAsKotlinObjectDef | Marker interface for kotlin object definitions so that they are deserialized as the singleton instance.
com.r3corda.client.model.Diff |
com.r3corda.core.crypto.DigitalSignature | A wrapper around a digital signature. The covering field is a generic tag usable by whatever is interpreting the signature. It isnt used currently, but experience from Bitcoin suggests such a feature is useful, especially when building partially signed transactions.
kotlin.Double (extensions in package com.r3corda.core.contracts) |
kotlin.Double (extensions in package com.r3corda.core) |
com.r3corda.node.driver.DriverDSL |
com.r3corda.node.driver.DriverDSLExposedInterface | This is the interface thats exposed to DSL users.
com.r3corda.node.driver.DriverDSLInternalInterface |
com.r3corda.core.contracts.DummyContract |
com.r3corda.core.crypto.DummyPublicKey |
com.r3corda.core.contracts.DummyState | Dummy state for use in testing. Not part of any contract, not even the DummyContract.
com.r3corda.core.testing.DurationGenerator |
com.r3corda.node.services.keys.E2ETestKeyManagementService | A simple in-memory KMS that doesnt bother saving keys to disk. A real implementation would:
com.r3corda.core.serialization.Ed25519PrivateKeySerializer | For serialising an ed25519 private key
com.r3corda.core.serialization.Ed25519PublicKeySerializer | For serialising an ed25519 public key
com.r3corda.core.utilities.Emoji | A simple wrapper class that contains icons and support for printing them only when were connected to a terminal.
com.r3corda.core.ErrorOr | Representation of an operation that may have thrown an error.
com.r3corda.client.mock.EventGenerator | Generators for incoming/outgoing events to/from the WalletMonitorService. Internally it keeps track of owned state/ref pairs, but it doesnt necessarily generate "correct" events
com.r3corda.client.model.ExchangeRate |
com.r3corda.client.model.ExchangeRateModel | This model provides an exchange rate from arbitrary currency to arbitrary currency. TODO hook up an actual oracle
com.r3corda.contracts.testing.ExitGenerator |
com.r3corda.core.contracts.Expression | Represents a textual expression of e.g. a formula
com.r3corda.core.contracts.ExpressionDeserializer |
com.r3corda.core.contracts.ExpressionSerializer |
com.r3corda.protocols.FetchAttachmentsProtocol | Given a set of hashes either loads from from local storage or requests them from the other peer. Downloaded attachments are saved to local storage automatically.
com.r3corda.protocols.FetchDataProtocol | An abstract protocol for fetching typed data from a remote peer.
com.r3corda.protocols.FetchTransactionsProtocol | Given a set of tx hashes (IDs), either loads them from local disk or asks the remote peer to provide them.
com.r3corda.node.utilities.FiberBox | Modelled on ThreadBox, but with support for waiting that is compatible with Quasar Fibers and MutableClocks.
com.r3corda.core.transactions.FilterFuns | Holds filter functions on transactions fields. Functions are used to build a partial tree only out of some subset of original transaction fields.
com.r3corda.core.contracts.clauses.FilterOn | Filter the states that are passed through to the wrapped clause, to restrict them to a specific type.
com.r3corda.core.transactions.FilteredLeaves | Class that holds filtered leaves for a partial Merkle transaction. We assume mixed leaves types.
com.r3corda.core.transactions.FilteredTransaction | Class representing merkleized filtered transaction.
com.r3corda.protocols.FinalityProtocol | Finalise a transaction by notarising it, then recording it locally, and then sending it to all involved parties.
com.r3corda.core.contracts.clauses.FirstComposition | Compose a number of clauses, such that the first match is run, and it errors if none is run.
com.r3corda.core.contracts.Fix | A Fix represents a named interest rate, on a given day, for a given duration. It can be embedded in a tx.
com.r3corda.core.contracts.FixOf | A FixOf identifies the question side of a fix: what day, tenor and type of fix ("LIBOR", "EURIBOR" etc)
com.r3corda.core.contracts.FixableDealState | Interface adding fixing specific methods.
com.r3corda.client.fxutils.FlattenedList | FlattenedList flattens the passed in list of ObservableValues so that changes in individual updates to the values are reflected in the exposed list as expected.
com.r3corda.core.contracts.Frequency | Frequency at which an event occurs - the enumerator also casts to an integer specifying the number of times per year that would divide into (eg annually = 1, semiannual = 2, monthly = 12 etc).
com.r3corda.node.services.config.FullNodeConfiguration |
kotlin.Function1 (extensions in package com.r3corda.client.fxutils) |
kotlin.Function2 (extensions in package com.r3corda.client.fxutils) |
kotlin.Function3 (extensions in package com.r3corda.client.fxutils) |
kotlin.Function4 (extensions in package com.r3corda.client.fxutils) |
com.r3corda.core.contracts.FungibleAsset | Interface for contract states representing assets which are fungible, countable and issued by a specific party. States contain assets which are equivalent (such as cash of the same currency), so records of their existence can be merged or split as needed where the issuer is the same. For instance, dollars issued by the Fed are fungible and countable (in cents), barrels of West Texas crude are fungible and countable (oil from two small containers can be poured into one large container), shares of the same class in a specific company are fungible and countable, and so on.
com.r3corda.client.model.GatheredTransactionData |
com.r3corda.client.model.GatheredTransactionDataModel | This model provides an observable list of transactions and what state machines/protocols recorded them
com.r3corda.client.mock.Generator | This file defines a basic Generator library for composing random generators of objects.
com.r3corda.core.contracts.clauses.GroupClauseVerifier |
com.r3corda.node.utilities.certsigning.HTTPCertificateSigningService |
com.r3corda.node.services.schema.HibernateObserver | A vault observer that extracts Object Relational Mappings for contract states that support it, and persists them with Hibernate.
com.r3corda.core.node.services.IdentityService | An identity service maintains an bidirectional map of Partys to their associated public keys and thus supports lookup of a party given its key. This is obviously very incomplete and does not reflect everything a real identity service would provide.
com.r3corda.core.protocols.IllegalProtocolLogicException |
com.r3corda.core.serialization.ImmutableClassSerializer | Serializes properties and deserializes by using the constructor. This assumes that all backed properties are set via the constructor and the class is immutable.
com.r3corda.node.services.identity.InMemoryIdentityService | Simple identity service which caches parties and provides functionality for efficient lookup.
com.r3corda.node.services.network.InMemoryNetworkMapCache | Extremely simple in-memory cache of the network map.
com.r3corda.node.services.network.InMemoryNetworkMapService |
com.r3corda.node.services.persistence.InMemoryStateMachineRecordedTransactionMappingStorage | This is a temporary in-memory storage of a state machine id -> txhash mapping
com.r3corda.node.services.transactions.InMemoryUniquenessProvider | A dummy Uniqueness provider that stores the whole history of consumed states in memory
java.io.InputStream (extensions in package com.r3corda.core) |
com.r3corda.node.utilities.InstantColumnType | ColumnType for marshalling to/from database on behalf of java.time.Instant.
com.r3corda.core.testing.InstantGenerator |
com.r3corda.core.contracts.InsufficientBalanceException |
kotlin.Int (extensions in package com.r3corda.core.contracts) |
kotlin.Int (extensions in package com.r3corda.core) |
com.r3corda.core.math.Interpolator |
com.r3corda.core.math.InterpolatorFactory |
com.r3corda.core.contracts.IssuanceDefinition | Marker interface for data classes that represent the issuance state for a contract. These are intended as templates from which the state object is initialised.
com.r3corda.core.contracts.IssueCommand | A common issue command, to enforce that issue commands have a nonce value.
com.r3corda.contracts.testing.IssueGenerator |
com.r3corda.core.contracts.Issued | Definition for an issued product, which can be cash, a cash-like thing, assets, or generally anything else thats quantifiable with integer quantities.
com.r3corda.core.testing.IssuedGenerator |
kotlin.collections.Iterable (extensions in package com.r3corda.core.contracts) |
kotlin.collections.Iterable (extensions in package com.r3corda.core.crypto) |
kotlin.collections.Iterable (extensions in package com.r3corda.core.node.services) |
kotlin.collections.Iterable (extensions in package com.r3corda.core) |
kotlin.collections.Iterable (extensions in package com.r3corda.contracts.asset) |
com.r3corda.node.utilities.JDBCHashMap | A convenient JDBC table backed hash map with iteration order based on insertion order. See AbstractJDBCHashMap for further implementation details.
com.r3corda.node.utilities.JDBCHashSet | A convenient JDBC table backed hash set with iteration order based on insertion order. See AbstractJDBCHashSet and AbstractJDBCHashMap for further implementation details.
com.r3corda.node.utilities.JDBCHashedTable |
com.r3corda.node.utilities.JsonSupport | Utilities and serialisers for working with JSON representations of basic types. This adds Jackson support for the java.time API, some core types, and Kotlin data classes.
com.r3corda.core.node.services.KeyManagementService | The KMS is responsible for storing and using private keys to sign things. An implementation of this may, for example, call out to a hardware security module that enforces various auditing and frequency-of-use requirements.
java.security.KeyPair (extensions in package com.r3corda.core.crypto) |
com.r3corda.core.serialization.KotlinObjectSerializer | Serializer to deserialize kotlin object definitions marked with DeserializeAsKotlinObjectDef.
com.r3corda.node.services.network.LastAcknowledgeInfo |
com.r3corda.core.transactions.LedgerTransaction | A LedgerTransaction is derived from a WireTransaction. It is the result of doing the following operations:
com.r3corda.client.fxutils.LeftOuterJoinedMap | LeftOuterJoinedMap implements a special case of a left outer join where were matching on primary keys of both tables.
com.r3corda.core.math.LinearInterpolator | Interpolates values between the given data points using straight lines.
com.r3corda.core.contracts.LinearState | A state that evolves by superseding itself, all of which share the common "linearId".
kotlin.collections.List (extensions in package com.r3corda.core) |
java.time.LocalDate (extensions in package com.r3corda.core.contracts) |
com.r3corda.node.utilities.LocalDateColumnType | ColumnType for marshalling to/from database on behalf of java.time.LocalDate.
com.r3corda.node.utilities.LocalDateTimeColumnType | ColumnType for marshalling to/from database on behalf of java.time.LocalDateTime.
com.r3corda.core.utilities.LogHelper | A configuration helper that allows modifying the log level for specific loggers
kotlin.Long (extensions in package com.r3corda.core) |
com.r3corda.client.fxutils.MapValuesList | MapValuesList takes an ObservableMap and returns its values as an ObservableList. The order of returned elements is deterministic but unspecified.
com.r3corda.client.fxutils.MappedList | This is a variant of EasyBind.map where the mapped list is backed, therefore the mapping function will only be run when an element is inserted or updated. Use this instead of EasyBind.map to trade off memory vs CPU, or if (god forbid) the mapped function is side-effecting.
com.r3corda.core.schemas.MappedSchema | A database schema that might be configured for this node. As well as a name and version for identifying the schema, also list the classes that may be used in the generated object graph in order to configure the ORM tool.
com.r3corda.node.services.messaging.MarshalledObservation | Used in the RPC wire protocol to wrap an observation with the handle of the observable its intended for.
com.r3corda.core.transactions.MerkleTree | Creation and verification of a Merkle Tree for a Wire Transaction.
com.r3corda.core.crypto.MerkleTreeException |
com.r3corda.core.messaging.Message | A message is defined, at this level, to be a (topic, timestamp, byte arrays) triple, where the topic is a string in Java-style reverse dns form, with "platform." being a prefix reserved by the platform for its own use. Vendor specific messages can be defined, but use your domain name as the prefix e.g. "uk.co.bigbank.messages.SomeMessage".
com.r3corda.core.messaging.MessageHandlerRegistration |
com.r3corda.core.messaging.MessageRecipientGroup | A base class for a set of recipients specifically identified by the sender.
com.r3corda.core.messaging.MessageRecipients | The interface for a group of message recipients (which may contain only one recipient)
com.r3corda.core.messaging.MessagingService | A MessagingService sits at the boundary between a message routing / networking layer and the core platform code.
com.r3corda.node.services.api.MessagingServiceBuilder | This class lets you start up a MessagingService. Its purpose is to stop you from getting access to the methods on the messaging service interface until you have successfully started up the system. One of these objects should be the only way to obtain a reference to a MessagingService. Startup may be a slow process: some implementations may let you cast the returned future to an object that lets you get status info.
com.r3corda.node.services.api.MessagingServiceInternal |
com.r3corda.core.serialization.MissingAttachmentsException | Thrown during deserialisation to indicate that an attachment needed to construct the WireTransaction is not found
com.r3corda.client.model.Models |
com.r3corda.node.services.api.MonitoringService | Provides access to various metrics and ways to notify monitoring services of things, for sysadmin purposes. This is not an interface because it is too lightweight to bother mocking out.
com.r3corda.core.contracts.MoveCommand | A common move command for contracts which can change owner.
com.r3corda.contracts.testing.MoveGenerator |
com.r3corda.contracts.clause.MultilateralNetState | Subset of state, containing the elements which must match for two or more obligation transactions to be candidates for netting (this does not include the checks to enforce that everyones amounts received are the same at the end, which is handled under the verify() function). In comparison to BilateralNetState, this doesnt include the parties keys, as ensuring balances match on input and output is handled elsewhere. Used in cases where all parties (or their proxies) are signing, such as central clearing.
com.r3corda.core.contracts.MultilateralNettableState | Interface for state objects that support being netted with other state objects.
com.r3corda.node.utilities.MutableClock | An abstract class with helper methods for a type of Clock that might have its concept of "now" adjusted externally.
com.r3corda.core.contracts.NamedByHash | Implemented by anything that can be named by a secure hash value (e.g. transactions, attachments).
com.r3corda.contracts.clause.NetClause | Clause for netting contract states. Currently only supports obligation contract.
com.r3corda.core.contracts.NetCommand | A common netting command for contracts whose states can be netted.
com.r3corda.contracts.clause.NetState | Common interface for the state subsets used when determining nettability of two or more states. Exposes the underlying issued thing.
com.r3corda.core.contracts.NetType | Enum for the types of netting that can be applied to state objects. Exact behaviour for each type of netting is left to the contract to determine.
com.r3corda.core.contracts.NettableState |
com.r3corda.core.node.services.NetworkCacheError |
com.r3corda.client.model.NetworkIdentityModel |
com.r3corda.core.node.services.NetworkMapCache | A network map contains lists of nodes on the network along with information about their identity keys, services they provide and host names or IP addresses where they can be connected to. The cache wraps around a map fetched from an authoritative service, and adds easy lookup of the data stored within it. Generally it would be initialised with a specified network map service, which it fetches data from and then subscribes to updates of.
com.r3corda.node.services.network.NetworkMapService | A network map contains lists of nodes on the network along with information about their identity keys, services they provide and host names or IP addresses where they can be connected to. This information is cached locally within nodes, by the NetworkMapCache. Currently very basic consensus controls are applied, using signed changes which replace each other based on a serial number present in the change.
com.r3corda.core.serialization.NoReferencesSerializer |
com.r3corda.contracts.clause.NoZeroSizedOutputs | Clause for fungible asset contracts, which enforces that no output state should have a balance of zero.
com.r3corda.node.internal.Node | A Node manages a standalone server that takes part in the P2P network. It creates the services found in ServiceHub, loads important data off disk and starts listening for connections.
com.r3corda.node.services.persistence.NodeAttachmentService | Stores attachments in the specified local directory, which must exist. Doesnt allow new attachments to be uploaded.
com.r3corda.node.serialization.NodeClock | A Clock that tokenizes itself when serialized, and delegates to an underlying Clock implementation.
com.r3corda.node.services.config.NodeConfiguration |
com.r3corda.core.node.NodeInfo | Info about a network node that acts on behalf of some form of contract party.
com.r3corda.node.driver.NodeInfoAndConfig |
com.r3corda.node.services.network.NodeMapError |
com.r3corda.node.services.messaging.NodeMessagingClient | This class implements the MessagingService API using Apache Artemis, the successor to their ActiveMQ product. Artemis is a message queue broker and here we run a client connecting to the specified broker instance ArtemisMessagingServer. Its primarily concerned with peer-to-peer messaging.
com.r3corda.client.model.NodeMonitorModel | This model exposes raw event streams to and from the node.
com.r3corda.node.services.network.NodeRegistration | A node registration state in the network map.
com.r3corda.node.services.network.NodeRegistrationInfo |
com.r3corda.node.services.config.NodeSSLConfiguration |
com.r3corda.node.services.events.NodeSchedulerService | A first pass of a simple SchedulerService that works with MutableClocks for testing, demonstrations and simulations that also encompasses the Vault observer for processing transactions.
com.r3corda.node.services.schema.NodeSchemaService | Most basic implementation of SchemaService.
com.r3corda.node.services.vault.NodeVaultService | Currently, the node vault service is a very simple RDBMS backed implementation. It will change significantly when we add further functionality as the design for the vault and vault service matures.
com.r3corda.core.utilities.NonEmptySet | A set which is constrained to ensure it can never be empty. An initial value must be provided at construction, and attempting to remove the last element will cause an IllegalStateException. The underlying set is exposed for Kryo to access, but should not be accessed directly.
com.r3corda.core.utilities.NonEmptySetSerializer | Custom serializer which understands it has to read in an item before trying to construct the set.
com.r3corda.node.services.NotaryChange |
com.r3corda.protocols.NotaryChangeProtocol | A protocol to be used for changing a states Notary. This is required since all input states to a transaction must point to the same notary.
com.r3corda.protocols.NotaryError |
com.r3corda.protocols.NotaryException |
com.r3corda.protocols.NotaryProtocol |
com.r3corda.node.services.transactions.NotaryService | A Notary service acts as the final signer of a transaction ensuring two things:
com.r3corda.core.crypto.NullPublicKey |
com.r3corda.core.crypto.NullSignature | A signature with a key and value of zero. Useful when you want a signature object that you know wont ever be used.
com.r3corda.contracts.asset.Obligation | An obligation contract commits the obligor to delivering a specified amount of a fungible asset (for example the Cash contract) at a specified future point in time. Settlement transactions may split and merge contracts across multiple input and output states. The goal of this design is to handle amounts owed, and these contracts are expected to be netted/merged, with settlement only for any remainder amount.
javafx.collections.ObservableList (extensions in package com.r3corda.client.fxutils) |
javafx.collections.ObservableMap (extensions in package com.r3corda.client.fxutils) |
javafx.beans.value.ObservableValue (extensions in package com.r3corda.client.fxutils) |
com.r3corda.contracts.asset.OnLedgerAsset | An asset transaction may split and merge assets represented by a set of (issuer, depositRef) pairs, across multiple input and output states. Imagine a Bitcoin transaction but in which all UTXOs had a colour (a blend of issuer+depositRef) and you couldnt merge outputs of two colours together, but you COULD put them in the same transaction.
com.r3corda.core.serialization.OpaqueBytes | A simple class that wraps a byte array and makes the equals/hashCode/toString methods work as you actually expect. In an ideal JVM this would be a value type and be completely overhead free. Project Valhalla is adding such functionality to Java, but it wont arrive for a few years yet
com.r3corda.node.services.config.OptionalConfig | Helper class for optional configurations
com.r3corda.core.serialization.OrderedSerializer |
com.r3corda.core.contracts.OwnableState | A contract state that can have a single owner.
com.r3corda.node.ParamsSpec |
com.r3corda.node.utilities.certsigning.ParamsSpec |
com.r3corda.core.crypto.PartialMerkleTree | 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.
com.r3corda.client.model.PartiallyResolvedTransaction | PartiallyResolvedTransaction holds a SignedTransaction that has zero or more inputs resolved. The intent is to prepare clients for cases where an input can only be resolved in the future/cannot be resolved at all (for example because of permissioning)
com.r3corda.core.crypto.Party | A Party is well known (name, pubkey) pair. In a real system this would probably be an X.509 certificate.
com.r3corda.core.contracts.PartyAndReference | Reference to something being stored or issued by a party e.g. in a vault or (more likely) on their normal ledger. The reference is intended to be encrypted so its meaningless to anyone other than the party.
com.r3corda.core.testing.PartyAndReferenceGenerator |
com.r3corda.node.utilities.PartyColumns |
com.r3corda.core.testing.PartyGenerator |
java.nio.file.Path (extensions in package com.r3corda.core) |
com.r3corda.core.contracts.PaymentRule | Whether the payment should be made before the due date, or after it.
com.r3corda.node.services.messaging.PermissionException |
com.r3corda.node.services.keys.PersistentKeyManagementService | A persistent re-implementation of E2ETestKeyManagementService to support node re-start.
com.r3corda.node.services.network.PersistentNetworkMapService | A network map service backed by a database to survive restarts of the node hosting it.
com.r3corda.core.schemas.PersistentState | A super class for all mapped states exported to a schema that ensures the StateRef appears on the database row. The StateRef will be set to the correct value by the framework (theres no need to set during mapping generation by the state itself).
com.r3corda.core.schemas.PersistentStateRef | Embedded StateRef representation used in state mapping.
com.r3corda.node.services.transactions.PersistentUniquenessProvider | A RDBMS backed Uniqueness provider
com.r3corda.core.node.PhysicalLocation | A labelled WorldCoordinate, where the label is human meaningful. For example, the name of the nearest city. Labels should not refer to non-landmarks, for example, they should not contain the names of organisations.
com.r3corda.core.node.PluginServiceHub | A service hub to be used by the CordaPluginRegistry
com.r3corda.core.math.Polynomial | Represents a polynomial function of arbitrary degree.
com.r3corda.node.driver.PortAllocation |
java.security.PrivateKey (extensions in package com.r3corda.core.crypto) |
com.r3corda.core.testing.PrivateKeyGenerator |
com.r3corda.core.utilities.ProgressTracker | A progress tracker helps surface information about the progress of an operation to a user interface or API of some kind. It lets you define a set of steps that represent an operation. A step is represented by an object (typically a singleton).
com.r3corda.client.model.ProgressTrackingEvent |
com.r3corda.node.services.PropertiesFileRPCUserService |
com.r3corda.node.api.ProtocolClassRef |
com.r3corda.node.services.statemachine.ProtocolIORequest |
com.r3corda.node.api.ProtocolInstanceRef |
com.r3corda.core.protocols.ProtocolLogic | A sub-class of ProtocolLogic implements a protocol flow using direct, straight line blocking code. Thus you can write complex protocol logic in an ordinary fashion, without having to think about callbacks, restarting after a node crash, how many instances of your protocol there are running and so on.
com.r3corda.core.protocols.ProtocolLogicRef | A class representing a ProtocolLogic instance which would be possible to safely pass out of the contract sandbox.
com.r3corda.core.protocols.ProtocolLogicRefFactory | A class for conversion to and from ProtocolLogic and ProtocolLogicRef instances.
com.r3corda.node.api.ProtocolRef | Encapsulates the protocol to be instantiated. e.g. TwoPartyTradeProtocol.Buyer.
com.r3corda.node.api.ProtocolRequiringAttention | Thinking that Instant is OK for short lived protocol deadlines.
com.r3corda.core.protocols.ProtocolSessionException |
com.r3corda.core.protocols.ProtocolStateMachine | A ProtocolStateMachine instance is a suspendable fiber that delegates all actual logic to a ProtocolLogic instance. For any given flow there is only one PSM, even if that protocol invokes subprotocols.
com.r3corda.node.services.statemachine.ProtocolStateMachineImpl |
com.r3corda.client.model.ProtocolStatus |
java.security.PublicKey (extensions in package com.r3corda.core.crypto) |
com.r3corda.node.utilities.PublicKeyColumnType | ColumnType for marshalling to/from database on behalf of PublicKey.
com.r3corda.core.testing.PublicKeyGenerator |
com.r3corda.core.crypto.PublicKeyTree | A tree data structure that enables the representation of composite public keys.
com.r3corda.core.schemas.QueryableState | A contract state that may be mapped to database schemas configured for this node to support querying for, or filtering of, states.
com.r3corda.node.services.messaging.RPCDispatcher | Intended to service transient clients only (not p2p nodes) for short-lived, transient request/response pairs. If you need robustness, this is the wrong system. If you dont want a response, this is probably the wrong system (you could just send a message). If you want complex customisation of how requests/responses are handled, this is probably the wrong system.
com.r3corda.node.services.messaging.RPCException | Thrown to indicate a fatal error in the RPC system itself, as opposed to an error generated by the invoked method.
com.r3corda.node.services.messaging.RPCOps | Base interface that all RPC servers must implement. Note: in Corda theres only one RPC interface. This base interface is here in case we split the RPC system out into a separate library one day.
com.r3corda.node.services.messaging.RPCReturnsObservables | If an RPC is tagged with this annotation it may return one or more observables anywhere in its response graph. Calling such a method comes with consequences: its slower, and consumes server side resources as observations will buffer up on the server until theyre consumed by the client.
com.r3corda.node.services.messaging.RPCSinceVersion | Records the protocol version in which this RPC was added.
com.r3corda.node.services.RPCUserService | Service for retrieving User objects representing RPC users who are authorised to use the RPC system. A User contains their login username and password along with a set of permissions for RPC services they are allowed access to. These permissions are represented as Strings to allow RPC implementations to add their own permissioning.
com.r3corda.client.fxutils.ReadOnlyBackedObservableMapBase | ReadOnlyBackedObservableMapBase is a base class implementing all abstract functions required for an ObservableMap using a backing HashMap that subclasses should modify.
com.r3corda.core.node.services.ReadOnlyTransactionStorage | Thread-safe storage of transactions.
com.r3corda.node.services.statemachine.ReceiveOnly |
com.r3corda.node.services.statemachine.ReceiveRequest |
com.r3corda.core.serialization.ReferencesAwareJavaSerializer | Improvement to the builtin JavaSerializer by honouring the Kryo.getReferences setting.
com.r3corda.node.services.api.RegulatorService | Placeholder interface for regulator services.
com.r3corda.client.fxutils.ReplayedList | This list type just replays changes propagated from the underlying source list. Used for testing changes and backing a non-backed observable
com.r3corda.core.contracts.Requirements |
com.r3corda.protocols.ResolveTransactionsProtocol | This protocol is used to verify the validity of a transaction by recursively checking the validity of all the dependencies. Once a transaction is checked its inserted into local storage so it can be relayed and wont be checked again.
com.r3corda.node.servlets.ResponseFilter | This adds headers needed for cross site scripting on API clients.
com.r3corda.core.RetryableException | This represents a transient exception or condition that might no longer be thrown if the operation is re-run or called again.
com.r3corda.core.contracts.SchedulableState |
com.r3corda.core.contracts.Scheduled | Something which is scheduled to happen at a point in time
com.r3corda.core.contracts.ScheduledActivity | This class represents the lifecycle activity that a contract state of type LinearState would like to perform at a given point in time. e.g. run a fixing protocol.
com.r3corda.node.services.events.ScheduledActivityObserver | This observes the vault and schedules and unschedules activities appropriately based on state production and consumption.
com.r3corda.core.contracts.ScheduledStateRef | Represents a contract state (unconsumed output) of type LinearState and a point in time that a lifecycle event is expected to take place for that contract state.
com.r3corda.core.node.services.SchedulerService | Provides access to schedule activity at some point in time. This interface might well be expanded to increase the feature set in the future.
com.r3corda.node.services.api.SchemaService | A configuration and customisation point for Object Relational Mapping of contract state objects.
com.r3corda.core.crypto.SecureHash | Container for a cryptographically secure hash value. Provides utilities for generating a cryptographic hash using different algorithms (currently only SHA-256 supported).
com.r3corda.node.utilities.SecureHashColumnType | ColumnType for marshalling to/from database on behalf of SecureHash.
com.r3corda.core.testing.SecureHashGenerator |
com.r3corda.node.services.statemachine.SendAndReceive |
com.r3corda.node.services.statemachine.SendOnly |
com.r3corda.node.services.statemachine.SendRequest |
com.r3corda.core.serialization.SerializationToken | This represents a token in the serialized stream for an instance of a type that implements SerializeAsToken.
com.r3corda.core.serialization.SerializeAsToken | This interface should be implemented by classes that want to substitute a token representation of themselves if they are serialized because they have a lot of internal state that does not serialize (well).
com.r3corda.core.serialization.SerializeAsTokenContext | A context for mapping SerializationTokens to/from SerializeAsTokens.
com.r3corda.core.serialization.SerializeAsTokenSerializer | A Kryo serializer for SerializeAsToken implementations.
com.r3corda.core.serialization.SerializedBytes | A type safe wrapper around a byte array that contains a serialised object. You can call SerializedBytes.deserialize to get the original object back.
com.r3corda.core.serialization.SerializedBytesSerializer | A serialiser that avoids writing the wrapper class to the byte stream, thus ensuring SerializedBytes is a pure type safety hack.
com.r3corda.core.node.ServiceEntry | Information for an advertised service including the service specific identity information. The identity can be used in protocols and is distinct from the Nodes legalIdentity
com.r3corda.core.node.ServiceHub | A service hub simply vends references to the other services a node has. Some of those services may be missing or mocked out. This class is useful to pass to chunks of pluggable code that might have need of many different kinds of functionality and you dont want to hard-code which types in the interface.
com.r3corda.node.services.api.ServiceHubInternal |
com.r3corda.core.node.services.ServiceInfo | A container for additional information for an advertised service.
com.r3corda.protocols.ServiceRequestMessage | Abstract superclass for request messages sent to services which expect a reply.
com.r3corda.core.node.services.ServiceType | Identifier for service types a node can expose over the network to other peers. These types are placed into network map advertisements. Services that are purely local and are not providing functionality to other parts of the network dont need a declared service type.
com.r3corda.core.crypto.SignedData | A serialized piece of data and its signature. Enforces signature validity in order to deserialize the data contained within.
com.r3corda.core.transactions.SignedTransaction | SignedTransaction wraps a serialized WireTransaction. It contains one or more signatures, each one for a public key that is mentioned inside a transaction command. SignedTransaction is the top level transaction type and the type most frequently passed around the network and stored. The identity of a transaction is the hash of a WireTransaction, therefore if you are storing data keyed by WT hash be aware that multiple different STs may map to the same key (and they could be different in important ways, like validity). The signatures on a SignedTransaction might be invalid or missing: the type does not imply validity. A transaction ID should be the hash of the WireTransaction Merkle tree root. Thus adding or removing a signature does not change it.
com.r3corda.contracts.testing.SignedTransactionGenerator |
com.r3corda.node.services.transactions.SimpleNotaryService | A simple Notary service that does not perform transaction validation
com.r3corda.core.messaging.SingleMessageRecipient | A base class for the case of point-to-point messages
com.r3corda.core.serialization.SingletonSerializationToken | A class representing a SerializationToken for some object that is not serializable but can be looked up (when deserialized) via just the class name.
com.r3corda.core.serialization.SingletonSerializeAsToken | A base class for implementing large objects / components / services that need to serialize themselves to a string token to indicate which instance the token is a serialized form of.
com.r3corda.core.math.SplineFunction | A spline is function piecewise-defined by polynomial functions. Points at which polynomial pieces connect are known as knots.
com.r3corda.node.services.statemachine.StackSnapshot |
com.r3corda.core.contracts.StateAndRef | A StateAndRef is simply a (state, ref) pair. For instance, a vault (which holds available assets) contains these.
com.r3corda.client.model.StateMachineData |
com.r3corda.node.services.messaging.StateMachineInfo |
com.r3corda.node.services.statemachine.StateMachineManager | A StateMachineManager is responsible for coordination and persistence of multiple ProtocolStateMachine objects. Each such object represents an instantiation of a (two-party) protocol that has reached a particular point.
com.r3corda.core.node.services.StateMachineRecordedTransactionMappingStorage | This is the interface to storage storing state machine -> recorded tx mappings. Any time a transaction is recorded during a protocol run addMapping should be called.
com.r3corda.core.protocols.StateMachineRunId |
com.r3corda.client.model.StateMachineStatus |
com.r3corda.core.node.services.StateMachineTransactionMapping |
com.r3corda.node.services.messaging.StateMachineUpdate |
com.r3corda.core.contracts.StateRef | A stateref is a pointer (reference) to a state, this is an equivalent of an "outpoint" in Bitcoin. It records which transaction defined the state and where in that transaction it was.
com.r3corda.node.utilities.StateRefColumns |
com.r3corda.core.testing.StateRefGenerator |
com.r3corda.protocols.StateReplacementException |
com.r3corda.protocols.StateReplacementRefused | Thrown when a participant refuses the proposed state replacement
com.r3corda.node.api.StatesQuery | Extremely rudimentary query language which should most likely be replaced with a product.
com.r3corda.core.node.services.StorageService | A sketch of an interface to a simple key/value storage system. Intended for persistence of simple blobs like transactions, serialised protocol state machines and so on. Again, this isnt intended to imply lack of SQL or anything like that, this interface is only big enough to support the prototyping work.
com.r3corda.node.services.persistence.StorageServiceImpl |
com.r3corda.node.utilities.StrandLocalTransactionManager | A relatively close copy of the ThreadLocalTransactionManager in Exposed but with the following adjustments to suit our environment:
kotlin.String (extensions in package com.r3corda.core.serialization) |
kotlin.String (extensions in package com.r3corda.core) |
java.time.temporal.Temporal (extensions in package com.r3corda.core) |
com.r3corda.core.contracts.Tenor | Placeholder class for the Tenor datatype - which is a standardised duration of time until maturity
com.r3corda.node.utilities.TestClock | A Clock that can have the date advanced for use in demos.
com.r3corda.core.ThreadBox | A threadbox is a simple utility that makes it harder to forget to take a lock before accessing some shared state. Simply define a private class to hold the data that must be grouped under the same lock, and then pass the only instance to the ThreadBox constructor. You can now use the locked method with a lambda to take the lock in a way that ensures itll be released if theres an exception.
kotlin.Throwable (extensions in package com.r3corda.core) |
com.r3corda.core.utilities.TimeWindow | A class representing a window in time from a particular instant, lasting a specified duration.
com.r3corda.core.contracts.Timestamp | If present in a transaction, contains a time that was verified by the uniqueness service. The true time must be between (after, before).
com.r3corda.core.node.services.TimestampChecker | Checks if the given timestamp falls within the allowed tolerance interval.
com.r3corda.core.testing.TimestampGenerator |
com.r3corda.core.messaging.TopicSession | An identifier for the endpoint MessagingService message handlers listen at.
com.r3corda.core.messaging.TopicStringValidator | A singleton thats useful for validating topic strings
com.r3corda.client.model.TrackedDelegate |
com.r3corda.node.services.messaging.TransactionBuildResult |
com.r3corda.node.api.TransactionBuildStep | Encapsulate a generateXXX method call on a contract.
com.r3corda.core.transactions.TransactionBuilder | A TransactionBuilder is a transaction class thats mutable (unlike the others which are all immutable). It is intended to be passed around contracts that may edit it by adding new states/commands. Then once the states and commands are right, this class can be used as a holding bucket to gather signatures from multiple parties.
com.r3corda.core.contracts.TransactionConflictException |
com.r3corda.client.model.TransactionCreateStatus |
com.r3corda.core.contracts.TransactionForContract | A transaction to be passed as input to a contract verification function. Defines helper methods to simplify verification logic in contracts.
com.r3corda.core.contracts.TransactionGraphSearch | Given a map of transaction id to SignedTransaction, performs a breadth first search of the dependency graph from the starting point down in order to find transactions that match the given query criteria.
com.r3corda.core.contracts.TransactionResolutionException |
com.r3corda.core.contracts.TransactionState | A wrapper for ContractState containing additional platform-level state information. This is the definitive state that is stored on the ledger and used in transaction outputs.
com.r3corda.core.testing.TransactionStateGenerator |
com.r3corda.core.node.services.TransactionStorage | Thread-safe storage of transactions.
com.r3corda.core.contracts.TransactionType | Defines transaction build & validation logic for a specific transaction type
com.r3corda.core.contracts.TransactionVerificationException |
com.r3corda.core.TransientProperty | A simple wrapper that enables the use of Kotlins "val x by TransientProperty { ... }" syntax. Such a property will not be serialized to disk, and if its missing (or the first time its accessed), the initializer will be used to set it up. Note that the initializer will be called with the TransientProperty object locked.
com.r3corda.protocols.TwoPartyDealProtocol | Classes for manipulating a two party deal or agreement.
com.r3corda.protocols.TwoPartyTradeProtocol | This asset trading protocol implements a "delivery vs payment" type swap. It has two parties (B and S for buyer and seller) and the following steps:
com.r3corda.core.node.services.TxWritableStorageService | Storage service, with extensions to allow validated transactions to be added to. For use only within ServiceHub.
com.r3corda.core.contracts.TypeOnlyCommandData | Commands that inherit from this are intended to have no data items: its only their presence that matters.
com.r3corda.node.utilities.UUIDStringColumnType | ColumnType for marshalling to/from database on behalf of UUID, always using a string representation.
com.r3corda.core.contracts.UniqueIdentifier | This class provides a truly unique identifier of a trade, state, or other business object, bound to any existing external ID. Equality and comparison are based on the unique ID only; if two states somehow have the same UUID but different external IDs, it would indicate a problem with handling of IDs.
com.r3corda.core.node.services.UniquenessException |
com.r3corda.core.node.services.UniquenessProvider | A service that records input states of the given transaction and provides conflict information if any of the inputs have already been used in another transaction.
com.r3corda.core.utilities.UntrustworthyData | A small utility to approximate taint tracking: if a method gives you back one of these, it means the data came from a remote source that may be incentivised to pass us junk that violates basic assumptions and thus must be checked first. The wrapper helps you to avoid forgetting this vital step. Things you might want to check are:
com.r3corda.node.services.User |
com.r3corda.protocols.ValidatingNotaryProtocol | A notary commit protocol that makes sure a given transaction is valid before committing it. This does mean that the calling party has to reveal the whole transaction history; however, we avoid complex conflict resolution logic where a party has its input states "blocked" by a transaction from another party, and needs to establish whether that transaction was indeed valid.
com.r3corda.node.services.transactions.ValidatingNotaryService | A Notary service that validates the transaction chain of he submitted transaction before committing it
com.r3corda.core.node.services.Vault | A vault (name may be temporary) wraps a set of states that are useful for us to keep track of, for instance, because we own them. This class represents an immutable, stable state of a vault: it is guaranteed not to change out from underneath you, even though the canonical currently-best-known vault may change as we learn about new transactions from our peers and generate new transactions that consume states ourselves.
com.r3corda.core.node.services.VaultService | A VaultService is responsible for securely and safely persisting the current state of a vault to storage. The vault service vends immutable snapshots of the current vault for working with: if you build a transaction based on a vault that isnt current, be aware that it may end up being invalid if the states that were used have been consumed by someone else first
com.r3corda.core.crypto.WhitelistTrustManager | Our TrustManager extension takes the standard certificate checker and first delegates all the chain checking to that. If everything is well formed we then simply add a check against our whitelist
com.r3corda.core.crypto.WhitelistTrustManagerProvider | Custom Security Provider that forces the TrustManagerFactory to be our custom one. Also holds the identity of the original TrustManager algorithm so that we can delegate most of the checking to the proper Java code. We simply add some more checks.
com.r3corda.core.crypto.WhitelistTrustManagerSpi | Registered TrustManagerFactorySpi
com.r3corda.node.services.network.WireNodeRegistration | A node registration and its signature as a pair.
com.r3corda.core.transactions.WireTransaction | A transaction ready for serialisation, without any signatures attached. A WireTransaction is usually wrapped by a SignedTransaction that carries the signatures over this payload. The hash of the wire transaction is the identity of the transaction, that is, its possible for two SignedTransactions with different sets of signatures to have the same identity hash.
com.r3corda.core.serialization.WireTransactionSerializer | A serialisation engine that knows how to deserialise code inside a sandbox
com.r3corda.contracts.testing.WiredTransactionGenerator |
com.r3corda.core.node.WorldCoordinate | A latitude/longitude pair.
com.r3corda.core.crypto.X509Utilities |