A simple view into validator operations
When you stake ETH, you always (sometimes unknowingly) pick an operator. You cannot see how they hold their keys, which clients they run, or how correlated their setup is with everyone else securing the network. Validator Beat makes that visible.
The gap
Rollups have L2Beat. Wallets have Walletbeat. The validator operators securing tens of millions of staked ETH have had no way to differentiate themselves outside of performance and reputation. Stakers, from ETH holders to institutional allocators, choose an operator or protocol and forget about it. Compliance attestations like SOC 2 cover process and custody, but they say nothing about the choices that actually determine whether a validator stays safe and online: how signing keys are split, whether the operator runs a single client implementation, how concentrated their infrastructure is, and how much of that overlaps with the rest of the network.
That invisible risk is unpriced. Validator Beat is the public entry point that compares these risks and gives operators a reason to compete on it.
Why it matters
There are two ways a validator fails, and decentralization is the insurance against both.
Most safety and liveness issues trace back to a single point of failure: one machine, one team member, one client, one provider, one region. Validator Beat measures how many of those single points of failure an operator has removed.
The assessment
Most operators start exposed with two stages to climb and a six-slice risk profile.
This can be read at a glance. For the exact thresholds and rubric, see the methodology. To see where your own validator lands, take the assessment .
Validator Beat is self-reported and consent-based.Who it's for
If you delegate your ETH
If you're an operatooor
The standard behind the score
Validator Beat is the public-facing who is running validators. valOS, the Validator Operating Standard, is the technical how: a deep catalog of the controls and mitigations behind professional validator operations.
A staker can quickly read an operator's stages and profile here. An operator doing the hard work and implementing the mitigations should dig into valOS. Follow valOS, and you'll end up at stage 2.
Validator Beat
The who — the public dashboardvalOS
The how — the operating standardCredibility
Validator Beat is co-authored by Obol and Lido. It is deliberately neutral and no single team owns the rubric. The methodology is public and is meant to be adopted, challenged, and improved by the whole ecosystem.
The goal is a race to the top, where transparency about validator risk becomes the default expectation.