Open
Description
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:
- Subscribe to 2 peers and compare if 1st broadcasts messages faster than 2nd;
Filter scoring (with use of Store):
- Check if any of present subscriptions misses any messages by using store pings;
Light push scoring (with use of Filter):
- Check if a message sent through peer A was relayed from any of the Filter subscriptions;
Other strategies that might be used(each should be discussed):
- Pretense of Relay protocol is beneficial for other protocols;
- If we know IP we can try to decide if a peer is close to us geographically (note that these should not be the only peers a node is using but some);
- Investigate if libp2p ping can be used to measure latency;
- Blacklist peers that drop connection with us more than once;
- Monitor errors during Filter ping / Filter subscribe / Lightpush send and other operations within protocols - decrease score for such peers;
Notes
Decoupled from discussions in #1463
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Icebox