fibercrypto / fibercrypto/skycoin
Connection Pool: Should be Three Peer Lists
- Dominant language
- Go
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
1> Trusted Peers: First list is peers that are configured by hand by node owner. Should always to connect to all peers on list. Peers should not count towards the connection pool and should not disconnect peers if over connection pool limit.
2> Default Peers: Second list of default peers. Bootstrap peers.
- should count towards connection pool limit
- can be configured by user (user can add more peers to list)
3> Automatic Peers: Third is list of automatic peers (from peer exchange)
- are peers that come in through peer exchange.
- should count towards connection pool limit
-------
The three peer lists should be stored separately. Or can be stored together, with a field for determining the type of peer.
The client will attempt to connect to all peers in list 1.
The client will choose randomly between peers in list 2 and 3 for selecting new peers to connect to
There should be an option for disabling automatic peers.
The interface in the networking tab must be updated to show the list of each peer
- list of default peers and automatic peers should be sorted with the connected peers at the top
Data should be recorded for each peer
- should last time connected
- show connection status (connected, disconnected, etc)
Add "max trusted peer connections" parameter
- if "max trusted peer connections" is set, then client will connecting to new peers on the trusted peer list until a maximum of N trusted peers connections has been reached
-------
Right now there are 2 peer lists.
The default peers are going on peer list 1
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.