How and where to run DVs

Launchers and Deployment Tooling

• Obol CDVN
• Obol K8s
• Obol Helm Charts
• Obol Ansible Playbooks
• Dappnode
• Stereum
• Sedge
• Terraform Charon Relay
• Terraform Grafana Charon dashboards

Quickstart Guides

• Run a DV alone
• Run a DV as a group
• Run a DV using the SDK

CL+VC Combinations:

Legend

• ✅: All duties succeed in testing
• 🟡: All duties succeed in testing, except non-penalised aggregation duties
• 🟠: Duties may fail for this combination
• 🔴: One or more duties fails consistently

Consensus 👇 Validator 👉	Teku v24.8.0	Lighthouse v5.3.01	Lodestar v1.20.2	Nimbus v24.7.0	Prysm PR	Remarks
Teku v24.8.0	🟡	🟡	✅	✅	🟠	Teku bn needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku vc are only failing aggregation duties 50% of the time, which are not directly penalised but impact network density at high scale.
Lighthouse v5.3.0	🟡	🟡	✅	✅	🟠	Lighthouse vc are only failing aggregation duties, which are not directly penalised but impact network density at high scale.
Nimbus v24.7.0	🟡	🟡	✅	✅	✅	Nimbus beacon nodes requires that you add the following flag to charon run: charon run --feature-set-enable=json_requests
Prysm v5.0.3	🟡	🟡	✅	✅	✅	Prysm validator needs a particular pull request merged and released for aggregation duties to succeed.
Lodestar v1.20.2	🟡	🟡	✅	✅	🔴

Note:

• Blinded beacon block proposals are only supported from cluster lock version v1.7 and charon release v0.17.0 onwards.
• Prysm VC support is added from prysm version v5.0.0 onwards.

Footnotes

1. sync committee and aggregator duties are not yet supported in a DV setup by Lighthouse, all other duties work as expected. ↩