Mobile App <> Node Monitoring

A step by step tutorial on how to monitor your staking device & beaconnode on the beaconcha.in mobile app.

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 beacon & validator node.

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

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. Head over to the user settings on beaconcha.in and create an API key

  1. Open the Mobile App Tab and enter a name for your staking setup. Use the same worker name even if your beaconnode runs on a seperate machine than your validator node.

beaconcha.in/user/settings

3. Copy the generated flag and paste it add it to your beacon & validator node

Lighthouse Beacon & Validator node

If your beacon-node or Ethereum 1.0 node is not in sync yet, you will see some warning logs!

4. Open the beaconcha.in mobile app and login with your account under Preferences. Your staking device will appear under Machines!

Prysm

This functionality is in its early stage alpha testing and may not be fully functional at this time.

  1. Head over to the user settings on beaconcha.in

  2. Open the Mobile App Tab and enter a name for your staking setup. Use the same worker name even if your beaconnode runs on a seperate machine than your validator node.

  3. Make sure your prysm.sh file is updated and supports client-stats Updated version: https://github.com/prysmaticlabs/prysm/blob/develop/prysm.sh

  4. Open an extra terminal next to your validator and beacon-node and modify YOUR-API-KEY and DEVICE-NAME

    Use the same worker name even if your beaconnode runs on a seperate machine than your validator node.

    ./prysm.sh client-stats --beacon-node-metrics-url=http://localhost:8080/metrics --validator-metrics-url=http://localhost:8081/metrics --clientstats-api-url=https://beaconcha.in/api/v1/stats/<YOUR-API-KEY>/<DEVICE-NAME>

Docs: https://docs.prylabs.network/docs/prysm-usage/client-stats/

Nimbus

Teku