-
Notifications
You must be signed in to change notification settings - Fork 12
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
Subnet service #115
Subnet service #115
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for starting this! I added some comments.
{ | ||
error!(?err, subnet = *subnet, "can't subscribe"); | ||
} | ||
self.swarm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly, Lighthouse doesn't do that. There could be a check somewhere else (PeerManager?) that keeps the target number of peers for each subnet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think we should check the peer_store
before trying to discover. Will add this in my simplified peer manager PR.
6849e86
to
af77b69
Compare
Pushed a new design based on #117. Also pulled out the logic from |
Co-authored-by: diegomrsantos <[email protected]>
82a062c
to
4b5e32f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks amazing!
Proposed Changes
Small service that gets notified when a validator gets added or removed and passes on instructions to subscribe/unsubscribe/look for peers