Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Contains all transaction types that can be in a new block: - User transactions (same types as MempoolTransaction: Declare, DeployAccount, Invoke) - L1Handler transactions (messages from L1, not propagated via mempool)
Used in:
L2 gas info for the block (next price and gas used).
Used in:
Used in:
Identifies a Starknet block based on the content streamed in the proposal.
Number of executed transactions in the proposal.
Optional payload carried in ProposalFin: commitment parts and L2 gas.
Used in:
Used in:
Network format: 1. First message is ProposalInit (init, includes all block metadata) 2. transactions is sent repeatedly (for non-empty blocks) 3. Last message is ProposalFin
Used in:
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.
Used in: