Ether.fi eETH versus EigenLayer restaking comparison

Slashing risk myths and eETH

Misconceptions regarding slashing risk persist among Ethereum stakers. One myth claims slashing only targets native operators, but liquid restakers who use eETH still face the risk of loss if the underlying validator fails. Another false belief suggests that slashing happens instantly, yet the protocol applies safety and time delays to all penalties. A third misconception states that slashing undermines security, while the mechanism increases the cost of corruption for attackers. Some think all liquid restaking tokens carry identical risk, but different assets follow different deposit caps and rules. Finally, many believe slashing is random, though it follows specific AVS-defined commitments. While many participants believe that liquid restaking tokens eliminate exposure to penalties, users who stake ETH through Ether.fi to receive eETH still inherit the slashing risks associated with the underlying validator sets. Because the protocol relies on AVS-defined rules, operators must select which services to support based on their technical capability, hardware infrastructure, and specific risk tolerance for potential slashing events. Operators face AVS-specific slashing and operational risk based on the stake they allocate. In the worst case, the AVS determines the penalty and applies it to the operator stake. You should understand that the complexity of managing multiple slashing risks across different AVSs makes this a dangerous game for unobservant stakers.

Rehypothecation and the operator cap

The ecosystem saw massive activity following the second airdrop epoch in September. This epoch, the StakeDrop campaign, distributed 70 million tokens to stakers and operators. Another 10 million tokens went to ecosystem partners like AVSs and liquid staking protocols. The remaining 6 million tokens went to community members. This massive distribution helped drive the 4.2 million ETH rehypothecation. To accommodate the influx, EigenLayer raised the node operator cap to 12,000. This expansion provides more room for infrastructure providers to join the network. The protocol manages limits for liquid staking tokens like stETH, rETH, and cbETH, and when any single LST reaches 100,000 tokens restaked, a global pause triggers. This procedure follows a governance process involving a 10-day timelock and Multisignatory Governance approval. Once approved, the Operations Multisig triggers the action from the timelock contract. The protocol also recently increased the total re-pledge limit for major tokens to 500,000 pieces. Individual limits for some of the nine supported LSTs remain at 200,000 pieces. This tiered approach ensures that no single asset overwhelms the capacity of the network. The 12,000 cap raise allows more operators to participate in the growing market of Actively Validated Services. Native restaking remains uncapped, though it requires users to run their own nodes and requires 32 ETH as a hard requirement.

Comparing eETH and native restaking yields

Comparing returns shows a clear gap between methods. Ether.fi holds over $1.37B in TVL and provides 4% APY for eETH. EigenLayer, which holds over $8B in TVL, provides additional rewards for restakers. Using YieldNest to restake liquid staking tokens provides a 3.6% APR. Combined returns for restaking can reach approximately 7% when adding EigenLayer rewards to a liquid staking position. This combined yield makes restaking an attractive option for those seeking higher returns than standard staking. Origin Ether provides a 3.4% 7-day trailing APY for OETH. This asset remains fully backed by ETH through partnerships with platforms like Curve and Origin’s ARM. YieldNest holds over $100M in TVL and provides extra rewards from EigenLayer Points and AVS baskets. Liquid staking protocols like Lido provide a net rate of around 2.5% annually after protocol fees.

Will the increase in rehypothecated capital eventually dilute the rewards for early stakers?