dappnode / dappnodepackage-lighthouse-prater

Lighthouse DAppNode package (prater config)

Lighthouse prater ETH2.0 Beacon chain + validator

Lighthouse is an Ethereum consensus client that connects to other Ethereum consensus clients to form a resilient and decentralized proof-of-stake blockchain.

We implement the specification as defined in the ethereum/consensus-specs repository.

Updated	Champion/s
✔️	@pablomendez_95

dappnodepackage-lighthouse-prater's Issues

Use same beacon API ports for all Eth2 clients

Consider using the same beacon API port for all the eth2 clients for consistency (for instance the dappmanager could require this API for the module chain drivers to get beacon sync status)

Use port 3500 for Prysm, Lighthouse, Teku, ?

Implement chain driver in manifest

Implement chain driver to track Eth2 chain status in dappnode dashboard

Deppends on dappnode/DAppNodeSDK#193

Lock `public_keys.txt` file to improve security

Context

The public_keys.txt files contains the public keys used to start the teku binary for the validator flags. This file must not change unless the public keys exposed by the web3signer API are different, then it should be edited and the process will restart

To do

• Find a way to lock the file public_keys.txt and unlock it when required to avoid possible bugs.(chattrd cannot be used in docker containers)
• Consider using docker volumes stuff to provide read-only access

Wrong license

need to implement the proper license Apache-2.0 not GPL-3.0

Mismatch between URL link and Version under the "Version" information in the DAppStore Installer page

The issue here is similar to:
dappnode/DAppNodePackage-teku-prater#58

Describe the bug

To Reproduce

Expected behavior

Screenshots

DAppNode version:

• Package version:
• OS:
• Browser

Additional context

Review metadata files

There should be review the metadata files before released:

• README.md
• setup-wizard.yml
• dappnode_package.json
• getting-started.yml
  ....

Test Lighthouse + web3signer in network prater

Test instructions

You must have at least 2 Prater validators.

Install the web3signer prater and the client Lighthouse. You must get the hash from the Github latest release "dot".

In the client use the checkpoint sync feature to be able to start validating in minutes.

The web3signer will listen only to one client, you must select the client Lighthouse at config.

For a deeper test, you may find it useful to check out the grafana dashboards from the client, web3signer, and docker host.

Test report

With an editable unique comment report any errors and feedback you may find necessary.

Testers

• @pablomendezroyo ✔️
• @3alpha
• @tropicar ✔️
• @mgarciate ✔️

Set quick sync option

Set quick sync option as an optional feature in the setup-wizard

setup cronjob to periodically fetch public keys

Context

Eth2 clients must notice when a new validator is imported into the web3signer, so the public key is loaded into the eth2 client and start validating for it as well.

Approach

Setup a cronjob to periodically fetch public keys from web3signer API, so if there is a new pubkey restart the container to load the new public key

Track Lighthouse

Track the most important features in the road to Eth2 multiclient in DAppNode of the Lighthouse client.

• Implement web3signer support
• Immplement validator remote keymanager API: 🚀 sigp/lighthouse#3162
• Implement fee recipient: #52
• Run as separated services
• Checkpoint sync
• DAppNode package for Gnosis chain
• DAppNode package for mainnet
• Implement JWT

Implement public keys auto-check with API standard

Once Teku implements the API remote keymanager on the client there must be done:

• Enable client API
• Implement cronjob with auto-check repository: https://github.com/dappnode/eth2-pubkeys-autocheck

*Track API remote keymanager implementation at: dappnode/DAppNode#389

Lighthouse Prater v0.1.2 not working

Describe the bug

Lighthouse Prater not working

To Reproduce

1. Install the package
2. Check logs

Expected behavior

Lighthouse should be synced after a while

Screenshots

DAppNode version:

• Package version: 0.1.2 (v2.3.0 upstream)
• core.dnp.dappnode.eth: 0.2.55
• dappmanager.dnp.dappnode.eth: 0.2.50, commit: 552ab6c8

Port standardization

According to this issue dappnode/DAppNode#457, add the configuration to use the standard ports on Lighthouse
Sources: https://lighthouse-book.sigmaprime.io/advanced_networking.html

Lighthouse Prater Allowlist Headers

detailed in dappnode/DAppNode#461
1/4 of dappnode/DAppNode#468

Add RPC headers identifying calls as coming from lighthouse prater, so that the allow/whitelisting from dappnode/DAppNode#462 and dappnode/DAppNode#463 works properly, limiting the EL to listen to requests from one CL client.

Consider not persisting validators in the client

Currently, there is not implemented a way to delete validators using the Lighthouse client API. Consider not persisiting the validators in the docker volume, so it fetches from the web3signer every single time

Review cronjob

Review the cronjob used to fetch the publicKeys exposed by the web3signer API.

• Is one minute a good period of time to repeat the loop?
• What period of time would be considered as spamming the web3signer API?
• Prevent the cronjob from possible infinite loops

Prepare Lighthouse client for the merge

Add the configuration required for the Bellatrix upgrade:

Before this update https://github.com/sigp/lighthouse/releases/tag/v2.4.0 (07/22/2022) some flags were another.

• Indicate API engine endpoint

--execution-endpoints

• JWT authentication for the Engine API

--execution-jwt

• Override TTD flag

--terminal-total-difficulty-override

• Update to version 2.4.0 of the client

This configuration has been tested on Ropsnet network successfully.
Repo: https://github.com/tropicar/DAppNodePackage-lighthouse-ropsten

Improve `compare_public_keys` function

This is a critical function and must have high-quality code. Consider:

• Add unit tests for it
• Use of regex

Give read-only permissions to `public_keys.txt` file

The file public_keys.txt contains the public keys used to start the lighthouse binary and should not be edited at anytime until the process restarts.

Implement integration test for web3signer API

web3signer API is used in each eth2 client, there should be implemented integration test to test this API to be triggered in every new release

Improve quality code

Code for eth2 clients must be high quality, review all the code files and try to improve them

Set grafana prometheus metrics and grafana dashboards

Similar as is done in the Prysm-prater package set the corresponding files for collecting metrics and display them in the grafana dashboards

Upstream Lighthouse docs for metrics: https://lighthouse-book.sigmaprime.io/advanced_metrics.html?highlight=grafana#prometheus-metrics

Fetch pubkeys from web3signer api keymanager

Use the API keymanager endpoint /eth/v1/keystores to fetch the list of public keys. Use the public keys to set-up the Teku eth2-client in remote mode