Lido node operator monitoring: missed attestations, slashing alerts, and fee-recipient changes
Who this is for: Lido CSM operators and smaller independent node operators running up to ~200 validators. Eyrium monitors your beacon-chain validators — point it at the pubkeys you run for Lido and it handles the rest.
Who this is NOT for: Large curated Lido operators running hundreds or thousands of validators. Eyrium Pro caps at 200 today. If you're in that segment, see the note on the 200-validator limit below.
What you get: Missed attestation alerts (configurable streak threshold, head-only-miss suppression), missed proposal and sync-committee alerts, slashing / exit / withdrawal status changes, balance drops, and fee-recipient changes. Upcoming sync assignments and successful proposals are recorded in the feed. Email free; Telegram and iOS/Android push on Pro ($7/mo or $70/yr).
What it means to run validators for Lido
When you run validators as a Lido node operator, you're not just a solo staker minding your own business. You're part of a protocol with an operator accountability layer.
For curated operators: Lido's Node Operator Registry tracks your performance. Sustained underperformance can result in reduced stake allocation — or removal from the set entirely. Reliability is how you retain your position.
For CSM (Community Staking Module) operators: You posted an ETH bond to join. That bond is at risk. A slashing event or prolonged degraded performance can eat into it. The permissionless nature of CSM means you're responsible for your own monitoring stack — the protocol doesn't babysit you, and a missed alert can mean real money.
In both cases, missed attestations across your validator set hurt your operator metrics. Fee-recipient compliance is enforced by the protocol; an unexpected fee-recipient change on one of your validators is a red flag — either configuration drift or something worse.
What Eyrium monitors (and what it doesn't)
Eyrium monitors beacon-chain validator state. You add validator pubkeys, it watches them. That's the model.
It does not integrate with:
- The Lido Node Operator Registry
- The CSM contracts or bond accounting
- Lido's operator performance dashboard or score
It does fire on:
| Event | What it means for Lido operators |
|---|---|
| Missed attestation streak | Configurable threshold (1–10 consecutive misses). Head-only-miss suppression filters relay-delay false positives. Keeps signal-to-noise ratio workable across a multi-validator set. |
| Status change | Catches slashing, voluntary exit, and withdrawal — any validator state transition — on the next finalized-checkpoint processing cycle. If one of your validators is slashed, that's direct impact to your ETH bond (CSM) or your operator standing. |
| Balance drop | A validator balance that drops unexpectedly outside of normal attestation-miss losses may indicate a deeper problem. |
| Fee-recipient change | Lido requires the protocol fee recipient on your validators. An unexpected change here — or a change to a validator's withdrawal credentials — is a compliance issue or a supply-chain red flag. The fee recipient is verified on every block you propose; credential changes are caught when the finalized checkpoint advances. |
Missed block proposals fire their own alert. There is no sync-committee alert today. Slashing and unexpected exits are caught via the status-change alert.
The CSM sweet spot
CSM operators are essentially solo-staker-scale operators running under Lido's banner. You posted an ETH bond to enter, you're running a relatively small validator count, and you're accountable to the protocol. This is exactly who Eyrium was built for:
- Small enough to fit: Pro covers up to 200 validators. Most CSM operators launching today are well within that range.
- Bond at risk: A slashing event means immediate financial loss. A finality-aware alert is still far better than discovering it hours later in a dashboard or chat thread.
- Performance accountability: Sustained attestation misses affect your operator metrics. The streak threshold means you won't get paged for a single miss during a relay hiccup — only for the patterns that actually matter.
- Fee-recipient compliance: Lido enforces the protocol fee recipient. Monitor it.
A note on the 200-validator cap
Eyrium Pro currently caps at 200 validators. If you're running a large curated Lido operator set — several hundred to several thousand validators — Eyrium isn't the right fit today.
If you're in that segment and want to be notified when Eyrium ships higher limits, the best option is to sign up with a small subset of validators and contact support. But don't pay for a Pro plan expecting it to cover a 1,000-validator set. That's not what exists today.
For CSM operators and smaller independent operators: 200 is a real ceiling that most of you won't hit for a while.
Setup
Eyrium doesn't know about Lido — it knows about validators. Setup is:
- Get your validator pubkey (a 0x-prefixed 96-hex string, available from any beacon explorer or your client's logs).
- Add it to Eyrium. Free tier handles 1 validator on email; Pro handles up to 200 across all channels.
- Alerts are on by default. Status-change, balance drop, and fee-recipient alerts fire immediately when triggered. Missed attestation fires after your configured streak threshold.
That's it. No Lido credentials, no operator API keys, no special configuration.
Alert channels
| Channel | Free | Pro ($7/mo) |
|---|---|---|
| ✓ | ✓ | |
| Telegram (native bot) | ✗ | ✓ |
| iOS push (App Store) | ✗ | ✓ |
| Android push (Google Play) | ✗ | ✓ |
Both mobile apps are live — iOS on the App Store and Android on Google Play (app.eyrium).
FAQ
- I run a curated Lido operator with hundreds or thousands of validators. Does Eyrium work for me?
- Not at current scale. Eyrium Pro caps at 200 validators today. If you run a large curated operator set, you've outgrown the current limit. Eyrium fits CSM operators and smaller independent operators whose sets land within 200 validators. If you want to be notified when higher limits ship, contact support.
- Does Eyrium integrate with CSM or the Lido Node Operator Registry?
- No. Eyrium monitors beacon-chain validators — you point it at your validator pubkeys. There is no Lido-protocol integration, no CSM contract awareness, and no operator performance score tracking. It's beacon-chain monitoring: missed attestations, status changes, balance drops, fee-recipient changes.
- Why does the fee-recipient alert matter for Lido operators?
- Lido requires validators to use the protocol fee recipient. An unexpected fee-recipient change on one of your validators can mean configuration drift, a client misconfiguration, or in the worst case, a supply-chain compromise. A fee recipient is only observable in the blocks a validator proposes, so Eyrium verifies it on every block your validators propose and fires the alert as soon as one lands with a changed address. For Lido operators in particular, fee-recipient compliance is non-negotiable — catching it at the first affected proposal matters.
- Will Eyrium catch a slashing against my CSM bond?
- Yes. The status-change alert fires on the next finalized-checkpoint processing cycle when a validator transitions into a slashed, exited, or withdrawn state. For CSM operators, that's direct impact to your ETH bond. The alert includes validator index, pubkey, the prior state, and the new state.
- Can I monitor just a subset of my validators to evaluate it first?
- Yes. The free tier supports 1 validator with email alerts. You can add one validator — say, the one you'd be most worried about — and run it that way to evaluate the product before upgrading.
- Is there a missed-proposal or sync-committee alert?
- Yes. Eyrium alerts when a CSM validator's assigned proposal slot goes empty or a sync-committee signature is missed. Successful proposals and current or upcoming sync-committee assignments are recorded in the event feed. Other alerts cover missed attestations, status changes, balance drops, and credentials changes.
- Is the iOS app available?
- Yes. Both apps are live — the iOS app on the App Store and the Android app on Google Play.
Free tier gets you started in under a minute.
Add one validator, configure email alerts, done. Upgrade to Pro for $7/mo when you want Telegram, Android push, and coverage across your full operator set (up to 200 validators).
Get started →
