Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move kad to the end of the protocol name #62

Merged
merged 1 commit into from
Dec 9, 2024
Merged

move kad to the end of the protocol name #62

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ There are three different networks that serve different type of applications:
* Consensus - responsible for creating and adding new blocks to Starknet via staking

Each network has a separate discovery network. The Kademlia protocol names for those networks are:
* /starknet/kad/<chain_id>/sync/1.0.0
* /starknet/kad/<chain_id>/mempool/1.0.0
* /starknet/kad/<chain_id>/consensus/1.0.0
* /starknet/<chain_id>/sync/kad/1.0.0
* /starknet/<chain_id>/mempool/kad/1.0.0
* /starknet/<chain_id>/consensus/kad/1.0.0

A node that wants to connect to multiple networks should connect through a different port for each network.

Expand Down
12 changes: 6 additions & 6 deletions p2p/proto/sync/protocols.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,12 @@ The following table describes the different protocols in Starknet, the name that
negotiation, and the protobuf messages related to the protocol.
| Protocol | Name (for negotiation) | Request Message | Response Message |
| ------------ | -------------- | -------------- | -------------- |
| Headers | /starknet/headers/0.1.0-rc.0 | [BlockHeadersRequest](./header.proto) | [BlockHeadersResponse](./header.proto) |
| StateDiffs | /starknet/state_diffs/0.1.0-rc.0 | [StateDiffsRequest](./state.proto) | [StateDiffsResponse](./state.proto) |
| Classes | /starknet/classes/0.1.0-rc.0 | [ClassesRequest](./class.proto) | [ClassesResponse](./class.proto) |
| Transactions | /starknet/transactions/0.1.0-rc.0 | [TransactionsRequest](./transaction.proto) | [TransactionsResponse](./transaction.proto) |
| Events | /starknet/events/0.1.0-rc.0 | [EventsRequest](./event.proto) | [EventsResponse](./event.proto) |
| Kademlia (for discovery) | /starknet/kad/<chain_id>/sync/1.0.0 |
| Headers | /starknet/<chain_id>/sync/headers/0.1.0-rc.0 | [BlockHeadersRequest](./header.proto) | [BlockHeadersResponse](./header.proto) |
| StateDiffs | /starknet/<chain_id>/sync/state_diffs/0.1.0-rc.0 | [StateDiffsRequest](./state.proto) | [StateDiffsResponse](./state.proto) |
| Classes | /starknet/<chain_id>/sync/classes/0.1.0-rc.0 | [ClassesRequest](./class.proto) | [ClassesResponse](./class.proto) |
| Transactions | /starknet/<chain_id>/sync/transactions/0.1.0-rc.0 | [TransactionsRequest](./transaction.proto) | [TransactionsResponse](./transaction.proto) |
| Events | /starknet/<chain_id>/sync/events/0.1.0-rc.0 | [EventsRequest](./event.proto) | [EventsResponse](./event.proto) |
| Kademlia (for discovery) | /starknet/<chain_id>/sync/kad/1.0.0 |

In addition, nodes should also support the `Identify` protocol, who's name for negotiation is
`/ipfs/id/1.0.0`
Expand Down
Loading