7.8 Execution Dashboard

To list your node on an Execution Status Page, you can add a ETHStats secret to your execution client to monitor versions, latencies, peers, synced blocks, and pending transactions based on their current gas price configuration. You node will then begin to synchronize data with the dashboard service, so the service can be monitored from any device.

Dashboard	Maintainer	Access	Credentials
Mainnet Execution Status Page ↗	LUKSO Team	Private	Server: stats.execution.mainnet.lukso.network Secret: Apply as core contributor via Discord
Testnet Execution Status Page ↗	LUKSO Team	Private	Server: stats.execution.testnet.lukso.network Secret: Apply as Testnet operator via Discord
Stakingverse Status Page ↗	Community	Public	Server: community.stats.execution.stakingverse.io Secret: Stakingverse-JordyDutch-69420

info

The following steps are performed on your 📟 node server.

1. Stop Node Operation

Depending on your setup method, there are different ways to stop your node before listing your node on a dashboard.

LUKSO CLI

cd <lukso-working-directory>
lukso stop

info

Exchange <lukso-working-directory> with the path of the node folder.

Service Automation

sudo systemctl stop lukso-validator

Force Client Shutdown

Geth

sudo pkill geth

Erigon

sudo pkill erigon

Nethermind

sudo pkill nethermind

Besu

sudo pkill besu

Teku

sudo pkill teku

Nimbus-Eth2

sudo pkill nimbus_beacon_node
sudo pkill nimbus_validator_client

Lighthouse

sudo pkill lighthouse

tip

The Lighthouse client uses a single binary for both the consensus and validator processes.

Prysm

sudo pkill prysm
sudo pkill validator

2. Add ETHStats Secret

You can either set your dashboard credentials via startup flags or persistently within the configuration files of your execution client. If you only want to check your node temporarily, using the flag is recommended, as it will only persist until the next restart of the node.

Setting a Startup Flag

Depending on your setup method, there are different ways to pass down the ETHStats flag using the LUKSO CLI.

LUKSO CLI Node

Every execution client has a individual flag to set the ETHStats Secret during startup.

Geth

cd <lukso-working-directory>

# Start the Mainnet Node with a ETHStats Secret
lukso start --checkpoint-sync --geth-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

# Start the Testnet Node with a ETHStats Secret
lukso start --testnet --checkpoint-sync --geth-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Erigon

cd <lukso-working-directory>

# Start the Mainnet Node with a ETHStats Secret
lukso start --checkpoint-sync --erigon-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

# Start the Testnet Node with a ETHStats Secret
lukso start --testnet --checkpoint-sync --erigon-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Nethermind

cd <lukso-working-directory>

# Start the Mainnet Node with Custom Name
lukso start --checkpoint-sync --nethermind-ethstats-enabled=true --nethermind-ethstats-name "<your-dashboard-name>" --nethermind-ethstats-secret "<ethstats-secret>" --ethstats-server "wss://<ethstats-server>"

# Start the Testnet Node with Custom Name
lukso start --testnet --checkpoint-sync --nethermind-ethstats-enabled=true --nethermind-ethstats-name "<your-dashboard-name>" --nethermind-ethstats-secret "<ethstats-secret>" --nethermind-ethstats-server "wss://<ethstats-server>"

Besu

cd <lukso-working-directory>

# Start the Mainnet Node with a ETHStats Secret
lukso start --checkpoint-sync --besu-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

# Start the Testnet Node with a ETHStats Secret
lukso start --testnet --checkpoint-sync --besu-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

info

The following properties need to be exchanged:

• <lukso-working-directory> with the path of the node folder
• <your-dashboard-name> with the node name to show up on the dashboard
• ethstats-secret with the actual secret of your dashboard server
• ethstats-server with the address of your dashboard server

After the clients were started, verify that their services are still up.

sudo lukso status

LUKSO CLI Validator

Every execution client has a individual flag to set the EthStats Secret during startup.

Geth

cd <lukso-working-directory>

# Start the Mainnet Validator Node with Custom Name
lukso start --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --geth-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

# Start the Testnet Validator Node with Custom Name
lukso start --testnet --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync  --geth-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Erigon

cd <lukso-working-directory>

# Start the Mainnet Validator Node with Custom Name
lukso start --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --erigon-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

# Start the Testnet Validator Node with Custom Name
lukso start --testnet --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --erigon-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Nethermind

cd <lukso-working-directory>

# Start the Mainnet Validator Node with Custom Name
lukso start --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --nethermind-ethstats-enabled=true --nethermind-ethstats-name "<your-dashboard-name>" --nethermind-ethstats-secret "<ethstats-secret>" --nethermind-ethstats-server "wss://<ethstats-server>"

# Start the Testnet Validator Node with Custom Name
lukso start --testnet --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --nethermind-ethstats-enabled=true --nethermind-ethstats-name "<your-dashboard-name>" --nethermind-ethstats-secret "<ethstats-secret>" --nethermind-ethstats-server "wss://<ethstats-server>"

Besu

cd <lukso-working-directory>

# Start the Mainnet Validator Node with Custom Name
lukso start --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --besu-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

# Start the Testnet Validator Node with Custom Name
lukso start --testnet --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync --besu-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

info

The following properties need to be exchanged:

• <lukso-working-directory> with the path of the node folder
• <your-fee-recipient-address> with the wallet address receiving staking profits
• <your-dashboard-name> with the node name to show up on the dashboard
• ethstats-secret with the actual secret of your dashboard server
• ethstats-server with the address of your dashboard server

After the clients were started, verify that their services are still up.

sudo lukso status

