Skip to content

Conversation

@0xrajath
Copy link
Collaborator

Motivation:

We need to support Rewards v2.2 :

  • Rewards that are linear to allocated unique stake.
  • Needs to be both retroactive and future-looking

Modifications:

Updates in RewardsCoordinator:

  • New createOperatorSetRewardsSubmission function with OperatorSetRewardsSubmissionCreated event emission
  • New PAUSED_OPERATOR_SET_REWARDS_SUBMISSION constant
  • New isOperatorSetRewardsSubmissionHash mapping
  • Updated storage gap to 34 slots (from 35 slots)

Result:

Support for Rewards v2.2

@0xrajath 0xrajath self-assigned this Oct 21, 2025
OperatorSet calldata operatorSet,
RewardsSubmission[] calldata rewardsSubmissions
) external onlyWhenNotPaused(PAUSED_OPERATOR_SET_REWARDS_SUBMISSION) checkCanCall(operatorSet.avs) nonReentrant {
require(allocationManager.isOperatorSet(operatorSet), InvalidOperatorSet());
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving a note that we should check if it has allocated stake to that operator set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants