The battle for Ethereum staking control

The scale of liquid staking and restaking

Ethereum staking reached its highest monthly level in October. This growth follows the 34% solo staker node growth seen this month. Lido manages approximately 4,600,000 ETH using stETH as its liquid token. Rocket Pool manages about 360,000 ETH using rETH. StakeWise handles 83,000 ETH, where rewards accrue in a separate rETH2 token. EigenLayer holds $11 billion in deposits and provides a platform where protocols piggyback on Ethereum security. You should notice how the gap between these protocols widens as liquid staking becomes the preferred method for users. Lido applies a 10% fee on all rewards, splitting it between node operators, the Lido DAO, and a coverage fund. Rocket Pool requires 16 ETH and 16 ETH worth of RPL for validators. Rocket Pool charges between 5% and 20% in fees, though it recently set a 15% fee. StakeWise charges a 10% fee.

Lido’s transition to modular validators

Lido’s Curated Module v2 introduces 0x02 validator support to handle validator consolidations. This migration moves 265,000 existing validators to new credentials. The migration of 265,000 existing validators to 0x02 Withdrawal Credentials will reduce the total Ethereum validator count from 880,000 to 628,000, which helps lower network congestion and attestation messages. This process reduces attestation messages by 29% each epoch. The Community Staking Module (CSM) provides a permissionless avenue for participation. CSM secures 770,000 staked ETH across 335 active operators, which accounts for 1.9% of the total network stake. Identified DVT Clusters (IDVTC) allow community stakers to run distributed validators via Obol or SSV. These clusters require a bond of 0.5 to 1.5 ETH per key. IDVTC provides capital efficiency up to 3.1x compared to solo staking. Curated Module v2 also introduces operator classification for Decentralization Operators, Extra Effort Operators, and Public Good Operators. Decentralization Operators run Ethereum nodes across underrepresented geographies and diverse infrastructure. Extra Effort Operators contribute through service roles like the Lido Oracle or governance. Public Good Operators maintain core Ethereum client software.

Security risks in the EigenLayer ecosystem

Sreeram Kannan built EigenLayer to allow custom layers with shared security. The protocol allows users to restake ETH for additional slashing risk. Critics argue that the reliance on a single batch of Ether for multiple services could lead to cascading failures. If an application built on EigenLayer fails, the failure could take the restaked Ether with it. Lefteris Karapetsas claims that lucrative relationships between protocols and Ethereum Foundation researchers create conflicts of interest. Justin Drake and Dankrad Feist joined EigenLayer as advisers to solve restaking risks. EigenLayer’s AVS market includes projects like EigenDA, AltLayer, and Lagrange. EigenLayer secured $100 million from a16z. Symbiotic offers permissionless network deployment and multi-asset collateral. Symbiotic reached $1.5 billion in TVL by the first quarter of 2026. Karak holds $850 million in TVL, while Babylon holds $5 billion. Renzo acts as an LRT abstraction layer on top of EigenLayer. Lido’s move toward consolidation and EigenLayer’s search for stability demonstrate a race for Ethereum’s security dominance.

Rocket Pool and the Atlas update

Rocket Pool’s Atlas update implements LEB8s to utilize idle ETH in the minipool queue. This update requires 31 ETH for all minipools in the queue to launch. The protocol uses all remaining ETH to pair against the queue for new minipools. This allows more validators to start than otherwise possible. Existing 16 ETH minipools can migrate to LEB8s immediately. The protocol gives these operators an 8 ETH credit for future minipools. This migration remains one-way. The Atlas update also removes the requirement for total effective RPL stake and the blocker for creating minipools during consensus issues. The update includes a new flexible size queue for LEB8s and future 16 ETH minipools. Existing queues have priority over the flexible queue. This means the existing queues will empty first. The Atlas update scales assignments with deposit size. The number of scaling assignments is the minimum of 90 or the number of minipools that can be assigned using the deposit. The number of socialized assignments is 2. The total number of assignments from a deposit is the minimum of scaling plus socialized assignments or the total queue length. In a node with both 16-ETH minipools and LEB8s, rewards will split the same regardless of which specific minipool got the rewards. Does this shift toward higher minimums favor larger operators at the expense of smaller ones?