OBOL Incentives
Last updated
Version-v1.4.0 (current)
Last updated
The OBOL Incentives Program is designed to be powerful and transparent, rewarding anyone OBOL tokens for staking on Distributed Validators (DVs).
OBOL Incentives offer an opportunity to earn OBOL Token incentives for staking on Distributed Validators.
12.5 million OBOL Tokens (2.5% of the total supply) will be distributed in the first year (2025).
Incentives begin accruing on March 24th, 2025.
Claiming will be possible starting May 12th, 2025.
Each week, 1/52 of the 12.5M OBOL will be distributed (~240,385 OBOL per week).
If you are staking with a partner, incentives will either be claimed via the participating partner UI frontends or via the as per the table below.
You can participate by:
Staking through Staking Partners
For the latest list of partners that qualify for OBOL Incentives, visit and see the table below.
Running Your Own DV Cluster
Use the to create and manage your own DV cluster, e.g., using a or other hardware. Please note, you must opt into to qualify for Obol Incentives.
This method directly supports Ethereum’s decentralization while earning OBOL incentives.
Visit the official Obol Discord to find squad mates.
If you are staking with a partner protocol, it's best to review the details of that partner at Obol.org/incentives. Only ETH staked on Obol DVs with qualified partners qualify for Obol Incentives and not all partners are created equal.
The OBOL amount per ETH depends on total ETH participation.
The 240,385 OBOL per week is distributed proportionally across all participating ETH.
Your share of the total ETH determines your share of OBOL incentives.
If you need help calculating your potential rewards, feel free to use this community created calculator:
NOTE: This is a community created calculator, is not managed by DV Labs or the Obol Association, and is not to be fully trusted.
OBOL incentives are based on staking rewards earned by validators (pubkeys). Performance factors like effectiveness and uptime impact rewards.
Incentives are tracked off-chain in a centralized database.
API endpoints allow users & protocols to query earned incentives.
Our rewards calculation and distribution system is built for accuracy, transparency, and security. We use Miga Labs' indexer to reliably track validator rewards, and all critical data—such as total rewards, split configurations, and depositor allocations—is verified on-chain and made publicly available for cross-verification. In cases where a partner misreports depositor splits, it only affects their own internal distribution and does not compromise the total rewards allocation or the fairness of the system.
For those staking with a Partner: Your staking platform should show and distribute your OBOL incentives in their UI frontend.
OBOL Tokens serve as the basis for ownership and governance of the Obol Collective. Learn more on the OBOL Token page.
OBOL incentives are tied to validator staking rewards and calculated daily.
For a validator with total staking rewards ( R ), and operator split percentages ( p_1, p_2, ..., p_n ), the operator’s rewards (Oᵢ) are:
[ Oᵢ = R × pᵢ × 0.01 × 1.01 ]
( pᵢ ) = Operator’s percentage split.
The 1.01 multiplier ensures the full 1% of rewards is distributed correctly.
Higher effectiveness & uptime = more incentives.
Yes, you can withdraw at anytime but you stop accruing incentives upon withdrawal.
If you are staking with a partner, they may choose to set penalties for early withdrawals but this is not common.
If you are running your own distributed validator, there is no penalty for withdrawing or exiting.
If you are staking with a partner, they will have their own minimum deposit amount.
If you are running your own distributed validator, the total amount required by your squad is 32 ETH.
Since OBOL incentives are tied to staking rewards, validator performance metrics directly impact earned incentives.
More uptime & effectiveness = More incentives.
Longer downtime = Fewer rewards.
Yes. Incentives are publicly accessible through the Obol API (with the correct protocol address).
Increase the amount of ETH staked.
Improve validator performance (higher uptime & effectiveness).
If you are staking with a partner, reach out to them directly.
For each partner listed below, you’ll find:
The eligible TVL for Obol Incentives
How depositors can claim these incentives
The portion of incentives (if any) retained by the partner
You’ll also see an estimated multiplier, which reflects how each partner manages these incentives.
A multiplier below 100% typically means Obol incentives are spread across all depositors, even though only a portion of the partner's total TVL is running Obol DVs.
A multiplier above 100% usually indicates that the partner is concentrating Obol rewards on a specific vault, which has less TVL than the total TVL running Obol DVs.
All of Mellow DVV TVL + Lido SDVT Module validators added post Jan 13th Airdrop + Lido CSM TVL ran by Obol DVs
Mellow Depositors: 80% for CSM TVL, 90% for SDVT TVL
Rest to Node Operators
≥ 100%
Portion of total TVL running on Obol DVs
<100%
Blockdaemon
TBD
According to partner's fee structure
TBD
Total TVL of the OBOL Vault
TBD
According to partner's fee structure
= 100%
Portion of total TVL running on Obol DVs
TBD
According to partner's fee structure
< 100%
Portion of total TVL running on Obol DVs
< 100%
Portion of total TVL running on Obol DVs
TBD
According to partner's fee structure
< 100%
TBD
According to partner's fee structure
TBD
Portion of total TVL running on Obol DVs
According to partner's fee structure
= 100%
If you are staking yourself directly on Obol DVs and/or Squad Staking, your stake is 100% eligible for rewards. Please note, you must opt into to qualify for Obol Incentives.
Incentives are displayed in the and/or participating partner UI frontends.
For those running their own Distributed Validators: Incentives are displayed on the .
Check each partner’s requirements at .
Distributed Validators improve performance, lower risks and increase rewards. Learn more at .
Join the Obol Discord community: .
Directly accruing as
According to partner's
According to partner's
