Lido CSM Dashboard

Lido CSM Operator Dashboard - Track your Community Staking Module validator earnings, bond status, APY metrics, strikes, and health status.

  • Crypto Currency
  • Monitoring & Logging
  • Tools & Utilities
Lido CSM Operator Dashboard - Track your Community Staking Module validator earnings, bond status, APY metrics, strikes, and health status. Features both a web UI and CLI interface.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

49/100 Fair

Maintained
76last commit 63 days ago
Popular
176 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 29 days ago

GitHub stars
6
Open issues
0
Last commit
2026-09-19
Latest release
v0.6.3
Activity
stale

Checked 9 days ago - source: GitHub (0xdespot/lido-csm-dashboard)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Copy the sample settings file Create a real .env file from .env.example and fill in the required values before starting the app. Without this, the app may fail to start or connect with missing settings. source
  • Use port 3000 for the server The app listens on port 3000 by default, so use that port to open the dashboard. If you need to reach it from another machine, open or forward port 3000; otherwise remote access will not work. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to create a .env file before starting the dashboard?

Copy .env.example to .env and set the values you need. Environment variables override .env values, which override built-in defaults.

Which port should I use for reverse proxy or remote access?

The Docker image binds to 0.0.0.0 on port 3000, while non-Docker defaults to 127.0.0.1 on 8080. Set HOST and PORT to change the bind and expose or forward that port.

Can I use public Ethereum RPC endpoints for all features?

Lighter pages can work with a public endpoint, but Distribution History needs your own node because it performs many eth_getLogs scans. Public endpoints may rate-limit or time out and cause the history panel to show an RPC error.

Where is local data stored if I need to back it up?

CACHE_DIR is the root for the operator database, CID cache, and IPFS cache, defaulting to ~/.cache/csm-dashboard. DATABASE_PATH can override only the database location if you want to relocate or back it up separately.

Are API keys required for the dashboard?

No; BEACON_API_KEY is optional for higher beaconcha.in rate limits, and ETHERSCAN_API_KEY is optional but recommended for more accurate historical data.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads