Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Streaming of proposals is done on the "consensus_proposal" topic.
Contains all variants of mempool and an L1Handler variant to cover all transactions that can be in a new block.
Used in:
Used in:
Starknet version
State root of block `H-K`, where `K` is defined by the protocol's version.
The state diff commitment returned by the Starknet Feeder Gateway
Lets for the 5 preceding commitments. TODO: Just put the sizes explicitly? This is relatively free compared actually hashing the lists we commit to. If not, should we also pack other fields?
Identifies the content proposed (and executed). Consensus is reached on the value contained here.
Used in:
Used in:
Messages which make up a Proposal stream.
The content and stream_id are generic fields. The user of the stream can choose to pass whatever message that they want. The messages are then encoded in bytes.
Used in:
Marks the completion of the transaction streaming.
Used in:
Total number of transactions executed in the proposal.
We use a type field to distinguish between prevotes and precommits instead of different messages, to make sure the data, and therefore the signatures, are unambiguous between Prevote and Precommit.
This is optional since a vote can be NIL.
Identifies the voter.
Used in: