-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat: peer scoring strategies for light protocols #2017
Comments
scoring was decided to not be introduced for the scope of js-waku currently (ref: #1463 (comment), #1463 (comment)) as js-waku is a relatively short-lived connection when compared to its full-node counterparts where scoring offers a much more substantial advantage.
We do this part of finding connections to peer currently: peers with lowest latency are given priority |
Agree that we have no deliverable in this issue. Iceboxing for now |
This is a feature request
Problem
Peer scoring for light protocols should improve overall quality of peers being used by a node. This should drive satisfaction from the service provided as well as perceived reliability.
Proposed Solutions
Filter scoring:
Filter scoring (with use of Store):
Light push scoring (with use of Filter):
Other strategies that might be used(each should be discussed):
Notes
Decoupled from discussions in #1463
The text was updated successfully, but these errors were encountered: