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
  • Claim Status
  • Claim Flow​
  • Launchpad Edge Cases​
Edit on GitHub
  1. Run a DV
  2. Running a DV

Claim Rewards

PreviousMonitoring Your NodeNextExit a DV

Last updated 6 days ago

Introduction

For every epoch, active validators earn ETH rewards from both the consensus layer and the execution layer. The consensus layer rewards are derived from validator duties such as attestation, proposals, and sync committees. These rewards are accumulated in the validator’s withdrawal address. Execution rewards, which are earned from MEV and transaction priority tips, are accumulated in the fee recipient address.

The method for claiming rewards depends on the Cluster's withdrawal configuration, whether it's an or an . The table below outlines the latest details on how and where to claim rewards.

Claim Status

\

Withdrawal Configuration
Subcategory Description
Is supported on Launchpad?
Where to claim?

1. Claim principal + rewards without splits - Exit and get rewards

To claim principal or rewards without splits, users currently have to exit the validator.

✅

2. Splits only rewards using OWR - ETH

For all clusters with ETH rewards.

✅

3. Split principal + rewards - ETH

For clusters configured to split both principal and rewards.

✅

4. Splits non-ETH rewards using any withdrawal config - wstETH or weETH

For Lido and EtherFi clusters earning rewards in protocol-specific tokens.

In Progress ➡️

5. Lido CSM rewards - wstETH

For all Lido CSM clusters earning wstETH rewards.

In Progress ➡️

Claim Flow

To understand how claims via Launchpad work, it is highly recommended to first understand how splits work. More details are available . The flowchart below summarizes how an operator and a non-operator can interact with split contracts to facilitate claims:

  1. All validator rewards are accumulated in the validator's withdrawal address, which is a split wallet.

  2. Claims can be triggered in two ways:

    1. From addresses in the Splitter: Splitter addresses will see a Claim All button. When the first address (e.g., address A) executes Claim All, it triggers a multi-call transaction to distribute rewards from all the split wallets associated with a cluster into the Split Main. The Split Main then sends address A’s proportion of the rewards (based on the split configuration at the time of cluster creation). All of this is executed with a single click for the first address.

    2. From addresses not in the Splitter: Non-splitter addresses will see a Distribute All button instead of Claim All. These addresses cannot claim rewards directly but can distribute rewards to the Split Main (subsidizing transaction fees for others). Operators can then claim rewards later by visiting the same cluster details page.

  3. Internally, after clicking Claim All or Distribute All, the split wallet sends the funds to the Split Main contract.

  4. The Split Main then sends proportional rewards to address A, completing steps 2a, 3, and 4 with a single click.

  5. Other addresses (e.g., B, C, D) can later click on Claim All to receive their share of the rewards.

We are constantly improving the user experience. Below are some edge cases to avoid confusion:

Case 1: The Claimable column doesn’t match the amount next to the Claim All button.

In this scenario, someone else (a splitter or non-splitter address) has already distributed rewards to the Split Main (e.g., 0.12 ETH). However, your validators (4 in this case) have earned an additional 0.2 ETH in rewards. Your total effective claimable balance is 0.032 ETH, which you can claim using the Claim All button.

Your total effective claimable amount will always be displayed next to the Claim All button.

This happens because the connected address is not listed in the split configuration. You may have used a different operator address from the one in the splitter configuration. You can:

  • Distribute all rewards using the connected address for all operators and claim using your address in the splitter configuration.

  • Switch to the splitter address and claim directly.

Note: It costs the same gas to distribute rewards for one address as it does for all addresses.

Case 3: You just created a new cluster with no active validators or rewards, but it shows a Claim All amount.

The amount shown here is from a previous case and is now sitting in the Split Main, ready to be claimed. Unfortunately, it is not possible to associate the Split Main balance of an address with a specific cluster. If you are part of multiple clusters, your Split Main balance will appear next to all Claim All buttons, regardless of the cluster. We are working on a fix to avoid this confusion.

Cluster details page in the Operator Dashboard. For example, .

Cluster details page in the Operator Dashboard. For example, .

Operators currently need to use the UI provided by Splits.org. For example, a .

Operators currently need to use the UI provided by Splits.org. For example, a .

Similar to row number 3, use the Splits UI. More details can be found at the bottom of .

Launchpad Edge Cases

Case 2: You don’t see a Claim All button but instead see Distribute All.

​
​
here
here
Lido Split
Lido Split
this page
​
OWR
Exitable Withdrawal Configuration
​
here