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.

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

Set correct DHT protocol to match Starknet P2P v0.1 #2380

Closed
wants to merge 2 commits into from

Conversation

wojciechos
Copy link
Contributor

@wojciechos wojciechos commented Jan 15, 2025

Updated DHT protocol naming to align with Starknet P2P v0.1 spec and added a test.

Changes:
• Fixed incorrect DHT protocol naming:
• Before: /starknet/kad/1.0.0 (not matching any Starknet P2P spec)
• After: /starknet/kad/SN_MAIN/1.0.0 (matches v0.1)
• Added a test to validate the correct protocol format.

@wojciechos wojciechos force-pushed the wojciechos/adjust-p2p-naming branch 2 times, most recently from 7a7d296 to fc245de Compare January 15, 2025 12:56
Copy link

codecov bot commented Jan 15, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.42%. Comparing base (1caf86f) to head (f705e54).
Report is 121 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2380   +/-   ##
=======================================
  Coverage   74.41%   74.42%           
=======================================
  Files         113      113           
  Lines       13016    13016           
=======================================
+ Hits         9686     9687    +1     
- Misses       2592     2594    +2     
+ Partials      738      735    -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@wojciechos wojciechos added the P2P label Jan 15, 2025
@wojciechos wojciechos force-pushed the wojciechos/adjust-p2p-naming branch 3 times, most recently from b0b5de8 to 8dec96e Compare January 16, 2025 09:28
@wojciechos wojciechos marked this pull request as ready for review January 16, 2025 09:31
Copy link
Contributor

@AnkushinDaniil AnkushinDaniil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you tested sync with Pathfinder?

@wojciechos wojciechos force-pushed the wojciechos/adjust-p2p-naming branch from 8dec96e to 8ce0d16 Compare January 27, 2025 09:53
@wojciechos
Copy link
Contributor Author

wojciechos commented Jan 27, 2025

Have you tested sync with Pathfinder?

@AnkushinDaniil Yep, I tested, but Pathfinder hasn’t updated to the latest P2P spec, which is why it can’t sync with each other. See here

@wojciechos wojciechos marked this pull request as draft January 30, 2025 11:30
@wojciechos wojciechos force-pushed the wojciechos/adjust-p2p-naming branch from 1da486c to 0e85e86 Compare January 31, 2025 12:05
@wojciechos wojciechos marked this pull request as ready for review January 31, 2025 12:05
@wojciechos wojciechos changed the title Ensure p2p protocol matches new Starknet spec Set correct DHT protocol to match Starknet P2P v0.1 Jan 31, 2025
@wojciechos wojciechos force-pushed the wojciechos/adjust-p2p-naming branch from 0e85e86 to f705e54 Compare January 31, 2025 15:01
@wojciechos wojciechos closed this Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants