Peer discovery & management

[hopeyen]

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

1. DiscV5 can be initialized with a ENRtree url instead of a set of multiaddresses
2. DiscV5 can be enabled after the initialization of the node
3. 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

1. Initialize waku node, use DNS url to get bootstrap nodes
2. Connect to bootstrap nodes either by DNS discovery or enable DiscV5
3. Remember "good" peers to use in DiscV5 when node gets restarted

[harsh-98]

Weekly Update

• achieved: Worked mainly on rust-waku-bindings issues for go-waku.
• next: Handle epic 2.2

[richard-ramos]

Weekly Update

• achieved: Added dns discovery parameters to the node config