🦏
ETH Home Staking Collection
DVT Home Staking Curriculum
DVT Home Staking Curriculum
  • The DVT Home Staking Curriculum
  • Curriculum breakdown & timeline
  • Understanding ETH validators
    • Introduction to ETH Validators
    • Roles & Responsibilities of a node operator
    • Rewards and penalties
    • Importance of client diversity
    • Distributed Validator Technologies (DVTs)
    • Economics of using DVTs (WIP)
      • Diva Staking (WIP)
      • Obol (WIP)
      • SSV (WIP)
    • Bonded Validators
    • Economics of bonded validators (WIP)
  • Hardware & systems setup
    • Setup Overview
    • Hardware & system requirements
    • Procuring your hardware
    • Assemble your hardware
    • Practicing for free on Cloud VMs
      • Google Cloud
      • Alibaba Cloud
  • Linux OS, Networking, & Security
    • Install and prepare the OS
    • Networking & network security
    • Device level security setup
    • Verifying checksums
  • Installing & configuring your EL+CL clients
    • Set up and configure execution layer client
      • Nethermind
      • Besu
      • Geth
      • Erigon
      • Reth
    • Set up and configure consensus layer client
      • Teku BN
      • Nimbus BN
      • Lodestar BN
      • Lighthouse BN
      • Prysm BN
  • Keystore generation & MEV-Boost
    • Validator key generation
    • Set up and configure MEV-boost
  • Native Solo Staking Setup
    • Validator client setup
      • Teku VC
      • Nimbus VC
      • Lodestar VC
      • Lighthouse VC
      • Prysm VC
    • Depositing 32 ETH into your validator
    • Exiting your validator
  • Monitoring, Maintenance, and Updates
    • Set up monitoring suite
      • Installing & configuring Prometheus
      • Installing & configuring Node Exporter
      • Installing & configuring Grafana
      • Beaconcha.in App API
      • Client Uptime Check
    • Maintenance & Updates
      • Nethermind
      • Besu
      • Teku
      • Nimbus
      • Lodestar
      • Updating the monitoring suite
      • Preparing for Pectra
  • DVT Setup
    • Diva Staking
      • Diva Staking client setup
        • Default - All-in-one setup
        • Advanced - with standalone Lodestar VC
      • Registering your Diva node
      • Updating your Diva client
      • Monitoring your Diva Node
    • Obol
      • Techne Bronze Speedrun (Launchpad)
      • Obol + Bonded Validators (Techne Silver)
        • Obol + Lido CSM
    • SSV
      • SSV + Lido CSM (WIP)
      • SSV Operator
      • SSV Staker
  • Bonded Validators Setup
    • Lido CSM
      • Generating CSM keystores
      • Set Fee Recipient Address
        • Method 1: Configure on validator keys
        • Method 2: Configure on separate validator client
        • Verifying Fee Recipient Registered on MEV Relays
      • Upload/Remove/View validator keys
      • Rewards & bonds
      • Exiting CSM validators
        • "Lazy" exits (TESTNET ONLY)
        • Proper Exits
      • Role/Address management
      • Monitoring
      • Automations
        • CSM with ETHPillar
        • CSM with ETH Docker
        • CSM with Dappnode
    • Puffer
      • Non-Enclave: 2 ETH
    • Ether.fi
      • Receive distributed validator keyshares
    • Stader (WIP)
    • Rocketpool (WIP)
  • Liquid Staking Vaults
    • Stakewise V3
  • Mainnet
    • Mainnet Deployment
    • Heroglpyhs (WIP)
  • Best practices
    • Slashing prevention
    • Maximising uptime and performance
    • Optimising security
    • Managing your withdrawal wallet
  • Tips
    • Advanced networking
    • Downloading files from your node
  • Useful resources
    • General resources
    • Holesky Faucets
  • Automation/tools
    • ETHPillar
    • ETH Docker
    • Automated power on/off
      • Wake-on-LAN (WoL)
      • Network UPS Tools (NUT)
    • Validator Healthcheck Alerts
  • Solo Stakers Guild
    • Lido CSM+SSV+Obol (Testnet)
Powered by GitBook
On this page
  • On-chain Monitoring
  • Beaconcha.in V2
  • Rated Explorer
  • Lido Operators
  • Lido MEV Monitoring
  • Off-Chain Monitoring: Grafana
  • CSM Performance Threshold
  • Tips to improve performance
  1. Bonded Validators Setup
  2. Lido CSM

Monitoring

PreviousRole/Address managementNextAutomations

Last updated 2 months ago

On-chain Monitoring

Basic on-chain monitoring can be done using the following tools found on the CSM Widget directly. Under the Dashboard navbar tab scroll all the way down to the External Dashboards expandable list.

Beaconcha.in V2

Shows a wide range of performance data for all of the validator keys under your CSM Operator.

To receive notifications on when your validators go offline, open up the Validators pop-up window, click into each key, and add them to your watchlist. You will need to create a free account on Beaconcha.in in order to use this.

Rated Explorer

Provides more details on performance of all validator keys under your CSM Operator in aggregate. No built-in notifications available.

Lido Operators

Provides an overall view of validator keys uploaded onto the CSM Widget. Mouse over each category for a description of each metric.

Lido MEV Monitoring

Off-Chain Monitoring: Grafana

For more detailed monitoring, refer to the section below.

CSM Performance Threshold

Staying above the Lido CSM Performance Threshold enables CSM Operators to qualify for the socialized node operator rewards.

Lido CSM uses the following parameters to measure the Performance Threshold, where Performance Threshold = Average Validator Network Performance - Performance Leeway.

  • Performance of each validator = Successful Attestations / Total Attestations Assigned

  • Performance Leeway = 500 Basis Points (5%)

  • Frame = 28 days

e.g., For a 28 day period, if the Average Validator Network Performance is 99.6%, then your validators will need to achieve a 94.6% Performance level in order to qualify for the socialized node operator rewards.

Tips to improve performance

Provides details on blocks proposed by the validators under your CSM Operator over a period. If the Fee recipient is not equal to the designated fee recipient addresses for the respective networks, "" will be detected.

Average Validator Network Performance = A good proxy to use will be the Average Participation Rate found on .

MEV Stealing
Monitoring, Maintenance, and Updates
Rated Network
Maximising uptime and performance