package binance.tsslib

Get desktop application:
View/edit binary Protocol Buffers messages

Wrapper for TSS messages, often read by the transport layer and not itself sent over the wire

• bool is_broadcast = 1

  Metadata optionally un-marshalled and used by the transport to route this message.

• bool is_to_old_committee = 2

  Metadata optionally un-marshalled and used by the transport to route this message.

  used only in certain resharing messages

• bool is_to_old_and_new_committees = 5

  Metadata optionally un-marshalled and used by the transport to route this message.

  used only in certain resharing messages

• optional MessageWrapper.PartyID from = 3

  Metadata optionally un-marshalled and used by the transport to route this message.

• repeated MessageWrapper.PartyID to = 4

  Metadata optionally un-marshalled and used by the transport to route this message.

• optional google.protobuf.Any message = 10

  This field is actually what is sent through the wire and consumed on the other end by UpdateFromBytes. An Any contains an arbitrary serialized message as bytes, along with a URL that acts as a globally unique identifier for and resolves to that message's type.

PartyID represents a participant in the TSS protocol rounds. Note: The `id` and `moniker` are provided for convenience to allow you to track participants easier. The `id` is intended to be a unique string representation of `key` and `moniker` can be anything (even left blank).

Used in: MessageWrapper

• string id = 1

• string moniker = 2

• bytes key = 3

Container for output signatures, mostly used for marshalling this data structure to a mobile app

• bytes signature = 1

• bytes signature_recovery = 2

  Ethereum-style recovery byte; only the first byte is relevant

• bytes r = 3

  Signature components R, S

• bytes s = 4

• bytes m = 5

  M represents the original message digest that was signed M