Skip to content

Latest commit

 

History

History
137 lines (81 loc) · 5.58 KB

mobile-app-less-than-greater-than-beacon-node.md

File metadata and controls

137 lines (81 loc) · 5.58 KB
Raw
description
A step by step tutorial on how to monitor your staking device & beaconnode on the beaconcha.in mobile app

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 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

  • 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!)

{% hint style="info" %} Please adjust the network on the beaconcha.in browser and mobile app accordingly. {% endhint %}

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 beaconnode runs on a seperate machine than your validator node.
    __
    __Copy the generated flag and paste it add it to your beacon & validator node
    __

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


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

Prysm

  1. Head over to the beaconcha.in settings and open the prysm section:

2. Open a new Terminal and copy paste the commands

3. Make sure your Prysm client (beacon & validator) is already up and running. The exporter will now send the data to your mobile app!

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 !

Nimbus

  1. Head over to the beaconcha.in settings and open the nimbus section:

2. Add --metrics --metrics-port=8008 to your nimbus client! Otherwise the exporter will not be able to get any data from your client.

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 !

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 beaconnode --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)

****

Nimbus

Nimbus does not expose every data, thus, some data such as validators are not visible in the app.

Guide: https://gist.github.com/jshufro/89e32d417801bf3dfb02c32a983b63cf

Gnosis

Just as on Ethereum, the flag can be found at https://beaconcha.in/user/settings#app OR https://gnosischa.in/user/settings#app.

Please note that the API key for beaconcha.in users is the same on gnosischa.in, so it doesn't matter which one is chosen.

The same applies to the flag in the instructions. However, it's recommended to use the beaconcha.in endpoint as it offers several fallbacks.

The best support for the metric feature is available using the Lighthouse client. Other clients may not work or may only support a limited number of metrics in the app.