Getting started

Roundbeat watches every validator of every Lido node operator from the outside: it reads what the beacon chain and Lido’s contracts recorded, not what your node reports. Every page is public. Sign in to get alerts.

What Roundbeat is

Validator intelligence for Lido node operators. Roundbeat indexes every epoch of Ethereum’s beacon chain and tracks every operator in Lido’s four staking modules: Curated v1, SimpleDVT, CSM and Curated v2, including the move from Curated v1 to Curated v2.

Right now that is 509 operators with validators (of 793 registered), 233,398 active validators and 9.25M ETH of effective balance (snapshot, 13 Oct 2026, 10:45 UTC).

You install nothing. Roundbeat runs its own beacon node and reads Lido’s registry, so it sees a missed duty even when every local dashboard is green. Use it next to your own monitoring, not instead of it.

Words used in these docs

Operator

A node operator in one Lido staking module. Its ID is unique only inside that module, so Roundbeat always names both (see Lido staking modules).

Validator, key

The same thing, seen from two sides. A validator signs with its key; the app counts keys when it talks about many at once (“12 keys back online”). Before Lido deposits to a key it is not a validator yet (see Operators and keys).

Offline

Short for likely offline: a key that missed its attestation in 3 epochs in a row. Roundbeat sees the missed votes on chain, not your machine (see When a key counts as offline).

CMv2

The app’s short name for Curated v2, used in validator status labels such as Consolidating → CMv2.

Event, alert

An event is something Roundbeat recorded for a validator or an operator. It becomes an alert when a rule sends it to one of your destinations (see How alerts work).

Public and signed-in

Where the data comes from

• The beacon chain, read by Roundbeat’s own node every epoch (32 slots of 12 seconds, so about 6.4 minutes).
• Lido’s registry of operators and keys, through the Lido Keys API.
• Lido’s contracts for exit requests, bond and penalty events, and the Curated v2 migration.
• MEV-Boost relays for which relay delivered each block and the bids for it.

Roundbeat processes an epoch once it is complete, so its data normally trails the chain head by up to 2 epochs. If its beacon node falls more than 64 slots behind, the app shows a Chain data delayed banner; the FAQ explains what that means for alerts.

Sign in and your organization

Press Sign In at the top of app.roundbeat.com. The first time, Roundbeat asks you to Create your organization: give it a name (for example your company’s) and press Create organization. Monitors, rules and destinations belong to the organization and are shared with its members. Invite teammates under Settings → Organization, with one of three roles:

Owner

Everything, including roles, billing and the organization name.

Admin

Monitors, alert rules and destinations; invites people and removes members.

Viewer

Read-only: sees the monitors, rules and history, changes nothing.

Create a monitor

A monitor tells Roundbeat which validators are yours. There are two kinds:

Lido operator

Every validator of one operator in one module, including keys added later. You pick it from a searchable list of every operator.

Withdrawal address

Every validator that withdraws to one Ethereum address, for validators outside Lido. Up to 10,000 validators per address.

From My Validators

1. Open My Validators app.roundbeat.com/my-validators and press Add monitor.
2. Choose what to monitor: Withdrawal address or Lido operator.
3. Fill it in. Paste the address (0x followed by 40 hex characters), or search the operator by name or ID and filter by module. The Label is optional; an operator monitor takes the operator’s name.
4. Press Add monitor.

From an operator page

On any operator page, press Monitor in the header, then Start monitoring. The button then reads Monitoring, and Stop monitoring in the same popover removes the monitor. For Curated v1 and Curated v2 operators the popover also holds the migration alert toggles.

An organization can have up to 10 monitors, the Starter plan’s limit. Self-serve billing is not enabled yet: nothing is charged, and the Billing tab lists the coming plans for reference.

Add a destination

A destination is where alerts go.

1. Open My Alerts → Destinations app.roundbeat.com/my-alerts?tab=destinations and press Add destination.
2. Pick the type: Telegram, Slack, PagerDuty or Webhook. Email is listed but not delivered yet.
3. Name it and paste the target: a Telegram chat ID, a Slack webhook URL, a PagerDuty integration key or an HTTPS URL. Destinations explains each one.
4. Press Add destination, then Test on its row.

Add an alert rule

A rule connects monitors to destinations. Without a rule, nothing is sent.

1. Open My Alerts → Rules app.roundbeat.com/my-alerts?tab=rules and press Add rule.
2. Name it and choose the Scope: All monitors or one monitor.
3. Choose the events: All events, or Specific types. A good first rule for on-call is All events at Critical: only critical events. That covers missed proposals, offline keys, slashings, missed exit deadlines, out-of-order exits and bond penalties.
4. Pick the destinations and keep the default cooldown of 5 minutes.
5. Press Create rule.

The alert types tables list every type with its severity, and Rules explains each field.

Check that it works

• A destination whose test arrived shows Verified.
• A rule that can send shows Active. Any other status says why it cannot (see Rule status).
• Every alert Roundbeat tries to send appears under My Alerts → History, one row per destination, with its status (see Retries and history).
• Your validators’ events appear on My Validators whether or not a rule sends them.