-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat: cycle peers in local storage #2018
Labels
enhancement
New feature or request
Comments
4 tasks
Adding quote from #1463 (comment):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a feature request
Problem
When a js-waku node is started and starts to discover nodes, using different discovery mechanisms, it starts to store successfully connected nodes in the local storage for faster bootstrapping when a js-waku node starts the next time.
This can lead to an aspect of potential centralisation where the node is attempting to connect to the same pool of nodes, stored in the localstorage.
Proposed Solutions
Cycle the list of nodes stored in localstorage when new nodes are found upon a restart.
Notes
The text was updated successfully, but these errors were encountered: