Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CL light client support #101

Open
etan-status opened this issue Jun 1, 2022 · 0 comments
Open

Add CL light client support #101

etan-status opened this issue Jun 1, 2022 · 0 comments

Comments

@etan-status
Copy link
Contributor

There is an additional nimbus_light_client binary available in nimbus-eth2 unstable (and, eventually, also on the other branches). It would be interesting to have a few instances of these in the fleet to collect metrics regarding bandwidth (primary), memory, and CPU.

Compared to nimbus_beacon_node, the nimbus_light_client binary does not need a data-dir.
It takes similar arguments for configuring logs and libp2p settings (port numbers etc).

However, there is an additional --trusted-block-root argument that needs to be initialized to a recent checkpoint block root.

To obtain a --trusted-block-root, an existing nimbus_beacon_node could be queried:

curl -s "http://hostname:port/eth/v1/beacon/headers/finalized" | jq -r '.data.root'

For all the launch arguments, see https://github.com/status-im/nimbus-eth2/blob/62bfe97bbed8acd511817ef85d6ff9acaebeefe6/beacon_chain/conf_light_client.nim

For sample integration into the launch_local_testnet script used in CI, see https://github.com/status-im/nimbus-eth2/blob/62bfe97bbed8acd511817ef85d6ff9acaebeefe6/scripts/launch_local_testnet.sh#L742-L752

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant