-
Notifications
You must be signed in to change notification settings - Fork 41
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
Use DNS Discovery by default #517
Comments
|
Must be done first and some dogfooding needs to happen before we can consider dns discovery ready. |
Wouldn't we need for the PR to be merged before we can test it in our example? How would we go about using an unmerged/unreleased version without building locally? |
I think what @fryorcraken suggests is to hide if behind a feature flag so that consumers can pass an option and use experimental functionality intentionally without breaking old contract. |
My bad. |
Update: DNS Discovery used in the web-chat example here waku-org/examples.waku.org#190 |
Merged! |
Problem
DNS Discovery is a more decentralized and flexible strategy than using the (hardcoded) predefineded Status nodes.
We expect node operators and platforms to use DNS Discovery (either Status' one or their own) until more dynamic discovery mechanisms are in place (such as peer exchange).
Definition of Done
createLightClient
The text was updated successfully, but these errors were encountered: