The code is provided as-is with no warranties.
Youtube video of Ethereum Validator Watcher talk during EthCC[6].
Grafana dashboard configuration file.
Ethereum Validator Watcher monitors the Ethereum beacon chain in real-time and notifies you when any of your validators:
- are going to propose a block in the next two epochs
- missed a block proposal at head
- missed a block proposal at finalized
- did not optimally attest
- missed an attestation
- missed two attestations in a row
- proposed a block with the wrong fee recipient
- has exited
- got slashed
- proposed a block with an unknown relay
- did not had ideal source, target or head reward
It also exports some general metrics such as:
- your USD assets under management
- the total staking market cap
- the epoch and slot
- the number or total slashed validators
- the ETH/USD conversion rate
- the number of your queued validators
- the number of your active validators
- the number of your exited validators
- the number of the network queued validators
- the number of the network active validators
- the entry queue duration estimation
Optionally, you can specify the following parameters:
- the path to a file containing the list of public keys to watch, or / and
- a URL to a Web3Signer instance managing your keys to watch.
Pubkeys are dynamically loaded, at each epoch start.
- If you use a pubkeys file, you can change it without having to restart the watcher.
- If you use Web3Signer, a request to Web3Signer is done at every epoch to get the latest set of keys to watch.
Finally, this program exports the following sets of data from:
- Prometheus (you can use this Grafana dashboard to monitor your validators)
- Slack
- logs
Prometheus server is automatically exposed on port 8000.
╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ * --beacon-url TEXT URL of beacon node [required] │
│ --execution-url TEXT URL of execution node │
│ --pubkeys-file-path FILE File containing the list of public keys to watch │
│ --web3signer-url TEXT URL to web3signer managing keys to watch │
│ --fee-recipient TEXT Fee recipient address - --execution-url must be set │
│ --slack-channel TEXT Slack channel to send alerts - SLACK_TOKEN env var must be set │
│ --beacon-type [lighthouse|nimbus|old-prysm|old-teku|other] Use this option if connected to a Teku < 23.6.0, Prysm < 4.0.8, Lighthouse or │
│ Nimbus beacon node. See https://github.com/ConsenSys/teku/issues/7204 for Teku < │
│ 23.6.0, https://github.com/prysmaticlabs/prysm/issues/11581 for Prysm < 4.0.8, │
│ https://github.com/sigp/lighthouse/issues/4243 for Lighthouse, │
│ https://github.com/status-im/nimbus-eth2/issues/5019 and │
│ https://github.com/status-im/nimbus-eth2/issues/5138 for Nimbus. │
│ [default: BeaconType.OTHER] │
│ --relay-url TEXT URL of allow listed relay │
│ --liveness-file PATH Liveness file │
│ --help Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
| Beacon type | Compatibility |
|---|---|
| Lighthouse | Full with --beacon-type=lighthouse. See sigp/lighthouse#4243 for more details. |
Prysm >= 4.0.8 |
Full. |
Prysm < 4.0.8 |
Partial with --beacon-type=old-prysm - Rewards computation disabled. See prysmaticlabs/prysm#11581 for more details. |
Teku >= 23.6.0 |
Full. You need to activate the beacon-liveness-tracking-enabled flag on your beacon node. |
Teku < 23.6.0 |
Full with --beacon-type=old-teku. See Consensys/teku#7212 for more details. You need to activate the beacon-liveness-tracking-enabled flag on your beacon node. |
| Nimbus | Partial with --beacon-type=nimbus - Missed attestations detection and rewards computation disabled. See status-im/nimbus-eth2#5019 and status-im/nimbus-eth2#5138 for more details. |
| Lodestar | Not (yet) tested. |
The beacon type is relative to the beacon node connected to the watcher, not to the beacon node connected to the validator client containing a validator key you want to watch. (The watcher is agnostic of the infrastructure mananing validators keys you want to watch.)
Minimal example, connected to Prysm:
eth-validator-watcher --beacon-url http://localhost:3500
Example with Lighthouse and with keys to watch retrieved from Web3Signer:
eth-validator-watcher --beacon-url http://localhost:5052 --beacon-type lighthouse --web3signer-url http://localhost:9000
Example with Lighthouse, with keys to watch retrieved from a file, and with a specified fee recipient:
eth-validator-watcher --beacon-url http://localhost:5052 --beacon-type lighthouse --execution-url http://localhost:8545 --pubkeys-file-path keys.txt --fee-recipient 0x4675c7e5baafbffbca748158becba61ef3b0a263
With the following keys.txt file:
0x815210c169e598f1800dbda3b2ee146a0178f772c5105722e0673d824535bcab03aa6bc422955264bb201b5ddbb6981d
0x950f77f6cba50c9ad97240a7171cf4506bf86cbed11bb8e2f45a38036e4375c4f5344647e7150c640f308fd9d6de4d59
0x8adf063f810e2321a1aea258fd3a6ee5560911cee631980e1ef32bd88bf8c3dd5d28724e22a8987bfe411dd731f6dd38
--pubkeys-file-path and --fee-recipient flag allow both 0x prefixed and non 0x prefixed ETH1 address / pubkeys.
Example with Prysm, with keys to watch retrieved from Web3Signer and with Slack alerting:
export SLACK_TOKEN=xoxb-xxxxxxxxxxxxx-xxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxx
eth-validator-watcher --beacon-url http://localhost:3500 --web3signer-url http://localhost:9000 --slack-channel eth-alerting
Example with Prysm, with keys to watch retrieved from Web3Signer and with Flasbots and UltraSound as allowed relays:
eth-validator-watcher --beacon-url http://localhost:3500 --web3signer-url http://localhost:9000 --relay-url https://0xac6e77dfe25ecd6110b8e780608cce0dab71fdd5ebea22a16c0205200f2f8e2e3ad3b71d3499c54ad14d6c21b41a37ae@boost-relay.flashbots.net --relay-url https://0xa1559ace749633b997cb3fdacffb890aeebdb0f5a3b6aaa7eeeaf1a38af0a8fe88b9e4b1f61f236d2e64d95733327a62@relay.ultrasound.money
| name | description |
|---|---|
eth_usd |
ETH/USD conversion rate |
entry_queue_duration_sec |
Entry queue duration in seconds |
our_pending_queued_validators_count |
Our pending queued validators count |
total_pending_queued_validators_count |
Total pending queued validators count |
our_active_validators_count |
Our active validators count |
total_active_validators_count |
Total active validators count |
our_exited_validators_count |
Our exited validators count |
wrong_fee_recipient_proposed_block_count |
Wrong fee recipient proposed block count |
missed_attestations_count |
Missed attestations count |
double_missed_attestations_count |
Double missed attestations count |
missed_block_proposals_head_count |
Missed block proposals on head count |
missed_block_proposals_finalized_count |
Missed block proposals on finalized count |
future_block_proposals_count |
Future block proposals count |
our_slashed_validators_count |
Our slashed validators count |
total_slashed_validators_count |
Total slashed validators count |
suboptimal_attestations_rate |
Suboptimal attestations rate |
keys_count |
Keys count |
bad_relay_count |
Bad relay count |
net_suboptimal_sources_rate |
Network suboptimal sources rate |
net_suboptimal_targets_rate |
Network suboptimal targets rate |
net_suboptimal_heads_rate |
Network suboptimal heads rate |
net_ideal_sources_count |
Network ideal sources count |
net_ideal_targets_count |
Network ideal targets count |
net_ideal_heads_count |
Network ideal heads count |
net_actual_pos_sources_count |
Network actual positive sources count |
net_actual_neg_sources_count |
Network actual negative sources count |
net_actual_pos_targets_count |
Network actual positive targets count |
net_actual_neg_targets_count |
Network actual negative targets count |
net_actual_heads_count |
Network actual heads count |
our_suboptimal_sources_rate |
Our suboptimal sources rate |
our_suboptimal_targets_rate |
Our suboptimal targets rate |
our_suboptimal_heads_rate |
Our suboptimal heads rate |
our_ideal_sources_count |
Our ideal sources count |
our_ideal_targets_count |
Our ideal targets count |
our_ideal_heads_count |
Our ideal heads count |
our_actual_pos_sources_count |
Our actual positive sources count |
our_actual_neg_sources_count |
Our actual negative sources count |
our_actual_pos_targets_count |
Our actual positive targets count |
our_actual_neg_targets_count |
Our actual negative targets count |
our_actual_heads_count |
Our actual heads count |
From source:
git clone git@github.com:kilnfi/eth-validator-watcher.git
cd eth-validator-watcher
pip install .
Docker images (built for AMD64 and ARM64) are available here.
| Description | Log |
|---|---|
| A new epoch starts. | 🎂 Epoch 209904 starts |
| You are going to propose a block in the next two epochs. | 💍 Our validator 0xa6cdd026 is going to propose a block at slot 6716781 (in 13 slots) |
| Someone proposed a block. | ✅ validator 0xb9d2439f proposed block at epoch 209899 - slot 6716776 ✅ |
| You proposed a block. | ✨ Our validator 0xa6cdd026 proposed block at epoch 209899 - slot 6716781 ✨ |
| You proposed a block with the wrong fee recipient. | 🚩 Our validator 0x00000000 proposed block at epoch 209952 - slot 6718495 with the wrong fee recipient |
| You did not had optimal attestation inclusion. | ❗ Our validator 0x98a5bad4, 0x8116a5f8, 0xa2fff7bd, 0x87cd0fd3, 0x978ebbdb and 1 more (1.2 %) had not optimal attestation inclusion at slot 6716778 |
| Someone missed a block proposal. | 💩 validator 0xa3dbc635 missed block at epoch 209894 - slot 6716637 💩 |
| You missed a block proposal (head). | 🔺 Our validator 0xb09d7c4e missed block at head at epoch 107948 - slot 3454352 🔺 |
| You missed a block proposal (finalized). | ❌ Our validator 0xb09d7c4e missed block at finalized at epoch 107948 - slot 3454352 ❌ |
| You missed an attestation. | 🙁 Our validator 0xa672f362, 0xb5f46214, 0xac81b7f4 and 0 more missed attestation at epoch 209894 |
| You missed 2 attestations in a row. | 😱 Our validator 0x8c9bfca1, 0xa68f7c5d and 0 more missed 2 attestations in a row from epoch 209367 |
| You exited. | 🚶 Our validator 0xaeb82c90 is exited |
| Someone got slashed. | 🔪 validator 0xb3a608a7 is slashed |
| You got slashed (you don't want to see this one). | 🔕 Our validator 0x00000000 is slashed |
| You proposed a block with a non-allowed relay. | 🟧 Block proposed with unknown builder (may be a locally built block) |
| You did not had ideal source rewards. | 🚰 Our validator 0x8012aba2, 0x8012cdb1, 0x803f3b39, 0x8054cda1, 0x8055bb56 and 0 more had not ideal rewards on source at epoch 215201 |
| You did not had ideal target rewards. | 🎯 Our validator 0x8000118f, 0x80a238ea, 0x80e5809d, 0x80ec3c2d, 0x80f4487d and 0 more had not ideal rewards on target at epoch 215201 |
| You did not had ideal head rewards. | 🗣️ Our validator 0x8005f5e8, 0x801910e5, 0x80193dd5, 0x801a26e9, 0x80285258 and 0 more had not ideal rewards on head at epoch 215200 |
| The chain is not yet started. | ⏱️ The chain will start in 1 days, 1 hours, 3 minutes and 48 seconds. |
If you see this kind of message:
❓ Missed attestations detection is disabled for epoch 238030.
❓ You can ignore this message if the watcher just started less than one epoch ago. Otherwise, please check that you used the correct `--beacon-type`` option (currently set to `other`).
❓ Use `--help` for more details.
If you just started the watcher less than one epoch ago (and especially, if you started the watcher during the few last slots of the epoch), then you can safely ignore this message.
Otherwise, please check you uses the correct --beacon-type option.
If a Slack channel is specified, the slack messages are sent according to the following events:
- When you exited
- When you got slashed
- If fee recipient is specified, when you proposed a block with the wrong fee recipient
- When you missed 2 attestations in a row
- When you missed a block
We use Poetry to manage dependencies and packaging.
Installation:
git clone git@github.com:kilnfi/validator-watcher.git
cd validator-watcher
poetry install --with dev
poetry shell # To activate Python virtual environment
Running tests:
pytest
# With coverage
pytest --cov eth_validator_watcher --cov-report=term-missing
You can use --liveness-file <path-to-a-file> option to ensure the watcher is live.
If using this option, at the end of every slot, the watcher will simply write OK in the specified file.
Example of liveness probe usage on Kubernetes
livenessProbe:
periodSeconds: 60
initialDelaySeconds: 60
failureThreshold: 1
exec:
command:
- /usr/bin/python3.11
- /usr/local/bin/liveness_check.py
- <path-to-a-file>Why --execution-url is needed when --fee-recipient is used?
When using external block building (with MEV-boost for example), then the block builder may set its address as a fee recipient. In such a case, it adds an extra transaction in the block from its address to the proposer's fee recipient. To check this last transaction, the watcher needs to retrieve the execution block.