nim-libp2p
nim-libp2p copied to clipboard
Peer management
There is currently no peer management mechanisms in libp2p. This is required to maintain optimum connectivity across many user level provided protocols and applications.
Part of the requirement for the peer manager is to be able to collect and track metrics and statistics for the peer. Some that come to mind are:
- throughput
- latency
- overall bandwidth consumption
- age
- ???
In addition to the above, each application should be able to provide its own score for each peer, which is later aggregated and use by the peer manager to rebalance peers when a threshold, such as maximum peers is reached, cleaning up the lowest scored peers.
linking related issue from the waku project - https://github.com/status-im/nim-waku/issues/265