-
Notifications
You must be signed in to change notification settings - Fork 197
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
Conversation
7a7d296
to
fc245de
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
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. 🚀 New features to boost your workflow:
|
b0b5de8
to
8dec96e
Compare
There was a problem hiding this 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?
8dec96e
to
8ce0d16
Compare
@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 |
1da486c
to
0e85e86
Compare
0e85e86
to
f705e54
Compare
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.