From ethresear.ch
Work presented here has been carried out by the ProbeLab 1 team and in particular @guillaumemichel @cortze @dennis-tra and Steph.
High Level Description
The ProbeLab team has developed and deployed infrastructure to monitor several critical metrics for Ethereum’s CL discv5 DHT network. In particular, we have adapted the Nebula crawler (GitHub - dennis-tra/nebula: 🌌 A network agnostic DHT crawler, monitor, and measurement tool that exposes timely information about DHT networks.) to be compatible with discv5-based networks and are gathering results that reflect the health of the P2P network at the DHT level.
In this post we’re presenting a summary of what is included in the reports, but for a more complete picture of what’s there, head to: https://probelab.io/ethereum/discv5/2024-29/ 1 for the latest report.
- Reports are produced every Monday for the preceding week.
- The methodology we follow for DHT Crawling, Data Filtering, Node Classification as well as the differences of our tool to alternatives in the space is given in the Methodology section: https://probelab.io/ethereum/discv5/methodology/.
- The crawler used to produce the reports can be found (and can be reused) here: GitHub - dennis-tra/nebula: 🌌 A network agnostic DHT crawler, monitor, and measurement tool that exposes timely information about DHT networks..
Why you should care
The metrics included in the reports:
- give an overview of the network structure, size and client adoption breakdown. This helps in understanding the robustness and diversity of the network,
- provide accurate geographic distribution of nodes in the network per client implementation over time, which can highlight regional trends and potential vulnerabilities or strengths in specific areas,
- make it easy to spot drastic changes in the structure and setup of the network,
- allow for monitoring of new protocol version uptake/adoption, and provide insights on whether there are adoption barriers,
- reveal the infrastructure setup (e.g., data center-hosted vs non-data center-hosted) and cloud provider distribution per client implementation,
- show the breakdown of nodes supporting particular network-layer protocols,
- depict the percentage of reachable vs unreachable node records in the DHT network.
Overview of Results
We’re presenting a small fraction of the results given at https://probelab.io to give an idea of the metrics listed. Please head there for the complete reports from Week 11 (mid-March), 2024.
Client Diversity
discv5-agents-overall1568×1200 26.5 KB
Client Diversity Over Time
discv5-agents-overall-stacked1568×1200 67.6 KB
Agent version adoption over time - Example: Lighthouse
discv5-versions-distribution1568×1200 80.1 KB
discv5-agents-versions1568×1200 27.8 KB
Country distribution of all nodes
discv5-geo-agent-all-bars1568×1200 28.3 KB
Client-specific country distribution - Example: Prysm
discv5-geo-agents-lines-prysm1568×1200 78.7 KB
Cloud provider distribution of all nodes
discv5-cloud-agent-all-bars1568×1200 44.7 KB
Cloud vs non-cloud distribution of nodes over time
discv5-cloud-rate-agent-all-lines1568×1200 35.9 KB
Stale Peer Records over time
discv5-stale-records-mainnet-stacked1568×1200 48.1 KB
How to contribute
Overall, we believe this set of results give an accurate view of the structure and health of the discv5 DHT network. We hope you’ll find the reports useful.
If there are important metrics that you believe should be part of these weekly reports, comment below, or get in touch with the team: probelab.network/contact.
All Comments