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
In go-filecoin when a node fails the hello protocol (because they have a different genesis block or wrong version) we disconnect from them. However, we will frequently reconnect to them immediately. This is undesirable as we would prefer to not reconnect to this peer again for some time.
A solution we initially considered was the Backoff method in go-libp2p-swarm, but we were informed this component is for internal use only.
Acceptance criteria
As a developer I can configure my application to:
avoid reconnecting to a peer for some configurable amount of time. (e.g. in go-filecoin a peer may keep the same peerID but update its version, we would not want to blacklist a peer in this scenario).
Completely blacklist a peer from reconnecting.
The text was updated successfully, but these errors were encountered:
Description
In go-filecoin when a node fails the hello protocol (because they have a different genesis block or wrong version) we disconnect from them. However, we will frequently reconnect to them immediately. This is undesirable as we would prefer to not reconnect to this peer again for some time.
A solution we initially considered was the Backoff method in go-libp2p-swarm, but we were informed this component is for internal use only.
Acceptance criteria
The text was updated successfully, but these errors were encountered: