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

Run single Lodestar beacon node #555

Closed
nflaig opened this issue Apr 12, 2024 · 0 comments · Fixed by #558
Closed

Run single Lodestar beacon node #555

nflaig opened this issue Apr 12, 2024 · 0 comments · Fixed by #558

Comments

@nflaig
Copy link
Contributor

nflaig commented Apr 12, 2024

Right now it's not possible to run just a single Lodestar beacon node without passing additional params

This configuration works

participants:
  - el_type: geth
    el_image: ethereum/client-go:stable
    cl_type: lodestar
    cl_image: chainsafe/lodestar:next
    cl_extra_params:
      - --sync.isSingleNode
      - --network.allowPublishToZeroPeers
    vc_type: teku
    vc_image: consensys/teku:latest
    count: 1

But would it be possible to detect if there is just one node (participant) and automatically set the cl_extra_params as in the provided config?

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

Successfully merging a pull request may close this issue.

1 participant