Scope Discovery: Custom Kad-DHT + Connection Gating #4939
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problems
EOF.Rationale
A custom Kad-DHT protocol prefix isolates our routing table from the public DHT and keeps discovery Harmony-only.
Connection gating blocks or immediately tears down non-Harmony peers at the transport layer (pre-dial/accept and post-identify), preserving capacity for legitimate Harmony traffic.
Changes
/harmony/kad/1.0.0) and use only configured Harmony bootnodes.Notes:
No changes to PubSub topics, scoring, or connmgr here (follow-ups if needed).
Rollout
Success criteria