Roundbeat
Open the app

Validator intelligence for Lido operators

Monitoring and alerts for every Lido validator, read from the chain.

Roundbeat indexes every epoch of the beacon chain and tracks every operator in Lido’s four staking modules: Curated v1, SimpleDVT, CSM and Curated v2. Nothing to install, and every dashboard is public.

Open the appTalk to us

Roundbeat indexer:1 epoch behind head at 3 Oct 2026, 20:53 UTC

Lido operators
792
across all 4 staking modules
Active validators
255,790
of 491,051 keys ever deposited (incl. exited)
Stake tracked
9.30M ETH
effective balance, 9,301,499 ETH
Proposals made
99.8%
290,277 of 290,778 proposer duties indexed, 501 missed
Indexer freshness
1 epoch
behind head at 3 Oct 2026, 20:53 UTC

Snapshot from app.roundbeat.com, 3 Oct 2026, 20:54 UTC · Lido on Ethereum mainnet

Roundbeat Command Center: epoch and slot progress with chain participation 99.8%, fleet effectiveness 99.8% across attestation, proposals and sync committee, the 24-hour alert list, and fleet totals of 792 operators and 257,808 validators.
Command Center at app.roundbeat.com/command, a still captured 3 Oct 2026.

What the chain recorded, not what your node reports.

Your node’s logs tell you what your node thinks happened. Roundbeat reads what the beacon chain recorded for each of your validators, so a missed duty shows up even when every local dashboard is green. Use it next to your own monitoring, not instead of it.

Source: our own beacon node and the Lido Keys API, every epoch (about 6.4 minutes).

Your node’s logs

  • Your client’s view of itself: sync status, peers and the errors it chose to log.
  • An exporter or agent on every machine you run, kept up to date.
  • Can look healthy while attestations land late or not at all.

What the chain recorded

  • Attestation-miss streakslikely offline after 3 missed epochs in a row
  • Missed proposalsper block, with the slot
  • Slashingsfor any validator in your set
  • Exit requests and exitsrequested and completed
  • Sync committee dutywhen your validators are selected
  • MEV-Boost revenueper proposed block

Missed proposals, slashings and exit requests show up within an epoch or two of landing on chain. “Likely offline” fires after 3 missed attestations in a row, about 20 minutes.

Every operator in all four Lido modules.

Curated v1, SimpleDVT, CSM and Curated v2 each get their own operator table, sortable by effectiveness, proposals and MEV, next to the module average.

Stake by module, effective balance9.30M ETH

Snapshot, 3 Oct 2026, 20:54 UTC · Curated v2 operator count includes reserved slots without keys

One page per operator.

Everything the chain says about one operator, on one public page you can share with the DAO, your stakers or your team.

See an example: ChainSafe - PGO, Curated v2

  • Validators and stake

    Active and pending validators, effective stake next to actual balance, and status breakdown.

  • Proposals and MEV

    Proposal success rate with every missed slot, and MEV-Boost revenue per block.

  • Public and shareable

    No sign-in to view. The same page works on a phone.

The same operator page on a phone, 390 pixels wide.

app.roundbeat.com/operator/4/36, desktop and phone, captured 3 Oct 2026.

The Curated v1 to v2 migration, tracked.

Curated v1 validators are being consolidated into 0x02 compounding validators in Curated v2. Roundbeat follows every consolidation request on chain, for the whole module and for each operator.

Open Curated v2

  • Per-operator stage

    Awaiting pair, not started, submitted, in progress or done, with consolidated and remaining counts. Export to CSV.

  • Six migration alerts

    Stuck or rejected consolidation requests, overfill risk, pair changes, milestones and stake received.

  • Inbound migration on every page

    Each Curated v2 operator page shows what is arriving from its Curated v1 counterpart.

Curated v1 to v2 migration, all operators

snapshot, 3 Oct 2026, 20:54 UTC

13.7%

of legacy validators consolidated

Pace

~1,986/day

over the last 7 days

ETH moved

1.14M ETH

by completed consolidations

Drain estimate

~Jan 2027

221,787 legacy left, at the current pace

  • 35,578 consolidated
  • 9,735 in flight (6,595 queued, 3,140 source exited)
  • 6 requested, not queued
  • 215,186 not yet requested
Curated v2 operator table, sorted by stake: per operator the validators, stake, consolidation progress, effectiveness and migration stage, with stakefish, Stakely, RockLogic GmbH, MAVAN and Ebunker at the top.
Operator table at app.roundbeat.com/curated-v2, captured 3 Oct 2026.

Alerts that reach you.

Monitor an operator or a withdrawal address, choose the events you care about, and send them where your team already works.

Rules per event type, with label filters, cooldowns and grouping, including the CSM and Curated v2 contract events that cost bond. Monitors and alerts need a sign-in; the event feed is public.

Sign in to set up alertsBrowse the public event feed

Delivered to

  • Telegram
  • Slack
  • PagerDuty
  • Webhook
  • Email Planned

Validators

  • Slashed
  • Likely offline (missed attestations)
  • Missed proposal
  • Upcoming proposal
  • Exit request
  • Exited
  • Sync committee duty

CSM & Curated v2 on-chain

  • Penalty reported or settled
  • Bond burned or charged
  • Bond debt increased
  • Strikes penalty
  • Bad-performer ejection
  • Triggered exit and exit delay fee
  • Forced exit target

Curated v2 migration

  • Stuck consolidation request
  • Rejected consolidation request
  • Overfill risk
  • Migration pair change
  • Migration milestone
  • Consolidation stake received
Validator Alerts and Events page filtered to Critical: 15,074 events in 24 hours, 846 critical and 163 warning, and a list of Likely offline events for CSM operators, each with the validator index.
Public event feed at app.roundbeat.com/alerts, filtered to Critical, captured 3 Oct 2026.

Pricing

Free during early access.

Nothing is billed today and no card is asked for.

Open the appTalk to us
Every dashboard
Public. Open any module, operator or the event feed without an account.
Monitors and alerts
Sign in on the app to watch your operator and send alerts to your team. Up to 10 monitors per organisation during early access; need more? Talk to us.

Questions.

Do I install anything?

No. Roundbeat runs its own beacon node and reads Lido’s registry through the Lido Keys API. Find your operator, or add a withdrawal address, and press Monitor.

Where does the data come from?

From the beacon chain, read by our own node every epoch (about 6.4 minutes), and from Lido’s on-chain registry. The numbers on this page come from the same public API the app uses.

Which networks and modules?

Ethereum mainnet, covering every operator in Lido’s Curated v1, SimpleDVT, CSM and Curated v2 modules, including the Curated v1 to v2 migration.

Is it free?

Yes, during early access. Every dashboard is public, and monitors and alerts only need a sign-in (up to 10 monitors per organisation). Nothing is billed today.

Talk to us.

A question about your operator’s numbers, an alert you need, or monitoring for a larger fleet: write to us and a person replies.

[email protected]

Just want to look? Open the app, no account needed.