Skip to content
This repository has been archived by the owner on Feb 28, 2025. It is now read-only.

changing contributions to rewards #505

Open
wants to merge 25 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
92 changes: 0 additions & 92 deletions docs/gov/community/contributions.md

This file was deleted.

88 changes: 88 additions & 0 deletions docs/gov/governance/incentives.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
---
sidebar_position: 6
description: Earning OBOL Programmatic Incentives
---

# OBOL Programmatic Incentives Program

Our aim is to encourage continuous participation and sustained support for Ethereum’s infrastructure network. The Obol Programmatic Incentives Program program is designed to be fair and transparent, acknowledging stakers for their participation in staking on DVs.

## What is the OBOL Programmatic Incentives Program?

OBOL Programmatic Incentives offer an opportunity to earn OBOL Token incentives for staking on Distributed Validators. 12.5m OBOL Tokens, or 2.5% of the supply, will be rewarded to stakers in the first year (2025). Incentives will begin to be accrued on February 24th, 2025. Claiming of incentives will be possible shortly thereafter.

Each week, 1/52 of the 12.5m OBOL will be distributed, or about 240,385 OBOL. Incentives *need to be claimed* either via the DV Launchpad, or via the UI frontend of participating partners.

## How do I participate in the OBOL Programmatic Incentives Program?

You can participate in the OBOL Programmatic Incentives Program by:

1. **Staking through Staking Partners**: For the current list of staking partners, please visit [obol.org/stake](https://obol.org/stake).

2. **Running your own DV Cluster**: You can create and manage your own DV cluster using our [DV Launchpad](https://launchpad.obol.org), for example using a [DappNode](https://dappnode.com/) or other hardware. This allows you to directly participate in the network's decentralisation efforts and earn OBOL incentives. Visit our [Squad Staking](https://squadstaking.com) page for inspiration and to find squad members.


## Is existing stake eligible?

All stake deposited after January 13th, 2025 is eligible to accrue incentives, once the program starts on February 24th, 2025. The exception is stake deposited directly on DVs, outside of staking protocols (via our DV Launchpad, for example). Such stake is eligible regardless of when it was deposited.

## How much OBOL will I receive per ETH staked on DVs?

The amount of OBOL you receive per ETH staked depends on the total amount of ETH participating in the program. The 240,385 OBOL per week will be distributed evenly across all participating ETH, so your share of the total participating ETH will determine your share of the OBOL incentives.


## How are incentives tracked?

By basing OBOL incentives on staking rewards accumulated by validators (pubkeys), performance is factored in (i.e. effectiveness, uptime, etc.)

Incentives are tracked in a centralised database off-chain - our API endpoints enable users and protocols to query how much incentives they have generated. These endpoints are used to show individuals’ incentives within the [Obol DV Launchpad](https://launchpad.obol.org) and partners’ staking platforms.

## How can I track my OBOL incentives?

If you’re running your own DV, your incentives will be displayed on the [DV Launchpad](https://launchpad.obol.org). If you’re staking through a partner product, they should display your incentives and distribute them to you.

## What benefits do I get from the OBOL Token?

OBOL Tokens serve as the basis for ownership and governance of the Obol Collective. Learn more on the [OBOL Token page](./obol-token.md) of the docs.

## How are incentives calculated?

OBOL incentives are based on validator staking rewards. They are calculated daily and tracked off-chain. The higher the effectiveness and uptime of your validators, the more incentives you will generate.

If the total staking rewards \( R \) for a validator are split among operators with percentages \( p_1, p_2, ..., p_n \), the rewards \( O \) for each operator can be calculated as:

Oᵢ = R × pᵢ × 0.01 × 1.01

where pᵢ is the split percentage for the i-th operator. We multiply by 1.01 to ensure that the full 1% of rewards is accurately distributed among operators, compensating for the initial deduction of 1% from the total rewards.

## Do I need to run my own validator to participate?

No, you can stake on DVs and track your incentives through the partners listed on [obol.org/stake](https://obol.org/stake). More partners are coming soon.

## Can I withdraw my staked ETH at any time?

There is no penalty for withdrawing stake or exiting your validator. You simply stop accruing incentives. The specific withdrawal policy will depend on the staking protocol used.

## What is the minimum amount of ETH needed to stake?

The minimum amount varies by staking protocol, please refer to each partner to determine the minimum amount of stake required.

## What happens if my validator has downtime?

Since OBOL incentives are tied to staking rewards, the amount of incentives earned is impacted by validator performance metrics like effectiveness and uptime.

## Will my incentives be public?

Yes, incentives are public and can be viewed through the Obol API, if you have the address of the protocol.

## How can I increase my OBOL Programmatic Incentives?

Incentives increase with more stake, as well as higher performance and uptime of your validators.

## What are the benefits of using distributed validators?

Distributed validators increase the security, resiliency, and decentralisation of Ethereum. Learn more at [obol.org/learn](https://obol.org/learn).

## How can I get support if I have issues?

Support is available through Obol’s [Discord](https://discord.gg/obol) and partners’ support channels.
6 changes: 5 additions & 1 deletion docusaurus.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ const config = {
from: '/docs/faq/client_configurations',
},
{
to: '/gov/governance/contributions',
to: '/gov/governance/incentives',
from: '/docs/faq/contributions',
},
{
Expand Down Expand Up @@ -233,6 +233,10 @@ const config = {
to: '/sdk',
from: '/docs/sdk',
},
{
to: '/gov/governance/incentives',
from: '/gov/governance/contributions',
},
//Redirect from multiple old paths to the new path
// {
// to: '/docs/newDoc2',
Expand Down
92 changes: 0 additions & 92 deletions versioned_docs/version-v1.2.0/gov/governance/contributions.md

This file was deleted.

Loading