Skip to content
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

Registry: Implement server-side seeding #2874

Closed
Geod24 opened this issue Jan 18, 2022 · 0 comments · Fixed by #3320
Closed

Registry: Implement server-side seeding #2874

Geod24 opened this issue Jan 18, 2022 · 0 comments · Fixed by #3320
Assignees
Labels
type-enhancement An improvement of existing functionalities

Comments

@Geod24
Copy link
Collaborator

Geod24 commented Jan 18, 2022

When a node first start, from a clean configuration, it needs to connect to a set of peer and download the chain.
We implemented this client side a while ago (#19) but it was never implemented server side.

We should be able to do an A / AAAA query on a zone (probably the realm itself, but open to discussion, as the same idea might apply to flash) and get a "well distributed" set of nodes. Well distributed meaning that at least X validators are included (X to be decided based on the number of active validators), and the rest being staking nodes (ideally, but this requires #2867). Obviously there must be a maximum numbers of nodes that will be included in the response, and the nodes should be round-robin-ed on a timely basis (not per request, I think, to avoid people using it as a way to discover the network).

Note that the main part of this issue can be done without #2867 : it's fine if the initial implementation just return validators.

@Geod24 Geod24 added the type-enhancement An improvement of existing functionalities label Jan 18, 2022
@Geod24 Geod24 added this to the 6. Stabilization milestone Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-enhancement An improvement of existing functionalities
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants