Skip to content

Commit 915face

Browse files
committed
added rewards v2.2
1 parent 198cc78 commit 915face

File tree

2 files changed

+24
-17
lines changed

2 files changed

+24
-17
lines changed

docs/eigenlayer/concepts/rewards/rewards-concept.md

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -4,34 +4,39 @@ title: Overview
44
---
55

66
Rewards are tokens distributed to Stakers and Operators by an AVS to reward Stakers and Operators for participation in securing AVSs.
7-
Rewards implements the [EigenLayer Improvement Proposal-001: Rewards v2](https://github.com/eigenfoundation/ELIPs/blob/main/ELIPs/ELIP-001.md).
87

9-
EigenLayer has a flexible rewards mechanism that enables:
8+
## Rewards v2 and v2.1
109

11-
* [Operator directed Rewards](rewards-submission.md)
10+
Rewards v2 (operator directed rewards) implements the [EigenLayer Improvement Proposal-001: Rewards v2](https://github.com/eigenfoundation/ELIPs/blob/main/ELIPs/ELIP-001.md).
11+
Rewards v2.1 (operator directed Operator Set rewards) uses the same operator directed model but scoped to a specific Operator Set
12+
rather than AVS-wide.
1213

13-
AVSs can [direct performance-based rewards](../../developers/howto/build/submit-rewards-submissions.md) to specific Operators using custom logic. Operator directed Rewards enable
14-
rewards to be distributed based on work completion, quality or other parameters determined by the AVS, allowing flexible and tailored incentives.
14+
Using operator directed rewards (v2) and operator directed Operator Set rewards (v2.1), AVSs can [direct performance-based rewards](../../developers/howto/build/submit-rewards-submissions.md) to specific Operators using custom logic. Operator directed Rewards enable
15+
rewards to be distributed based on work completion, quality or other parameters determined by the AVS, allowing flexible and tailored incentives.
1516

16-
* [Variable Operator Fee Splits for AVS Rewards](rewards-split.md)
17+
## Rewards v2.2
1718

18-
Operators can [set their per-AVS fee rate](../../operators/howto/configurerewards/set-rewards-split.md) on AVS Rewards to any amount from 0% to 100%. The default split is 10%. Setting
19-
a variable split per-AVS enables Operators to align their fee structures with their economic needs and the complexity and diversity of AVS demands.
20-
Operator fees can be varied by Operator Set for more granular reward fee structures.
19+
Rewards v2.2 (unique stake and total stake Operator Set rewards) implements [ELIP-014](https://github.com/eigenfoundation/ELIPs/blob/main/ELIPs/ELIP-014.md), and:
20+
* Unique stake rewards distributes based on allocated unique stake (`magnitude / max_magnitude`) within an Operator Set.
21+
* Total stake rewards distributes based on total delegated stake within an Operator Set.
2122

22-
* [Variable Operator Splits for Programmatic Incentives](rewards-split.md)
23+
Rewards v2.2 enables auto-weighted distribution supports both retroactive and forward-looking submissions (up to 2 years).
2324

24-
Operators can [set their split of Programmatic Incentives](../../operators/howto/configurerewards/set-pi-split) to any amount from 0% to 100%. The default split is 10%. Setting
25-
a split enables Operators to have flexibility in determining the appropriate take rate. The Programmatic Incentive splits
26-
integrate with the Rewards distribution process which ensures that Stakers delegating to Operators benefit proportionately.
25+
## Rewards split
26+
27+
Operators can [set their per-AVS fee rate](../../operators/howto/configurerewards/set-rewards-split.md) on AVS Rewards to any amount from 0% to 100%. The default split is 10%. Setting
28+
a variable split per-AVS enables Operators to align their fee structures with their economic needs and the complexity and diversity of AVS demands.
29+
Operator fees can be varied by Operator Set for more granular reward fee structures.
30+
31+
## Rewards submission, calculation, and distribution
2732

2833
Rewards are submitted, calculated, and distributed as follows:
2934

3035
1. [AVSs submit rewards submissions to Operators and Stakers](../../developers/howto/build/submit-rewards-submissions.md).
3136
2. The Rewards updater calculates Rewards offchain and consolidates these into a merkle root posted onchain.
3237
3. [Operators and Stakers claim their allocated Rewards](rewards-claiming).
3338

34-
## Rewards Calculation
39+
## Rewards calculation
3540

3641
Rewards are calculated via an offchain process. A Merkle root (known as the distribution root) is posted which represents
3742
the cumulative rewards across all earners weekly on mainnet and daily on testnet. There is an additional 2 hour delay on

docs/eigenlayer/developers/howto/build/submit-rewards-submissions.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,10 @@ For information on Rewards concepts, refer to [Rewards Overview](../../../concep
1414

1515
Submitting rewards for an AVS is handled by the [RewardsCoorinator core contract](../../concepts/eigenlayer-contracts/core-contracts.md).
1616

17-
To submit rewards submissions, use [`RewardsCoordinator.createOperatorDirectedOperatorSetRewardsSubmission`](https://github.com/Layr-Labs/eigenlayer-contracts/blob/main/docs/core/RewardsCoordinator.md#createoperatordirectedoperatorsetrewardssubmission).
17+
To submit rewards submissions, use:
18+
* [`RewardsCoordinator.createOperatorDirectedOperatorSetRewardsSubmission`](https://github.com/Layr-Labs/eigenlayer-contracts/blob/main/docs/core/RewardsCoordinator.md#createoperatordirectedoperatorsetrewardssubmission)
19+
for Rewards v2 (operator directed rewards) and Rewards v2.1 (operator director Operator Set rewards).
20+
* `createUniqueStakeRewardsSubmission` or `createTotalStakeRewardsSubmission` for Rewards v2.2 (unique stake and total stake Operator Set rewards).
1821

1922
An AVS can use onchain or offchain data in rewards logic to determine the reward amount per Operator. The rewards can be calculated
2023
based on the work performed by Operators during a certain period of time, can be a flat reward rate, or another structure based on
@@ -31,8 +34,7 @@ rewards calculation per Operator by the AVS.
3134

3235
Each rewards submission specifies:
3336

34-
* Time range for which the rewards submission is valid. Rewards submissions can be retroactive from the [M2 upgrade](https://github.com/Layr-Labs/eigenlayer-contracts/releases/tag/v0.2.3-mainnet-m2)
35-
and last up to 30 days in the future.
37+
* Time range for which the rewards submission is valid.
3638
* List of strategies and multipliers that enables the AVS to weigh the relative payout to each strategy within a single rewards submission.
3739
* ERC20 token in which rewards should be denominated.
3840

0 commit comments

Comments
 (0)