This note explains how UnderwriterAVS and ValidatorAVS cooperate to produce operator-directed rewards using EigenLayer's RewardsCoordinator.
See the sequence diagram below and the implementation pointers.
sequenceDiagram
actor Initiator as Reward Initiator
participant Underwriter as UnderwriterAVS
participant Validator as ValidatorAVS
participant Rewards as RewardsCoordinator
participant Operator as Operators / Stakers
Initiator->>Underwriter: createOperatorDirectedAVSRewardsSubmission()
Underwriter->>Rewards: createOperatorDirectedAVSRewardsSubmission() (underwriter portion)
Underwriter->>Validator: handleValidatorRewards(validator portion)
Validator->>Rewards: createOperatorDirectedAVSRewardsSubmission()
Rewards-->>Operator: Merkle root for claiming
- Underwriter:
UnderwriterAVS.sol→_createOperatorDirectedAVSRewardsSubmission_handleUnderwriterSubmission
- Validator:
ValidatorAVS.sol→handleValidatorRewards
- Underwriter receives
1000tokens. Suppose it allocates700to its own operators and forwards300to ValidatorAVS. - ValidatorAVS splits the
300among validator operators pro-rata by validator count.
Reward calculation happens on-chain so anyone can trigger distribution without special permissions.