feat: incentive council + duration vaults release#1740
Merged
0xClandestine merged 31 commits intomainfrom Mar 5, 2026
Merged
Conversation
**Motivation:** We need to support Rewards v2.2 : - Rewards that are linear to allocated unique stake (Needs to be both retroactive and future-looking). - Rewards that are linear to total stake (Needs to be both retroactive and future-looking). TDD: https://www.notion.so/eigen-labs/PRD-Rewards-v2-2-Operator-Set-Rewards-with-Unique-Total-Stake-28513c11c3e080cbb856e41ddc6362f5 **Modifications:** Updates in `RewardsCoordinator`: - New `createUniqueStakeRewardsSubmission` function with `UniqueStakeRewardsSubmissionCreated` event emission - New `PAUSED_UNIQUE_STAKE_REWARDS_SUBMISSION` constant - New `isUniqueStakeRewardsSubmissionHash` mapping - New `createTotalStakeRewardsSubmission` function with `TotalStakeRewardsSubmissionCreated` event emission - New `PAUSED_TOTAL_STAKE_REWARDS_SUBMISSION` constant - New `isTotalStakeRewardsSubmissionHash` mapping - Updated storage gap to 33 slots (from 35 slots) Updated Bindings **Result:** Support for Rewards v2.2
**Motivation:** We need approval on initial design of the upcoming incentives council feature release. Historically, we've used [EigenHopper](https://github.com/Layr-Labs/EigenHopper/tree/master) for token emissions. Now we're looking to make some improvements. **Modifications:** - Drafted a consolidated interface that combines the two `EigenHopper` contracts into a single new contract. **Result:** Single consolidated interface with hopper functionality and proposed ELIP-012 functionality.
**Motivation:** We need to implement the ELIP-012 proposed implementation. **Modifications:** - Adds new `EmissionsController`. **Result:** New contract with owner who sets incentive council, an address privileged with configuring EIGEN emissions.
**Motivation:** We want to add a configurable protocol fee mechanism to the RewardsCoordinator contract to enable revenue generation. This allows reward submitters to opt into paying fees while maintaining backward compatibility with existing integrations. **Modifications:** - Added protocolFee (fixed constant amount) and feeRecipient state variables - Implemented setOptInProtocolFee() for submitters to opt into fee payments - Implemented setFeeRecipient() (owner-only) to set the fee destination address **Result:** Submitters can voluntarily enable protocol fees on their reward distributions. When opted in, the fixed fee amount is deducted and sent to the designated recipient. Existing integrations continue working unchanged since fees are disabled by default.
**Motivation:** This upgrade improves programmatic incentives for the EigenLayer protocol through a new EmissionsController that gives the Incentive Council flexible control over EIGEN token emissions and distribution. It also adds fee functionality to the RewardsCoordinator to support protocol fees. **Modifications:** - Deploy EmissionsController implementation and proxy, plus new RewardsCoordinator implementation with fee support. - Upgrade and initialize EmissionsController proxy. - Upgrade and reinitialize RewardsCoordinator with new feeRecipient parameter. - Register EmissionsController in ProtocolRegistry. - Transfer minting rights from old hopper to EmissionsController. - Complete the upgrade after timelock delay and validate all changes. **Result:** EmissionsController becomes the sole bEIGEN minter, and RewardsCoordinator has opt-in fees. --------- Co-authored-by: Rajath Alex <rajathalex@gmail.com>
**Motivation:** *Explain here the context, and why you're making that change. What is the problem you're trying to solve.* **Modifications:** *Describe the modifications you've done.* **Result:** *After your change, what will change.*
**Motivation:** The `RewardsCoordinator` needs to support a special pathway for EigenDA rewards submissions that can be initiated by the EmissionsController. Currently, all AVS rewards submissions go through the same `createAVSRewardsSubmission` function which doesn't distinguish between different reward submission sources or allow for privileged callers. This creates a need for a dedicated mechanism that allows the EmissionsController to submit EigenDA rewards on behalf of the EigenDA AVS. **Modifications:** - Added `emissionsController` as an immutable storage variable in `RewardsCoordinatorStorage` - Created new `createEigenDARewardsSubmission` function that accepts an AVS address parameter and can only be called by the EmissionsController - Refactored existing `createAVSRewardsSubmission` to use a new internal helper function `_createAVSRewardsSubmission` to avoid code duplication - Updated `EmissionsController` to call `createEigenDARewardsSubmission` instead of `createAVSRewardsSubmission` for EigenDA distribution type **Result:** The `RewardsCoordinator` now has a dedicated pathway for EigenDA rewards submissions from the EmissionsController.
**Motivation:** We need E2E tests to assert the new `EmissionsController` and `RewardsCoordinator` changes work together as expected. **Modifications:** - Improved existing EC integration state checks (which improves every existing test). **Result:** Full E2E coverage of our new changes.
**Motivation:** Address findings from the Certora security audit of the Incentive Council implementation (January 2026). **Modifications:** - **H-01 Fix**: Modified `_createAVSRewardsSubmission` to transfer tokens from `msg.sender` instead of `avs` parameter, ensuring EmissionsController correctly sources funds for EigenDA rewards distributions - **M-02 Fix**: Simplified `_takeProtocolFee` to consistently check `isOptedInForProtocolFee[msg.sender]` across all submission types, removing logic inconsistency in fee opt-in checks - **L-01 Fix**: Standardized `MAX_REWARDS_AMOUNT` validation to check pre-fee amounts in `_validateOperatorDirectedRewardsSubmission`, ensuring consistent 1e38-1 cap enforcement - **I-02 & I-04 Fix**: Updated natspec documentation in `RewardsCoordinatorStorage` and `IRewardsCoordinator` to reference correct function names (createRewardsForAllEarners, createOperatorDirectedOperatorSetRewardsSubmission, createUniqueStakeRewardsSubmission) and current architecture (EmissionsController vs deprecated token hopper) - Enhanced integration tests with improved state checks for comprehensive E2E coverage **Result:** Improved protocol correctness and security.
**Motivation:** Financial AVS's need stake constraints (duration, quantity) in order to use EigenLayer. **Modifications:** A new type of strategy, `DurationVaultStrategy`, that enforces delegate stake caps and duration constraints, and registers as an operator. Also includes modifications to the `StrategyManager` and default strategies, including hooks before shares are added/removed, to accommodate alternative stake models. **Result:** Financial AVS's will have the tools to build on Eigenlayer more easily.
<!--
🚨 ATTENTION! 🚨
This PR template is REQUIRED. PRs not following this format will be
closed without review.
Requirements:
- PR title must follow commit conventions:
https://www.conventionalcommits.org/en/v1.0.0/
- Label your PR with the correct type (e.g., 🐛 Bug, ✨ Enhancement, 🧪
Test, etc.)
- Provide clear and specific details in each section
-->
**Motivation:**
use call instead of try/catch
**Modifications:**
*Describe the modifications you've done.*
**Result:**
*After your change, what will change.*
**Motivation:** *DurationVaultStrategy* documentation **Modifications:** - added durationVaultStrategy documantation **Result:**
**Motivation:** *Explain here the context, and why you're making that change. What is the problem you're trying to solve.* **Modifications:** *Describe the modifications you've done.* **Result:** *After your change, what will change.*
<!--
🚨 ATTENTION! 🚨
This PR template is REQUIRED. PRs not following this format will be
closed without review.
Requirements:
- PR title must follow commit conventions:
https://www.conventionalcommits.org/en/v1.0.0/
- Label your PR with the correct type (e.g., 🐛 Bug, ✨ Enhancement, 🧪
Test, etc.)
- Provide clear and specific details in each section
-->
**Motivation:**
*Explain here the context, and why you're making that change. What is
the problem you're trying to solve.*
**Modifications:**
*Describe the modifications you've done.*
**Result:**
*After your change, what will change.*
**Motivation:** Address findings from the Certora security audit of the Duration Vaults implementation. **Modifications:** ### Medium Severity - **M-01 Fix**: Added `setRewardsClaimer(address claimer)` to designate a claimer for operator-attributed rewards, ensuring if any rewards accrued during split activation delay or via a new rewards type can be claimed - **M-02 Fix**: Implemented retry mechanism in `markMatured()` and `advanceToWithdrawals()` - both now check if vault is in WITHDRAWALS state and re-attempt operator cleanup (`_deallocateAll()` and `_deregisterFromOperatorSet()`) if needed - **M-03 Fix**: Added `updateDelegationApprover(address newDelegationApprover)` calling `DelegationManager.modifyOperatorDetails()` for delegation approver updates - **M-04 Fix**: Same retry mechanism as M-02 allows subsequent calls to complete cleanup if initial call was gas-griefed ### Informational Severity - **I-02 Fix**: Added `DeallocateAttempted(bool success)` and `DeregisterAttempted(bool success)` events for off-chain monitoring - **I-03 Fix**: changed to `DepositExceedsMaxPerDeposit()` error for clearer messaging in `beforeAddShares()` - **I-04 Fix**: Added strategy support check in `lock()` via `AllocationManager.getStrategiesInOperatorSet()`, reverts with `StrategyNotSupportedByOperatorSet()` if unsupported - **I-05 Fix**: Added `@param arbitrator` NatSpec to VaultConfig struct - **I-06 Fix**: Changed `operatorSetRegistered()` to query `AllocationManager.isMemberOfOperatorSet()` directly **Result:** Improved protocol correctness and security for Duration Vaults.
<!--
🚨 ATTENTION! 🚨
This PR template is REQUIRED. PRs not following this format will be
closed without review.
Requirements:
- PR title must follow commit conventions:
https://www.conventionalcommits.org/en/v1.0.0/
- Label your PR with the correct type (e.g., 🐛 Bug, ✨ Enhancement, 🧪
Test, etc.)
- Provide clear and specific details in each section
-->
**Motivation:**
*Explain here the context, and why you're making that change. What is
the problem you're trying to solve.*
**Modifications:**
*Describe the modifications you've done.*
**Result:**
*After your change, what will change.*
**Motivation:** Some environments are failing due to missing Zeus env parameters, and we also want to add default distributions in order to maintain the current emissions schedule as the TokenHopper initially. **Modifications:** - Added missing zeus params. - Added missing check to skip environments that core isn't deployed. **Result:** CI is passing, and default distributions are added.
**Motivation:** Out of date bindings. **Modifications:** Updated bindings. **Result:** Updated bindings.
…o release-dev/v1.12-combined Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # pkg/bindings/RewardsCoordinator/binding.go # script/releases/TestUtils.sol # script/releases/v1.11.0-duration-vault/3-completeUpgrade.s.sol # script/releases/v1.9.0-slashing-ux-destination/1-deployProtocolRegistryProxy.s.sol # src/test/integration/IntegrationDeployer.t.sol # src/test/mocks/RewardsCoordinatorMock.sol
…nto single v1.12 release Delete v1.11.0-duration-vault scripts and fold their deployments/upgrades into the v1.12.0-incentive-council scripts. The combined release goes from 1.9.0 → 1.12.0, deploying Duration Vault strategies alongside the Incentive Council EmissionsController in a single upgrade. Co-authored-by: Cursor <cursoragent@cursor.com>
**Motivation:** *Explain here the context, and why you're making that change. What is the problem you're trying to solve.* **Modifications:** *Describe the modifications you've done.* **Result:** *After your change, what will change.* --------- Co-authored-by: Cursor Bot <michael.muehl@eigenlabs.org>
0xClandestine
changed the title
eigenmikem
approved these changes
Mar 5, 2026
![certora-run[bot]](https://avatars.githubusercontent.com/in/1083145?s=60&v=4){kind=small}
There was a problem hiding this comment.
Verification Results
- Group ID: 1ee0b386-41b2-4593-95e6-bbfbde99c20e
- Commit: 486d005
| Job | Result | VERIFIED | VIOLATED | Link |
|---|---|---|---|---|
| strategies/StrategyBase.conf | ✅ | 2 | 0 | Link |
| pods/EigenPodManagerRules.conf | ✅ | 9 | 0 | Link |
| permissions/Pausable.conf | ✅ | 2 | 0 | Link |
| multichain/OperatorTableUpdater.conf | ✅ | 11 | 0 | Link |
| multichain/KeyRegistrar.conf | ✅ | 13 | 0 | Link |
| multichain/ECDSACertificateVerifier.conf | ✅ | 7 | 0 | Link |
| multichain/CrossChainRegistry.conf | ✅ | 21 | 0 | Link |
| multichain/BN254CertificateVerifier.conf | ✅ | 6 | 0 | Link |
| core/StrategyManager.conf | ❌ | 5 | 1 | Link |
| core/DelegationManagerValidState.conf | ✅ | 11 | 0 | Link |
| core/DelegationManager.conf | ⌛ | 9 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): sumOfPendingDiffCurrentMagnitudeRespectsWAD) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): SetInRegisteredIFFStatusIsTrue) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): registeredSetsInvariant) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): operatorSetsInvariant) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): noZeroKeyInDealocationQ) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): noPositivePendingDiffInDeallocationQ) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): negativePendingDiffAtMostCurrentMagnitude) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeMonotonicallyDecreasing) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeLeqWAD) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeHistoryPastLengthNullified) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeHistoryKeysMonotonicInc) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeHistoryKeysLessThanCurrentBlock) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeGEencumberedMagnitude) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): maxMagnitudeGECurrentMagnitude) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): EndGreaterThenBegin) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): encumberedMagnitudeLeqWAD) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): encumberedMagnitudeEqSumOfCurrentMagnitudesAndPositivePending) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): effectBlockZeroHasNoPendingDiff) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): deallocationQueueEffectBlocLessThanCurrBlockNumberPlushDelayPlusOne) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): deallocationQueueEffectBlockAscendingOrder) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): deallocationQueueDataUniqueness) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): deallocationQueueDataOutOfBoundsAreNullified) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): currentMagnitudeLeqWAD) | ✅ | 2 | 0 | Link |
| core/AllocationManagerValidState.conf (Rule(s): allocatedSetsInvariant) | ✅ | 2 | 0 | Link |
| core/AllocationManagerSanity.conf | ✅ | 2 | 0 | Link |
| core/AllocationManagerOverslashing.conf | ✅ | 4 | 0 | Link |
| core/AllocationManager.conf | ✅ | 4 | 0 | Link |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v1.12.0 Incentive Council (ELIP-012)
Release Manager
@0xClandestine
Overview
Core Features
EmissionsController: Mints EIGEN at a fixed inflation rate per epoch and distributes via gauge weights (bips 0-10,000)
Permissionless Trigger: Anyone can call
pressButton()to process epoch emissions—no trusted keeper required5 Distribution Types:
RewardsForAllEarners— Protocol-wide rewards for all delegated stakeOperatorSetTotalStake— Rewards proportional to total stake in operator setOperatorSetUniqueStake— Rewards proportional to unique stake allocationsEigenDA— Special pathway for EigenDA (pre-OperatorSets AVS)Manual— Off-chain computed distributions sent directly to Incentives CommitteeSilent Failure Handling: Distribution failures don't block other distributions (except reentrancy/OOG attacks)
Protocol Fee Mechanism: Opt-in 20% fee on reward submissions in RewardsCoordinator
setOptInForProtocolFee()Governance & Roles
setIncentiveCouncil()addDistribution(),updateDistribution()sweep()Key Design Points
EMISSIONS_INFLATION_RATEpressButton()andsweep()respectPAUSED_TOKEN_FLOWSflagpressButton()isn't called during an epoch, those emissions are permanently lostChangelog
Scope
New Contracts:
EmissionsController.sol— Main implementationEmissionsControllerStorage.sol— Storage layoutIEmissionsController.sol— InterfaceModified Contracts:
RewardsCoordinator.sol— Added protocol fee mechanism andcreateEigenDARewardsSubmission()RewardsCoordinatorStorage.sol— AddedPROTOCOL_FEE_BIPS,isOptedInForProtocolFee,feeRecipient,emissionsController