-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Peer Management #639
Comments
This was referenced Dec 3, 2018
Merged
InoMurko
pushed a commit
that referenced
this issue
Dec 4, 2018
Peer rating and reputation system:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when we run our sync code, we start two supervisors:
ExWire.PeerSupervisor
andExWire.TCP.InboundConnectionsSupervisor
. The latter is used for inbound connections, which isn't heavily supported right now. ForExWire.PeerSupervisor
, when we're running discovery mode, we connect to peers as they are discovered until we reach a certain count of max peers (currently hard-coded). We don't try to connect to other peers when our connected peers drop, and again, we ignore any inbound connections. This is pretty poor behavior.This issue is to improve peer connection management. It should do a variety of tasks:
This will require a good amount of work, but it's vital to getting a healthy node up and running.
The text was updated successfully, but these errors were encountered: