Skip to content

Render validator client config with charon vc-bundle - #523

Draft
KaloyanTanev wants to merge 4 commits into
mainfrom
kalo/vc-bundle
Draft

KaloyanTanev wants to merge 4 commits into
mainfrom
kalo/vc-bundle

Conversation

@KaloyanTanev

@KaloyanTanev KaloyanTanev commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Every validator client run.sh reimplements key import and proposer-settings rendering in shell, and Lighthouse, Nimbus, Prysm and Teku need custom Dockerfiles to get the tools for it. This PR moves that work into charon's charon alpha vc-bundle, added in ObolNetwork/charon#4844 as part of charon's proposer config stack (https://github.com/ObolNetwork/charon/stack/4832).

A one-shot vc-bundle service renders the selected VC's keystores and proposer settings into .charon/vc-bundle before the VC starts. Each run.sh copies its keys and settings into the VC's own data directory and runs only from there, with the distributed-validator flags written inline. The custom Dockerfiles are removed and the upstream images are used. Prysm reads a wallet that charon writes, so no import step is needed.

  • Nimbus accepts builder settings only as flags, so its run.sh reads them from the bundle's vc-flags.txt, and only the first builder is used.
  • Teku runs develop for now: its builder flags and builders in the proposer config file are not released yet (latest is 26.10.3).
  • Lodestar runs with --builder.selection=maxprofit, the only selection under which it applies the boost factor from the proposer settings, so VC_LODESTAR_BUILDER_SELECTION is removed.
  • The bundle is rendered again whenever the VC container is created, e.g. docker compose down then up. docker compose restart <vc>, or up -d while the VC is running, keeps the old settings.
  • Needs a charon image with the proposer config stack, which is not released yet. Until then, set CHARON_VERSION to a local build of the stack's top branch.

@KaloyanTanev KaloyanTanev self-assigned this Nov 16, 2026
@sonarqubecloud

Copy link
Copy Markdown

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 this pull request may close these issues.

1 participant