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.

Notify all involved parties about a transaction, including storing a copy. Normally this would be called via FinalityProtocol.

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.

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

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

Finalise a transaction by notarising it, then recording it locally, and then sending it to all involved parties.

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.

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.

Abstract superclass for request messages sent to services which expect a reply.

Thrown when a participant refuses the proposed state replacement

Classes for manipulating a two party deal or agreement.

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:

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.

Sends a ServiceRequestMessage to target and returns a ListenableFuture of the response.