Watch a validator in three steps
You only need a validator ID. No account, no API key, and nothing exposed on your server.
-
Open the bot in Telegram
Search for @MonadBeaconBot in Telegram or follow the direct link: t.me/MonadBeaconBot. Tap Start to begin.
-
Watch a validator with /watchval
Send
/watchvalfollowed by the validator ID you care about (or a0xauthority address known to the VDP directory). For example:/watchval 267Nothing on your side needs to be reachable — the bot reads the validator's state from on-chain data.
-
Get alerts on any change
That's it. The bot DMs you when the validator enters or leaves the active set, when its consensus stake changes, or on a VDP funding or approval event. Silence means nothing changed.
/myvalidators to see everything you are watching, and
/unwatchval <id> to stop.
Ready to watch a validator? Tap the button to open the bot directly in Telegram.
Open @MonadBeaconBotHow the bot works
The bot polls Monad's on-chain state from its own reference RPC every 60 seconds and compares each watched validator against the previous snapshot. Because the data is on-chain, you never expose your own node:
- Active-set membership — reads the live consensus set. If a watched validator enters or leaves it, you get an alert.
- Consensus stake — tracks each validator's current consensus stake, the strongest near-term signal of a rotation.
- VDP activity — watches the Validator Delegation Program: qualifying Foundation funding transfers and new approvals tied to the addresses you follow.
Each change triggers exactly one alert. You are not spammed while a state persists.
Alert types
| Alert | Meaning | When you get it | |
|---|---|---|---|
| 🟢 | Entered active set | Validator joined the live consensus set | First check after it enters |
| 🔴 | Left active set | Validator dropped out of the consensus set | First check after it leaves |
| 🟡 | Consensus stake changed | A meaningful add or removal of live consensus stake | When the change is observed |
| 💸 | New Foundation funding | A qualifying 100,000–100,100 MON transfer from a tracked Foundation wallet | When the transfer is seen |
| ✅ | New VDP approval | An address entering the VDP approval flow | When the approval is observed |
All commands
| Command | Description |
|---|---|
/start |
Introduction and the menu (VDP Tracker · Node Monitoring · My Alerts · Help) |
/watchval <id|address> |
Watch a validator's on-chain liveness. No RPC needed. Example: /watchval 267
|
/unwatchval <id> |
Stop watching a validator |
/myvalidators |
List the validators you are watching |
/help |
Show the full command reference |
Monitoring a full node or RPC endpoint
The bot also keeps the classic node monitoring mode: it polls an RPC URL every 60
seconds and alerts on an unreachable endpoint, a stuck block height (>3 min), or lag (10+ blocks
behind the network). This needs an RPC endpoint that is reachable from the internet, so it is meant for
full nodes and RPC providers — not validators. Per Foundation guidance, validators
should keep their RPC ports closed and use /watchval above instead.
| Command | Description |
|---|---|
/add <rpc_url> |
Monitor a reachable RPC endpoint (full node / RPC provider). Example: /add https://your-rpc:8080 |
/remove <rpc_url> |
Stop monitoring an RPC endpoint |
/status |
Health, status label, and block height for your monitored endpoints |
/list |
List your monitored RPC endpoints |
FAQ
Do I need to expose my node's RPC?
No — that is the point. /watchval reads the validator's state on-chain, so it works with your
RPC port closed, which is how validators should run. Only the optional full-node monitoring mode
(/add) needs a reachable RPC.
I closed my RPC port per Foundation guidance — can I still use the bot?
Yes. Watch your validator with /watchval <id> and you will get active-set, stake, and
VDP alerts without opening anything.
Does the bot need access to my server?
No. No SSH, no credentials, no agent. For /watchval it reads public chain data; for the
optional /add mode it only makes outbound requests to an RPC URL you provide.
How do I find my validator ID?
It is the on-chain validator ID from the active set (also shown in our
VDP Tracker). You can also pass a
0x authority address the VDP directory knows.
Will I get spammed?
No. One alert per change. You are not messaged repeatedly while a state persists.
Start watching a validator now. Under 30 seconds — no signup, no config, no open ports.
Open @MonadBeaconBot