Proto commits in starknet-io/starknet-p2p-specs

These 97 commits are when the Protocol Buffers files have changed:

2026-04-09

Sync consensus proto and readme with sequencer repo - Add signature field to Vote message - Expand ProposalInit with block metadata (moved from BlockInfo) - Remove BlockInfo message - Add CommitmentParts, L2GasInfo, ProposalFinPayload messages - Add executed_transaction_count and fin_payload to ProposalFin - Simplify ProposalPart to init/fin/transactions only - Update consensus.md to reflect new message ordering

The documentation is generated from this commit.

2026-03-22

InvokeV3WithProof: change proof from uint32 to bytes (#78)

2026-03-19

InvokeV3WithProof: change proof from uint32 to bytes

2026-01-15

Merge pull request #76 from starknet-io/avivg/consensus_tx_documentation modify ConsensusTransaction documentation

modify ConsensusTransaction documentation

2026-01-14

modify InvokeV3 and add InvokeV3WithProof to allow client side proving

remove eth/strk conversion from block info, add prices in fri/wei

2026-01-13

remove eth/strk conversion from block info, add prices in fri/wei

2025-12-09

update consensus proto and readme files

2025-06-24

Add executed_transaction_count to consensus spec

2025-02-20

Add protocol describing the semantics of the consensus network messages

2025-01-13

add l2 gas with backward compatibility

2025-01-08

add l2 gas support (#64)

2024-12-08

Add CI to validate proto compilation (#59) * add ci to validate proto compilation * Setup CI and fixes to some .proto files (#61) * add quotations on main branch name * cr * testing changes * cleaning up and swaping to Noelware proto instead of installing * test protoc version * add missing syntax on capabilities.proto * attempting to fix compilation errors * adding Classes message to snapshot.proto * experimental-codegen * kernel * temp file instead of /dev/null * package transaction duplication * disable java compilation * remove package declaration * install protoc-gen-go before compiling to go * add option go_package specification * clean up * testing find *.proto * find proto step * compiling each file seperatly * apply changes to all compilations * clean comments * add --fatal_warnings flag to error on warnings * move state.proto back into sync dir * fix CR comments

2024-12-02

add option go_package specification

install protoc-gen-go before compiling to go

remove package declaration

disable java compilation

package transaction duplication

adding Classes message to snapshot.proto

attempting to fix compilation errors

add missing syntax on capabilities.proto

2024-12-01

fix bug in ConsensusStreamId (#53)

2024-11-25

move TransactionInBlock to sync directory

2024-11-21

add mempool and consensus transaction objects (#54)

2024-11-18

put all sync related files in sync directory (#47)

2024-11-17

fix: update protobuf specs with new consensus streaming (#52) * fix: update protobuf specs with new consensus streaming * fix: update the proto with ProposalPart and StreamMessage * fix: address reviewer comments * fix: further reviewer comments

2024-09-13

L1 handler message hash values are 256 bit This change introduces a new `Hash256` message type to describe fields that are hash values but cannot be represented as a Felt252. For example, message hashes for L1 messages are defined as Keccak256 hashes: https://docs.starknet.io/architecture-and-concepts/network-architecture/messaging-mechanism/#hashing_l1-l2 All other uses of the `Hash` message are _indeed_ hash function output either from the Starknet Poseidon or Pedersen hashes, so `Hash` should be parsed as a Felt252 value.

2024-08-04

add basic sync capabilities

2024-07-22

Merge pull request #42 from starknet-io/shahak/transaction_hash_and_class_hash add transaction hash and class hash

feat: add fields associated with starknet 0.13.2 upgrade (#40)

2024-07-15

add transaction hash and class hash

2024-07-04

Add proto for generic streaming.

2024-06-10

comments clarifications

difficulty comment

increased difficulty

comments clarifications

discovery messages

2024-05-26

add broadcasted transaction

2024-05-22

Remove parent_hash as we already have (block_number, fork_id). Also remove block_hash from ProposalFin. The fear is that some validators will mistakenly accept this instead of calculating and confirming it on their own.

Initial draft of consensus messages. This is set up for Proposal streaming and voting. Certificates for a quorum are part of the sync protocol, not consensus. Peer state sharing is considered a future optimization.

2024-05-09

Add detailed description to all protocols.

2024-03-28

Change header in order to support 0.13.1 blocks

remove redundant spacing

2024-02-19

Change header in order to support 0.13.1 blocks

2024-02-07

change time to unix encoding

remove repeated, add deployed and replaced contracts, remove delimeters, remove fin error message, unite signatures with header (#27)

2024-01-11

revert: adding consumed message in receipt common (#22) Refs: f47ec7c

Rename parent_header to parent_hash in BlockHeader

Add protocol_version and gas_price to BlockHeader

2023-12-08

revert: adding consumed message in receipt common Refs: f47ec7c

2023-12-07

Merge pull request #17 from starknet-io/IronGauntlets/update-receipts Update receipt.proto (#17) Co-Authored-By: Krzysztof Lis <klis33@gmail.com>

Merge pull request #12 from kirugan/kirugan/update-transaction-spec2 Changes to transaction spec (#12)

Add Transaction hash to Event message (#18) Co-authored-by: Krzysztof Lis <klis33@gmail.com>

2023-12-01

Add Transaction hash to Event message Co-authored-by: Krzysztof Lis <klis33@gmail.com>

Add Transaction hash to Event message Co-authored-by: Krzysztof Lis <klis33@gmail.com>

2023-11-29

Add output to Receipt.ExecutionResources

Rename receipt to type to avoid overloading names

Add MessageToL2 for Receipt.Common Co-authored-by: Krzysztof Lis <klis33@gmail.com>

Add `CurrentBlockHeaderRequest{}` The response to `CurrentBlockHeaderRequest{}` is the peer's local current header. This can be used to get a rough idea of what the latest block is as viewed by other peers on the network. The header can be compared with a subset of peers to determine an efficient way of pulling blocks from the network while syncing. Initially, we modified the iteration message to include a `latest` option, however, since the iteration message is shared by multiple requests it didn't make sense for each of the messages to have access to it.

Add `deployed_contracts` and `replaced_classes` to `StateDiff` To verify the state diff commitment we need to have access to all the fields present in the `StateDiff` returned by the feeder gateway. Therefore, we need to have `deployed_contract` and `replaced_classes` in the `StateDiff` messages. The reason for not including the `DeclaredV0Classes` and `DeclaredV1Classes` is because these can be derived from the `Classes` message, which all Cairo0 and Cairo1 classes can be mapped to `DeclaredV0Classes` and `DeclaredV1Classes`, respectively.

Add protocol_version and gas_price to BlockHeader

Rename parent_header to parent_hash in BlockHeader

2023-11-28

Add output to Receipt.ExecutionResources

Rename receipt to type to avoid overloading names

Add MessageToL2 for Receipt.Common Co-authored-by: Krzysztof Lis <klis33@gmail.com>

Add `CurrentBlockHeaderRequest{}` The response to `CurrentBlockHeaderRequest{}` is the peer's local current header. This can be used to get a rough idea of what the latest block is as viewed by other peers on the network. The header can be compared with a subset of peers to determine an efficient way of pulling blocks from the network while syncing. Initially, we modified the iteration message to include a `latest` option, however, since the iteration message is shared by multiple requests it didn't make sense for each of the messages to have access to it.

2023-11-23

Add `deployed_contracts` and `replaced_classes` to `StateDiff` To verify the state diff commitment we need to have access to all the fields present in the `StateDiff` returned by the feeder gateway. Therefore, we need to have `deployed_contract` and `replaced_classes` in the `StateDiff` messages. The reason for not including the `DeclaredV0Classes` and `DeclaredV1Classes` is because these can be derived from the `Classes` message, which all Cairo0 and Cairo1 classes can be mapped to `DeclaredV0Classes` and `DeclaredV1Classes`, respectively.

2023-11-21

Address comments for transaction changes from another PR-s

Remove unnecessary fields

Add contract_class_version field to Cairo1Class message

Fix name and order of fields in Cairo1EntryPoints

Update class definitions

2023-11-20

Remove class_hash from invoke transactions

Added nonce field for some of transaction types

Change tags for some of transaction fields

2023-11-17

Remove extra_data and hash from BlockHeader

2023-11-09

Add missing block header and body fields The block header is updated to allow for the P2P spec to be compatible with the RPC spec. Before these changes, p2p spec was not enough to serve to block RPC requests. Block bodies include Transactions and Receipts because RPC requires the block to have transactions and receipts. A peer could retrieve them in a separate request, however, since block bodies are retrieved over multiple messages I don't see much benefit in requesting them separately. Also, note Events were added to Receipt common because `BlockID` is not enough to determine which event belongs to which receipt. We require the events for the bloom filter.

Add `CurrentBlockHeaderRequest{}` The response to `CurrentBlockHeaderRequest{}` is the peer's local current header. This can be used to get a rough idea of what the latest block is as viewed by other peers on the network. The header can be compared with a subset of peers to determine an efficient way of pulling blocks from the network while syncing. Initially, we modified the iteration message to include a `latest` option, however, since the iteration message is shared by multiple requests it didn't make sense for each of the messages to have access to it.

2023-09-26

removed BlockID from header responses as it is redundant

2023-09-21

reintroduced BlockID, type clarifications

2023-09-12

added contracts and classes roots

added block hash as identity

2023-09-11

alignment

2023-09-07

moved to flattened transaction structure

removed included txs and added handling of mempool reorg

major feedback overhaul

2023-07-12

added comment on mempool

2023-07-10

misc

wqrearrange files

feedback changes checkpoint

2023-07-04

incorporated feedback

2023-06-28

added receipt, fixes

2023-06-27

revamped messages. initial pass. no documentation updates

2022-10-02

Draft spec for synching txn pool

2022-09-28

Spec for propagating a new transaction. Also fixing the InvokeTransaction message - include a nonce.

2022-09-11

protobuf definitions to separate proto files