com.r3corda.protocols

Package com.r3corda.protocols

Types

AbstractRequestMessage abstract class AbstractRequestMessage : ServiceRequestMessage
FetchAttachmentsProtocol class FetchAttachmentsProtocol : FetchDataProtocol<Attachment, ByteArray>

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.

FetchDataProtocol abstract class FetchDataProtocol<T : NamedByHash, W : Any> : ProtocolLogic<Result<T>>

An abstract protocol for fetching typed data from a remote peer.

FetchTransactionsProtocol class FetchTransactionsProtocol : FetchDataProtocol<SignedTransaction, SignedTransaction>

Given a set of tx hashes (IDs), either loads them from local disk or asks the remote peer to provide them.

NotaryError sealed class NotaryError
NotaryProtocol object NotaryProtocol
RatesFixProtocol open class RatesFixProtocol : ProtocolLogic<Unit>

This protocol queries the given oracle for an interest rate fix, and if it is within the given tolerance embeds the fix in the transaction and then proceeds to get the oracle to sign it. Although the call method combines the query and signing step, you can run the steps individually by constructing this object and then using the public methods for each step.

ResolveTransactionsProtocol class ResolveTransactionsProtocol : ProtocolLogic<Unit>

This protocol fetches each transaction identified by the given hashes from either disk or network, along with all their dependencies, and verifies them together using a single TransactionGroup. If no exception is thrown, then all the transactions have been successfully verified and inserted into the local database.

ServiceRequestMessage interface ServiceRequestMessage

Abstract superclass for request messages sent to services, which includes common fields such as replyTo and replyToTopic.

TwoPartyDealProtocol object TwoPartyDealProtocol

Classes for manipulating a two party deal or agreement.

TwoPartyTradeProtocol object 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:

ValidatingNotaryProtocol class ValidatingNotaryProtocol : Service

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

Exceptions

NotaryException class NotaryException : Exception