You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
In lisk-p2p phase2 from LIP0004, we are going to implement peer shuffling on outgoing connections.
Over the course of 30 blocks (approximately 5 minutes), one outgoing connection is chosen uniformly at random and terminated at a random time during the interval of 30 blocks.
We need to consider fixed and black peers list here to make sure we don't connect with blacklist peer and we don't drop connection with fixedlist peer.
The text was updated successfully, but these errors were encountered:
shuse2
transferred this issue from LiskArchive/lisk-elements
Apr 15, 2019
jondubois
changed the title
Add feature to maintain and shuffle the connected peers
Add feature to expire connected peers as part of shuffling algorithm
May 17, 2019
jondubois
changed the title
Add feature to expire connected peers as part of shuffling algorithm
Add feature to disconnect peers as part of shuffling algorithm
May 17, 2019
Based on a few discussions with @diego-G, it was decided to separate peer management into three concerns:
Populating the connected peer list up to a desired size.
Removing (and disconnecting) peers from the connected peer list (e.g. can be caused by banning, shuffling or failed internet connection).
Preventing invalid peers from connecting.
This issue should implement the 'removing' part of the shuffling. The populating algorithm will automatically replenish the list with a different peer from the network (just like it already does if an existing peer drops/loses their connection).
Description
In lisk-p2p phase2 from LIP0004, we are going to implement peer shuffling on outgoing connections.
Over the course of 30 blocks (approximately 5 minutes), one outgoing connection is chosen uniformly at random and terminated at a random time during the interval of 30 blocks.
We need to consider fixed and black peers list here to make sure we don't connect with
blacklist
peer and we don't drop connection withfixedlist
peer.The text was updated successfully, but these errors were encountered: