package briolette.receiver

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc Gossip (GossipRequest, GossipReply)

  receiver.proto:26

  Exchange EpochUpdate if either epoch is mismatched above.

  message GossipRequest

  receiver.proto:66

  • bytes tx_id = 1

  • optional clerk.EpochUpdate epoch_update = 2

  message GossipReply

  receiver.proto:71

  • optional clerk.EpochUpdate epoch_update = 1

• rpc Initiate (InitiateRequest, InitiateReply)

  receiver.proto:24

  Cryptographically verifies the tokens and then asks tokenmap if they are legitimate.

  message InitiateRequest

  receiver.proto:40

  • Version version = 1

  • optional clerk.EpochData epoch = 2

  • bytes epoch_signature = 3

  message InitiateReply

  receiver.proto:46

  • bytes tx_id = 1

    The id is meant to allow the receiver to easily track state. E.g., digest(salt||peer_addr||time||items) or just a counter.

  • optional clerk.EpochData epoch = 2

  • bytes epoch_signature = 3

  • optional token.SignedTicket ticket = 4

    Send the payment destination and requested amount.

  • repeated TransactionItem items = 5

• rpc Transact (TransactRequest, TransactReply)

  receiver.proto:28

  Submits proposed payment without performing the transfer.

  message TransactRequest

  receiver.proto:75

  • bytes tx_id = 1

  • repeated TransactionItemMethod methods = 2

    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.

  message TransactReply

  receiver.proto:86

  • bool accept = 1

    A simplistic accept or abort. Change and other negotiations are possible.

• rpc Transfer (TransferRequest, TransferReply)

  receiver.proto:30

  Transfers/finalizes the agreed upon tokens.

  TODO: determine if an explicit abort is useful. rpc Abort (AbortRequest) returns (AbortReply);

  message TransferRequest

  receiver.proto:92

  • bytes tx_id = 1

  • repeated token.Token tokens = 2

    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.

  message TransferReply

  receiver.proto:100

  • bool accepted = 1

    Acceptance allows the sender's copies of the tokens to be deleted. Otherwise, they can be resent.

(message has no fields)

• bytes tx_id = 1

Used in: InitiateReply

• optional token.Amount amount = 1

  Associated amount

• string name = 2

  human readable name

• string description = 3

  human readable description, if appropriate

• repeated bytes supported_mint_public_keys = 4

  If conditional tokens are supported (or private tokens), this allows acceptance for specific items.

Used in: TransactRequest

• repeated token.Token tokens = 1

• bytes mint_public_key = 2

  default if empty.