eigen layer pays restakers for the security their delegated stake provides to paying Actively Validated Services (AVSs), but a reward becomes claimable only after its allocation is calculated offchain and included in an active onchain distribution root. If you see a pending amount, you may have earned a share that cannot yet be claimed. The payment, your operator’s cut, and the root’s timing determine what reaches your wallet.
AVS Rewards Pay for Delegated Security
An AVS pays for security supplied by operators and the stake delegated to them during a reward period. It submits a payment for eligible operators and restakers; simply holding restaked ETH or a liquid staking token does not create an AVS reward. An operator must serve an AVS that actually pays for the relevant period.
A pending figure in EigenLayer can look like a return on your entire restaked balance. For eigen layer rewards, the deciding question is whether your operator served a paying AVS while your stake was eligible. If it served no paying AVS, there is no AVS payment to allocate to you, even though your delegation remains in place.
The protocol team’s whitepaper, EigenLayer: The Restaking Collective, describes AVSs paying restakers for pooled security. That explains what the payment is for; it does not establish that any particular AVS paid your operator in a given period. Ethereum Beacon Chain consensus rewards are a separate stream. A native validator receives them through Beacon Chain accounting, while a liquid staking token may reflect them in its value or balance. Neither should be expected in an AVS claim.
How eigen layer Rewards Become Claimable
An AVS payment becomes claimable through a reward submission, an offchain calculation, and an onchain Merkle root. A submission identifies the reward token and period, along with the stake or operators eligible for that payment. The token is an ERC-20 chosen by the AVS. It need not be ETH or EIGEN, so an unfamiliar token in your rewards view may be the intended payment asset.
The calculation attributes the payment using the applicable stake weights and the operator’s reward split. The operator keeps its specified cut; delegated restakers divide the remainder according to their eligible stake. Your share therefore depends on more than the amount you deposited. The AVS’s payment, the strategies it rewards, your stake during the period, and your operator’s split all matter. Some reward types use total delegated shares; others can use stake allocated to an operator set.
The rewards updater periodically combines calculated earnings into a Merkle tree and posts its root to the RewardsCoordinator contract. A Merkle proof then lets the contract verify your allocation when you claim. Roots record cumulative earnings by token, so a later active root includes previously unclaimed amounts. You do not need a transaction for every reward period.
Why Do Pending and Claimable Amounts Differ?
Pending rewards can be attributed to you before an active root permits a claim. Claimable rewards have passed that onchain step. The gap is normal when an AVS has paid for a period but the next calculation and root have not been posted, or when a posted root is still in its activation delay.
- No AVS payment: There is no AVS reward to claim for that operator and period.
- Payment awaiting an active root: An expected or pending share may appear, but a claim cannot yet use it.
- Active root: Your unclaimed allocation for its included tokens can be claimed.
These states are different from a smaller allocation. If the root is active but the amount is below your estimate, compare the AVS’s eligible period and stake weights with your delegation history, then account for the operator’s cut. Also compare amounts token by token: a payment in an AVS token will not appear as additional ETH. The RewardsCoordinator documentation describes root posting, activation, and Merkle proof claims, which is why a display estimate alone is not proof that funds are available now.
How Do You Claim the Available Rewards?
Claim the available amount with the wallet that earned it. Open the protocol’s rewards interface on Ethereum, connect that wallet, review each claimable token and the recipient address, then approve the claim transaction and its gas cost. The interface supplies the proof used by RewardsCoordinator to verify your earnings. If you previously designated another address as your claimer, that address must submit the transaction and can specify the recipient, so confirm the destination before it signs.
After confirmation, the contract transfers the difference between the root’s cumulative earnings and what you have already claimed for each selected token. Your wallet may need the token displayed before the new balance is obvious; the confirmed claim transaction and token transfer show what arrived. If a later payment is still pending, wait for a new active root and claim the newly available difference.
You can judge a shortfall by separating an unpaid AVS period, an allocation reduced by eligibility or the operator’s cut, and an earned amount still waiting for an active root.
Top comments (0)