You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, enabling DiscV5 mechanism requires multiaddresses upon node handle initialization, while DNS discovery takes enrtree url and resolves to multiaddresses after node initialization.
It would be nice if the two mechanisms are consistent, potentially
DiscV5 can be initialized with a ENRtree url instead of a set of multiaddresses
DiscV5 can be enabled after the initialization of the node
Or if an ENRtree url can be optionally supplied with a toggle for discovery mechanisms, between static list, DNS discovery, DiscV5, ...
A potential flow is
Initialize waku node, use DNS url to get bootstrap nodes
Connect to bootstrap nodes either by DNS discovery or enable DiscV5
Remember "good" peers to use in DiscV5 when node gets restarted
The text was updated successfully, but these errors were encountered:
At the moment, enabling DiscV5 mechanism requires multiaddresses upon node handle initialization, while DNS discovery takes enrtree url and resolves to multiaddresses after node initialization.
It would be nice if the two mechanisms are consistent, potentially
A potential flow is
The text was updated successfully, but these errors were encountered: