Rocket Pool minipool monitoring — built by a node operator, for node operators

What you get: Alerts when your minipool validators miss attestations past your threshold, change their fee recipient (critical for RP's Smoothing Pool), drop in balance, or change status (slashing, exit, withdrawal). Delivered via email, Telegram, and native iOS/Android push.

Why it's different for Rocket Pool: The fee-recipient alert is genuinely load-bearing for RP node operators — a wrong fee recipient gets you penalized and kicked from the Smoothing Pool. Eyrium fires that alert within ~60 seconds.

Setup: Add your minipool validators' pubkeys, done. Pro covers up to 200 validators — more than enough for any realistic Rocket Pool node.

Cost: Free tier (1 validator, email alerts). Pro: $7/mo or $70/yr, up to 200 validators, all alert channels.

A note on who built this

Eyrium's builder runs a live Rocket Pool node with real ETH bonded and minipools attesting on mainnet. Not as a demo setup — as an actual node operator. The monitoring gaps that motivated building Eyrium were gaps felt personally, not inferred from forum posts.

That context is why this page exists. Generic validator monitoring tools don't talk about fee-recipient alerts because most solo validators don't have a protocol mechanism that penalizes a wrong fee recipient. Rocket Pool operators do.

What Rocket Pool monitoring actually requires

If you're running a Rocket Pool node with minipools, you have a few things a standard home validator doesn't:

Fee recipient is protocol-enforced. If you're opted into the Smoothing Pool, your validator's fee recipient must be set to the Smoothing Pool contract address. If it's wrong — due to a Smartnode misconfiguration, a client migration that reset it, or any other ops failure — the RP protocol penalizes you and the Smoothing Pool can remove you. You lose priority fees until you fix it. A generic validator monitor that doesn't fire on fee-recipient changes will not catch this.

RPL collateral ratio affects your node, but not your beacon-chain validators. Your validators on the beacon chain are indexed by pubkey and behave like any other validator — they attest, propose blocks, and can be slashed. The RPL mechanics (collateral ratio, RPL rewards, rETH minting limit) live in the RP smart contracts, not on the beacon chain. A validator monitoring tool watches the beacon chain; it can't see your RPL balance.

Missed attestations erode your commission economics. As a node operator, your revenue is a mix of consensus rewards, execution rewards (via Smoothing Pool or direct fee recipient), and the operator commission on the protocol ETH. Missed attestations reduce your consensus rewards and your attestation-rate performance record. Catching a degraded node before it misses a hundred attestations matters more for RP operators than for solo stakers running a single validator.

Slashing wipes your bond. You've put up 8 ETH (LEB8) or 16 ETH on each minipool. A slashing starts eating that immediately. The status-change alert catches the transition to active_slashed within ~60 seconds — before the slash has time to compound.

How Eyrium fits into a Rocket Pool stack

Eyrium monitors your validators at the beacon-chain layer. You point it at the validator pubkeys behind your minipools — not at your node address, not at the Smartnode. It watches:

This covers the beacon-chain failure modes that affect your minipool performance and your bond. It does not reach into the RP contracts — RPL price, collateral ratio, Smoothing Pool balance, and rETH capacity are outside scope. See the FAQ for detail on where Eyrium's scope ends.

Alert-by-alert breakdown for RP operators

Fee-recipient change alert — the one that matters most for Rocket Pool

If your validator's fee recipient changes — from the Smoothing Pool address to anything else, or from your node fee distributor to anything else — Eyrium fires an alert within ~60 seconds. The same alert also fires if a validator's withdrawal credentials change, giving you extra supply-chain coverage that catches someone redirecting your withdrawal or exit destination.

Why this matters: most generic monitoring tools don't watch fee recipients. For solo stakers, a fee-recipient change is a supply-chain / MEV security concern. For Rocket Pool operators in the Smoothing Pool, it's an ops compliance concern on top of that — the wrong fee recipient means you're breaking your Smoothing Pool membership terms and leaking priority fees to the wrong address. You want to know immediately.

Missed attestation alert — configurable streak threshold

Eyrium fires when your validator misses attestations for a consecutive streak you define (1–10 misses before alerting). Head-only-miss suppression filters out relay-delay false positives — the one-block misses that are usually a relay latency hiccup, not a node problem.

For RP operators: a degraded node that's missing attestations is leaking consensus rewards from both your bond and the protocol ETH. You're also degrading your node's performance record. The streak threshold lets you tune signal-to-noise — set it to 1 if you want to know every miss, or 3–5 if you want to suppress transient network noise and only hear about sustained problems.

Status change alert — catches slashing, exit, and withdrawal

A single alert type covers all validator status transitions: activeactive_slashed, voluntary exit initiation, and withdrawal completion. Slashing detection fires within ~60 seconds. If you have multiple minipools and one validator transitions unexpectedly, you hear about it.

For RP operators: a slashing event on any minipool starts eating your bond immediately. A ~60-second notification gives you enough time to take action — specifically, to ensure no duplicate key setup is still running somewhere, which is the leading cause of slashing.

Balance drop alert

Fires when your validator's effective balance drops below a threshold you set. Useful for catching early penalty accumulation or confirming the state post-slashing.

Comparison: Eyrium vs beaconcha.in for Rocket Pool operators

Eyrium Probeaconcha.in
Fee-recipient change alert
Missed attestation (streak threshold)✓ configurableBasic only
Head-only-miss suppression
Slashing alert✓ (~60s)
Native Telegram bot✗ (webhook only)
Native iOS/Android push
Pricing$7/mo flatFree (limited) / subscription tiers
Up to 200 validatorsPlan-dependent

Setup for Rocket Pool node operators

1. Sign up for Eyrium (free tier, no card required).

2. Find your minipool validators' pubkeys. From the Smartnode CLI, run rocketpool minipool status — it lists each minipool with its validator pubkey.

3. Add each validator pubkey to Eyrium. Copy the validator pubkey from rocketpool minipool status and paste it into Eyrium's add-validator screen. Eyrium accepts the validator pubkey — a 0x-prefixed 96-hex string (98 characters including the 0x).

4. Enable fee-recipient alerts. Set your missed-attestation streak threshold. All other alerts are on by default.

5. Connect Telegram and install the Android app for push alerts. iOS app is currently in Apple review — check eyrium.app for availability.

That's it. Eyrium polls the beacon chain every ~60 seconds. You don't need to give it your node address, your Smartnode credentials, or anything RP-specific.

FAQ

Does Eyrium integrate with the Rocket Pool Smartnode?
No. Eyrium monitors validators at the beacon-chain layer — it watches validator pubkeys directly, the same data any beacon chain explorer sees. You give it your minipool validators' pubkeys, and it watches their beacon-chain behavior: attestations, balance, status, and fee recipient. It does not connect to your Smartnode, your node wallet, or the RP contracts.
Why does the fee-recipient alert matter for Rocket Pool specifically?
Because Rocket Pool's Smoothing Pool enforces a correct fee recipient as a membership condition. If you're opted in and your validator's fee recipient changes — due to a misconfiguration, client migration, or anything else — the protocol considers you out of compliance. You'll lose priority fees for that validator, and the Smoothing Pool can remove you. The fee-recipient alert fires within ~60 seconds of any change, letting you catch and fix the misconfiguration before it compounds.
Can Eyrium monitor all of my minipools?
Yes, up to 200 validators on Pro ($7/mo). Rocket Pool nodes typically run between 1 and a few dozen minipools — the 200-validator cap comfortably covers the realistic top of that range. Free tier covers 1 validator with email alerts, which is enough to evaluate the product before upgrading.
Does Eyrium track my RPL collateral ratio or Smoothing Pool balance?
No. Eyrium monitors validators on the beacon chain. RPL collateral ratio, RPL staking rewards, rETH capacity, and Smoothing Pool balance are Rocket Pool protocol concepts that live in the RP smart contracts — not on the beacon chain. Eyrium can't see them and doesn't claim to. For RPL-level monitoring, use the Smartnode's own reporting or a RP-native dashboard.
Is there a missed-proposal alert?
Not yet. Eyrium fires on missed attestations, balance drops, status changes, and fee-recipient changes. A standalone missed-proposal alert isn't available today.
Is the iOS app available?
The Android app is live on Google Play (search "Eyrium" or package app.eyrium). The iOS app is submitted and in Apple review — not downloadable yet. Check eyrium.app for current availability. Email and Telegram alerts work on all platforms now.
How do I find my minipool validator pubkeys?
From the Smartnode CLI: rocketpool minipool status shows each minipool with its validator pubkey. Copy that pubkey and paste it into Eyrium — Eyrium accepts the validator pubkey (a 0x-prefixed 96-hex string, 98 characters including the 0x).

Set up Rocket Pool monitoring in under two minutes.

Add your minipool validator pubkeys, enable fee-recipient alerts, set your attestation miss threshold. Free tier gets you started — Pro is $7/mo when you want Telegram, native push, and coverage across all your minipools.

Get started →