Get desktop application:
View/edit binary Protocol Buffers messages
* A transaction body to publish a node's Common Reference String (CRS) to the network. This is used when node wants to update to reach the final CRS for network to use the hinTS protocol
Used in:
* The party's generated random CRS.
* The party's proof of the CRS update.
* A transaction body to publish a node's hinTS key for a certain party id and number of parties. A hinTS key is an extended public key; that is, a BLS public key combined with "hints" derived from the matching private key that a signature aggregator can use to prove well-formedness of an aggregate public key by an efficiently verifiable SNARK.
Used in:
* The party id for which the hinTS key is being published; must be in the range [0, num_parties). <p> This value MUST be set to a non-negative integer.<br/>
* The number of parties in the hinTS scheme.
* The party's hinTS key.
* A transaction body to publish a node's hinTS partial signature on a particular message for a certain construction id.
Used in:
* The id of the hinTS construction this partial signature applies to. (The size of the target roster for this construction implies what hinTS party id the submitting node has in the construction; and hence also what weight the node's signature has.)
* The message being signed.
* The node's partial signature on the message.
* A transaction body to publish a node's vote for the results of aggregating the hinTS keys for a specified construction id. The node can either give their explicit aggregation results, or delegate their vote to another node's results.
Used in:
* The id of the hinTS construction this vote is for. Because the network only ever performs one construction a time, this is somewhat redundant, but included to detect any strange edge cases where a node is so far behind it votes on the wrong construction.
* The vote the node is casting for the aggregation of the hints in the given construction (which should be ongoing).