Skip to main content

​
Mobile App Node Monitoring

​
General

This is a free monitoring tool provided by beaconcha.in to enhance the solo staking experience. The user specifies the monitoring endpoint on its consensus layer and validator node.
Screenshot: Mobile app and node monitoring overview
By using this endpoint, beaconcha.in will be allowed and is required to store the given data to display it in the beaconcha.in the mobile application. To protect user privacy, the IP address will never be stored

​
Requirements

  • beaconcha.in Account
  • beaconcha.in Mobile App
  • Lighthouse v.1.4.0 or higher
  • Prysm v1.3.10 or higher
  • Nimbus v1.4.1 or higher
  • Teku v22.3.0 or higher
  • Lodestar v1.6.0 or higher
  • Staking on Linux (No windows support by clients yet!)
Please adjust the network on the beaconcha.in browser and mobile app accordingly.
Both the beaconcha.in explorer and the mobile app are open source!

​
Lighthouse

A step-by-step guide on the Prater Testnet. Please adjust the network for your own needs.
  1. Open the Mobile App Tab and enter a name for your staking setup.
    Use the same worker name even if your consensus layer node runs on a separate machine than your validator node.
    Copy the generated flag and paste it to your beacon & validator node
Screenshot: Lighthouse mobile app flag in settings
Screenshot: Lighthouse command line flags
If your consensus layer node or execution layer node is not in sync yet, you will see some warning in the logs!
2. Open the beaconcha.in mobile app and login with your account under Preferences.
Your staking device will appear under Machines!
Screenshot: Mobile app Machines view

​
Prysm

  1. Head over to the beaconcha.in settings and open the prysm section:
Screenshot: Prysm section in beaconcha.in settings
2. Open a new Terminal and copy and paste the commands
Screenshot: Prysm exporter configuration
3. Make sure your Prysm client (consensus layer node and validator client) is already up and running. The exporter will now send the data to your mobile app!
Screenshot: Prysm exporter sending data
4. Wait a few minutes and open the beaconcha.in mobile app and login with your account under Preferences.

Your staking device will appear under Machines!
Screenshot: Mobile app Machines view

​
Nimbus

  1. Head over to the beaconcha.in settings and open the nimbus section:
Screenshot: Nimbus section in beaconcha.in settings
2. Add --metrics --metrics-port=8008 to your nimbus client! Otherwise, the exporter will not be able to get any data from your client.
Screenshot: Nimbus client metrics flags
3. Wait a few minutes and open the beaconcha.in mobile app and login with your account under Preferences.

Your staking device will appear under Machines!
Screenshot: Mobile app Machines view

​
Teku

Add the following endpoint to your teku node --metrics-publish-endpoint https://beaconcha.in/api/v1/client/metrics?apikey=YOUR_API_KEY You can find your API Key here: https://beaconcha.in/user/settings#app

​
Lodestar

Add the following CLI flag to your Lodestar validator and consensus layer node --monitoring.endpoint 'https://beaconcha.in/api/v1/client/metrics?apikey=YOUR_API_KEY' You can find your API Key in the account settings. Check out the Lodestar documentation about client monitoring for further details.

​
Monitoring with Rocket Pool

Works with Lighthouse, Lodestar, Teku and Nimbus only.

​
Lighthouse, Lodestar and Teku

Add Your beaconcha.in API key in Monitoring/Metrics (service config)
Screenshot: Rocket Pool service config Monitoring/Metrics API key

​
Nimbus

Nimbus does not expose all tracked data, some metrics such as validators are not visible in the app. Guide: https://gist.github.com/jshufro/89e32d417801bf3dfb02c32a983b63cf