Skip to main content

Consensus Client Distribution for "Lodestar"

Bug Reports

Previously, the Rated explorer would be able to detect Lodestar clients on the network. As of today, this is no longer the case as we know with certainty that ChainSafe is running 100% Lodestar as part of its staking setup:

https://explorer.rated.network/o/ChainSafe%20-%20Lido?network=mainnet&timeWindow=30d&idType=poolShare

If Rated uses Sigma Prime’s Blockprint API to identify client usage, there was a bug that was fixed when graffiti standards changed by default via

https://github.com/ethereum/execution-apis/pull/517 and the regex detection mechanism was fixed on Blockprint via

https://github.com/sigp/blockprint/issues/36.

We want to ensure coverage of Lodestar is accurately represented on your explorer, thanks!

Posted by Philip Ngo ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • Robert Tiong

    •

    Mar 7, 2025

    Hi @Philip Ngo! We’ve upgraded the version of Blockprint we’re running. :)

    You should now see the updated distribution of Lodestar now across the network and for Chainsafe:

    https://explorer.rated.network/o/ChainSafe?network=mainnet&timeWindow=30d&idType=nodeOperator

    We’re not entirely sure why it’s not reflecting 100% Lodestar for Chainsafe though. Might be due to the probabilistic nature of the model? What do you think?

    • Philip Ngo

      •

      Mar 10, 2025

      Hey Robert! Thanks for the update. Blockprint should always be treated as a “best guess” data source and predicts as accurately as possible. Previously, Blockprint used to only analyze our graffiti, which is a very standard default graffiti indicating Lodestar usage and is used throughout the ChainSafe fleet of validator and thus showed 100% because the graffiti always indicated Lodestar.

  • Robert Tiong

    •

    Feb 24, 2025

    Hi @Philip Ngo ! Thank you for raising. We’ll look into this. :)