-
Notifications
You must be signed in to change notification settings - Fork 3
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
Spike: Refine discv5 peer discovery process #269
Labels
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
p0
Critical priority
size:medium
Medium
type:bug
Something isn't working
Comments
hopeyen
added
type:bug
Something isn't working
size:medium
Medium
p2
Medium priority
labels
Aug 14, 2023
hopeyen
added
p0
Critical priority
and removed
meta:awaiting-triage
p2
Medium priority
labels
Sep 18, 2023
pete-eiger
added
the
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
label
Sep 21, 2023
hopeyen
removed
the
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
label
Sep 21, 2023
Steps we take in exploring node connectivity:
We can expect log outputs
Seemingly working, so let's update the mainnet bootnodes as well with the same standard ENR as the bootstrap nodes. The current radio should already be using our bootnodes for discv5 mechanism |
pete-eiger
added
the
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
label
Oct 2, 2023
Next steps on message routing in this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
p0
Critical priority
size:medium
Medium
type:bug
Something isn't working
Describe the bug
We have not seen a radio that connects to more than 2 peers even though discv5 is enabled by default and there are more than 2 active indexers for certain deployments
Expected behavior
Active peer number should be within a small threshold of active indexer number
Notes for random walk discovery
Waku Discv5
Ethereum devp2p
When the node set is large or requested property is poor, the random walk will take longer between 2 nodes. Waku implemented the protocol for dedicated discovery network so nodes can query this discovery network for a random set of nodes and all (well-behaving) returned nodes can serve as bootstrap nodes for other Waku2 protocols.
Each node is represented by a node record (ENR). They are organized into a DHT based on their IP addresses, which in our case contains a UDP port. The distance between two nodes is the number of hops it takes to reach the other node through the DHT (random walk distance can only be >= DHT distance).
Each node maintains its own local node record and is updated periodically by querying other nodes in the DHT.
They establish sessions with each other to exchange messages. They establish a session by performing a handshake and exchange their node records. In the session they could discover new nodes, exchange node records, and perform other tasks.
Search: Nodes can search for other nodes by IP address, UDP port, or topic.
The text was updated successfully, but these errors were encountered: