LogoLogo
SDKAPI
Version-v1.4.0 (current)
Version-v1.4.0 (current)
  • Learn
    • Introduction
      • Obol Collective
      • OBOL Incentives
      • Key Staking Concepts
      • Obol vs Other DV Implementations
      • Obol Splits
      • DV Launchpad
      • Frequently Asked Questions
    • Charon
      • Introduction to Charon
      • Distributed Key Generation
      • Cluster Configuration
      • Charon Networking
      • CLI Reference
    • Futher Reading
      • Ethereum and Its Relationship With DVT
      • Community Testing
      • Peer Score
      • Useful Links
  • Run a DV
    • Quickstart
      • Quickstart Overview
      • Create a DV Alone
      • Create a DV With a Group
      • Push Metrics to Obol Monitoring
    • Prepare to Run a DV
      • How and Where To Run DVs
      • Deployment Best Practices
      • Test a Cluster
    • Running a DV
      • Activate a DV
      • Update a DV
      • Monitoring Your Node
      • Claim Rewards
      • Exit a DV
    • Partner Integrations
      • Create an EigenLayer DV
      • Create a Lido CSM DV
      • DappNode
  • Advanced & Troubleshooting
    • Advanced Guides
      • Create a DV Using the SDK
      • Migrate an Existing Validator
      • Enable MEV
      • Combine DV Private Key Shares
      • Self-Host a Relay
      • Advanced Docker Configs
      • Beacon node authentication
    • Troubleshooting
      • Errors & Resolutions
      • Handling DKG Failure
      • Client Configuration
      • Test Commands
    • Security
      • Overview
      • Centralization Risks and Mitigation
      • Obol Bug Bounty Program
      • Smart Contract Audit
      • Software Development at Obol
      • Charon Threat Model
      • Contacts
  • Community & Governance
    • Governance
      • Collective Overview
      • The Token House
      • The RAF
      • Delegate Guide
      • RAF1 Guide
    • The OBOL Token
      • Token Utility
      • Token Distribution & Liquidity
      • TGE FAQ
    • Community
      • Staking Mastery Program
      • Techne
    • Contribution & Feedback
      • Filing a Bug Report
      • Documentation Standards
      • Feedback
  • Walkthrough Guides
    • Walkthroughs
      • Walkthrough Guides
  • SDK
    • Intro
    • Enumerations
      • FORK_MAPPING
    • Classes
      • Client
    • Interfaces
      • ClusterDefinition
      • RewardsSplitPayload
    • Type-Aliases
      • BuilderRegistration
      • BuilderRegistrationMessage
      • ClusterCreator
      • ClusterLock
      • ClusterOperator
      • ClusterPayload
      • ClusterValidator
      • DepositData
      • DistributedValidator
      • ETH_ADDRESS
      • OperatorPayload
      • SplitRecipient
      • TotalSplitPayload
    • Functions
      • validateClusterLock
  • API
    • What is this API?
    • System
    • Metrics
    • Cluster Definition
    • Cluster Lock
    • State
    • DV Exit
    • Cluster Effectiveness
    • Terms And Conditions
    • Techne Credentials
    • Address
    • OWR Information
  • Specification
Powered by GitBook
On this page
  • Launchers and Deployment Tooling
  • Quickstart Guides
  • CL+VC Combinations:
Edit on GitHub
  1. Run a DV
  2. Prepare to Run a DV

How and Where To Run DVs

How and where to run DVs

PreviousPrepare to Run a DVNextDeployment Best Practices

Last updated 5 days ago

Launchers and Deployment Tooling

Quickstart Guides

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

Validator 👉 Consensus 👇
Teku v24.10.3
Lighthouse v5.3.0
Lodestar v1.23.0
Nimbus v24.10.0
Prysm v5.1.2
Remarks

Teku v24.10.3

✅

🟡

✅

✅

🟠

Teku beacon node needs the --validators-graffiti-client-append-format=DISABLED flag in order to produce blocks properly. Teku validator client is 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 validator client is only failing aggregation duties, which are not directly penalised but impact network density at high scale.

Lodestar v1.23.0

✅

🟡

✅

✅

🟠

Nimbus v24.10.0

✅

🟡

✅

✅

🟠

Prysm v5.1.2

✅

🟡

✅

✅

✅

Prysm validator client is failing aggregation duties 50% of the time, which are not directly penalised but impact network density at high scale. In some combinations rare failures of attestation and proposal duties were observed (0-2% per epoch).

Note: for the most recent compatability information, please see the from the most recent release of Charon.

Obol CDVN
Obol K8s
Obol Helm Charts
Obol Ansible Playbooks
Dappnode
Stereum
Sedge
Terraform Charon Relay
Terraform Grafana Charon dashboards
Run a DV alone
Run a DV as a group
release notes