Service Automation

Open the startup script within your node directory with your preferred text editor.

Vim

sudo vim <lukso-working-directory>/static/lukso_startup.sh

Nano

sudo nano <lukso-working-directory>/static/lukso_startup.sh

info

Exchange <lukso-working-directory> with the path to the node folder.

Add the ETHStats flag new line to the start command, then save and exit the file.

Geth

exec /usr/local/bin/lukso start \
        --validator \
        --validator-wallet-password ./static/<your-generic-password-file> \
        --transaction-fee-recipient "<your-fee-recipient-address>" \
        --checkpoint-sync \
        --geth-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Erigon

exec /usr/local/bin/lukso start \
        --validator \
        --validator-wallet-password ./static/<your-generic-password-file> \
        --transaction-fee-recipient "<your-fee-recipient-address>" \
        --checkpoint-sync \
        --erigon-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Nethermind

exec /usr/local/bin/lukso start \
        --validator \
        --validator-wallet-password ./static/<your-generic-password-file> \
        --transaction-fee-recipient "<your-fee-recipient-address>" \
        --checkpoint-sync \
        --nethermind-ethstats-enabled=true \
        --nethermind-ethstats-name   "<your-dashboard-name>" \
        --nethermind-ethstats-secret "<ethstats-secret>" \
        --nethermind-ethstats-server "wss://<ethstats-server>" \

Besu

exec /usr/local/bin/lukso start \
        --validator \
        --validator-wallet-password ./static/<your-generic-password-file> \
        --transaction-fee-recipient "<your-fee-recipient-address>" \
        --checkpoint-sync \
        --besu-ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

info

The following properties need to be exchanged:

• <your-generic-password-file> with the name of your validator password file
• <your-fee-recipient-address> with the wallet address receiving staking profits
• <your-dashboard-name> with the node name to show up on the dashboard
• ethstats-secret with the actual secret of your dashboard server
• ethstats-server with the address of your dashboard server

After the startup script was updated, you can restart the node by executing the related service.

sudo systemctl start lukso-validator

Modifying the Client Configuration

Depending on your execution client, the ETHStats Secret can be set with different properties.

Geth

Open the configuration file using your preferred text editor.

Vim

cd <lukso-working-directory>/configs/<network>/geth/
vim geth.toml

Nano

cd <lukso-working-directory>/configs/<network>/geth/
nano geth.toml

Erigon

Open the configuration file using your preferred text editor.

Vim

cd <lukso-working-directory>/configs/<network>/erigon/
vim erigon.toml

Nano

cd <lukso-working-directory>/configs/<network>/erigon/
nano erigon.toml

Nethermind

Open the configuration file using your preferred text editor.

Vim

cd <lukso-working-directory>/configs/<network>/nethermind/
vim nethermind.cfg

Nano

cd <lukso-working-directory>/configs/<network>/nethermind/
nano nethermind.cfg

Besu

Open the configuration file using your preferred text editor.

Vim

cd <lukso-working-directory>/configs/<network>/besu/
vim besu.toml

Nano

cd <lukso-working-directory>/configs/<network>/besu/
nano besu.toml

info

The following properties need to be exchanged:

• <lukso-working-directory> with the path to the node folder.
• <network> with the name of your node's network.

Add the ETHStats Secret as a new line within the settings, then save and exit the file.

Geth

Search for the Ethstats section, then add and uncomment the URL property under it.

[Ethstats]
URL = "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Erigon

Set and uncomment the ethstats property at the end of the file.

"ethstats" = "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

Nethermind

Set the EthStats object and Name property at the ending bracket of the Network object.

"EthStats": {
  "Enabled": true,
  "Name": "<your-dashboard-name>",
  "Secret": "<ethstats-secret>",
  "Server": "wss://<ethstats-server>"
}

Besu

Set the ethstats property at the end of the file.

'ethstats'='<your-dashboard-name>:<ethstats-secret>@<ethstats-server>'

info

The following properties need to be exchanged:

• <your-dashboard-name> with the node name to show up on the dashboard
• ethstats-secret with the actual secret of your dashboard server
• ethstats-server with the address of your dashboard server

warning

Ensure there are no missing spaces, characters or unintended linebreaks before saving the configuration file.

Depending on your setup method, there are different ways to start your node after setting the ETHStats Secret.

LUKSO CLI Node

cd <lukso-working-directory>
lukso start --checkpoint-sync

info

Exchange <lukso-working-directory> with the path of the node folder.

LUKSO CLI Validator

cd <lukso-working-directory>
lukso start --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync

info

The following properties need to be exchanged:

• <lukso-working-directory> with the path of the node folder
• <your-fee-recipient-address> with the wallet address receiving staking profits

Service Automation

sudo systemctl start lukso-validator

After the clients were started, verify that their services are still up.

sudo lukso status

🎨 DAppNode

On a DAppNode setup, the Geth client can be adjusted from the user interface.

1. Stop Node Operation: Stop the execution and consensus client within the Node Operation View.

2. Navigate to Staker Menu: Open the LUKSO Stakers menu and move into the Lukso Geth Package.

3. Adjust Slasher Value: Navigate to the Configs window and add the ETHStats flag in the EXTRA_OPTS field.

--ethstats "<your-dashboard-name>:<ethstats-secret>@<ethstats-server>"

info

The following properties need to be exchanged:

• <your-dashboard-name> with the node name to show up on the dashboard
• ethstats-secret with the actual secret of your dashboard server
• ethstats-server with the address of your dashboard server

4. Restart the Node: Restart the execution and consensus client within the Node Operation View.