Roundbeat documentation

Roundbeat is validator intelligence for Lido node operators. These pages show how to set up monitors and alerts, what every page of the app shows, what the numbers mean, and how to use the public API.

Sections

• Getting startedWhat Roundbeat is, what you can see without an account, and how to set up a monitor, a destination and an alert rule.
• AlertsEvery Roundbeat alert type with its trigger, severity and frequency; offline outages and recoveries; rules and cooldowns, destinations, delivery history and the webhook payload.
• ConceptsLido staking modules and the Curated v1 to v2 migration, operators and keys, validator statuses, effective balance and 0x02 keys, epochs, exit deadlines and MEV.
• Reading the pagesA guide to every page of app.roundbeat.com: Lido overview, module tables, operator tabs and their time windows, Block Analysis, Curated v2, sync committees, contracts, shared links and link previews.
• Public APIThe public, read-only Roundbeat API: endpoints, parameters, response shapes and curl examples.
• FAQAnswers to common questions about Roundbeat data, alerts, monitors and limits.

Common questions

• How do I get my first alert?
• When does an offline key alert, and when does it recover?
• Which alert types are critical?
• What does PagerDuty, Telegram, Slack or a webhook receive?
• How long do I have after an exit request?
• Where is my operator in the Curated v1 to v2 migration?
• How do I share last week’s missed proposals, or one missed slot?

Right now

What Roundbeat is watching, from the same public API the app uses: