Keeping track of validator set distribution with ease.

As part of our commitment to decentralization as well as efforts to identify and minimize risks related to validator operators, Lido is pleased to present VaNOM - validator and node metrics reports for Lido on Ethereum

Check out VaNOM here.

There are automated ways to collect and present metrics over Node Operators participating in Lido and the validators which they run, and Lido supports these initiatives via LEGO grants and contributors work closely with these providers to ensure that the data is as accurate and complete as possible. While Lido is working on incorporating this data into its own metrics, this data is not always accurate as it approaches the data collection problem using heuristics.

For Lido’s reporting, the main data set consists of self-reported data from Node Operators who participate in the protocol, collate, clean, and aggregate the data for reporting. Previously, there was no good way to track or compare the metrics across different periods, but with improvements to the data gathering and reporting processes it is now easier to incorporate updates consistently across different reporting periods.

What is VaNOM?

The Lido on Ethereum validator and node operator metrics app ('VaNOM') allows users to view a variety of metrics related to the protocol's validator distribution across specific points in time. VaNOM provides a more granular method for users to view the infrastructure distribution of Node Operators participating in the protocol, adding transparency and visibility into Lido’s status and health. The metrics presented include information about client diversity, infrastructure, geolocation, and jurisdiction dispersion.

Using VaNOM For 'Lido on Ethereum' Insights

In order to paint a more accurate picture of the protocol’s status, we consolidate various data sources, including on-chain data, self-reported information, and other metrics gathered through third party APIs such as Rated and Miga-labs.

For example, using VaNOM users can see the use of both execution and consensus clients across the various Node Operators. It also shows some interesting quarter-to-quarter changes, for example, a shift in client diversity post-merge for both execution and consensus layer clients, which can also be compared to the overall Ethereum network. However, due to the limitations of the network wide data collection methods, it's important to be careful when comparing these different sources.

By tracking these metrics, users can gain valuable insights into how the protocol is performing and identify potential areas of over-reliance. Based on such data, we can make informed decisions on areas of future iteration and focus.

What's Next?

Lido is constantly evolving and improving, we are always working on new features and improvements. In the future, we plan to add additional features such as a side-by-side comparison of different time periods, improving the granularity of data, and the inclusion of other data sources so that users can directly compare the different data sets to each other (e.g. self-report, rated.network, realtime on-chain data, etc).

As always, it is very helpful to have a community of fellow users to exchange ideas. We welcome your feedback and comments. Please reach out to us via our Discord, Forums, or email.