We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently there's no node discovery for Waku, but we instead use hardcoded static nodes.
The most basic form of node discovery, as was previously investigated, is likely https://eips.ethereum.org/EIPS/eip-1459
See https://rfc.vac.dev/spec/6/#node-discovery and https://vac.dev/dns-based-discovery
Additionally, corresponding update in Waku v2 recommending the use of DNS based discovery (identical to Waku v1)
As a further enhancement, we can look into using Discovery v5 module like Nimbus, but this isn't initially needed.
cc @jm-clius fyi on practical next steps re discovery once we think this is a priority
UPDATE 2021-06-14:
raw
The text was updated successfully, but these errors were encountered:
wakuv2.prod
wakuv2.test
nim-waku
jm-clius
No branches or pull requests
Problem
Currently there's no node discovery for Waku, but we instead use hardcoded static nodes.
Solution
The most basic form of node discovery, as was previously investigated, is likely https://eips.ethereum.org/EIPS/eip-1459
See https://rfc.vac.dev/spec/6/#node-discovery and https://vac.dev/dns-based-discovery
Additionally, corresponding update in Waku v2 recommending the use of DNS based discovery (identical to Waku v1)
As a further enhancement, we can look into using Discovery v5 module like Nimbus, but this isn't initially needed.
cc @jm-clius fyi on practical next steps re discovery once we think this is a priority
UPDATE 2021-06-14:
Subtasks:
raw
specification vacp2p/rfc#398: Createraw
specificationThe text was updated successfully, but these errors were encountered: