Get desktop application:
View/edit binary Protocol Buffers messages
Exchange EpochUpdate if either epoch is mismatched above.
Cryptographically verifies the tokens and then asks tokenmap if they are legitimate.
The id is meant to allow the receiver to easily track state. E.g., digest(salt||peer_addr||time||items) or just a counter.
Send the payment destination and requested amount.
Submits proposed payment without performing the transfer.
Propose as many methods as needed to settle the request. E.g., if there are two token classes based on mint PK, then there may be two methods.
A simplistic accept or abort. Change and other negotiations are possible.
Transfers/finalizes the agreed upon tokens.
TODO: determine if an explicit abort is useful. rpc Abort (AbortRequest) returns (AbortReply);
For each TransactionItem, supply proposed tokens Transmit the signed tokens. In practice, only the last token.History needs to be transferred since the tokens were sent in a prior call.
Acceptance allows the sender's copies of the tokens to be deleted. Otherwise, they can be resent.
(message has no fields)
Used in:
Associated amount
human readable name
human readable description, if appropriate
If conditional tokens are supported (or private tokens), this allows acceptance for specific items.
Used in:
default if empty.