Lido Staking Router v3 Proposal Targets Large Validators

4th June 2026. Lido core contributors have proposed Lido Staking Router v3. It is a foundational upgrade that would bring Ethereum’s new large validators to the protocol’s core. They published the proposal, known as LIP-35, on the Lido governance forum on June 3, 2026. The official Lido account announced it the next day.

The plan is still at the review stage, so nothing is final yet. No Snapshot vote has happened, and no new contracts are live. Still, the proposal sets out a clear path toward Ethereum’s Pectra era of staking.

What Lido Staking Router v3 Changes

The Staking Router sits at the center of Lido. It routes new ETH deposits across staking modules, and it tracks rewards and fees. Today it counts validators in fixed units, because each validator holds exactly 32 ETH.

That model breaks under Ethereum’s new rules. So Lido Staking Router v3 switches to balance-based accounting. Instead of counting validators, the router tracks the actual ETH balance behind each one.

This shift prepares Lido for Ethereum’s Pectra upgrade and for EIP-7251. That change raises the maximum effective balance a validator can hold. As a result, the old 32 ETH ceiling no longer applies.

Large Validators and the 2048 ETH Cap

Under EIP-7251, a single validator can hold up to 2048 ETH. That is 64 times the old limit. So one large validator can earn up to 64 times the rewards of a 32 ETH validator.

To support this, Lido Staking Router v3 introduces new deposit flows. The proposal describes a pull model plus a TopUpGateway. Together they let the protocol top up larger validators over time, rather than sending a fixed 32 ETH at once.

These top-ups are not blind, though. Each one is gated by on-chain Merkle proofs of consensus-layer state. In other words, the protocol verifies the validator’s real balance before it adds more ETH. Each module will also support only one key type, either the older 0x01 keys or the new 0x02 keys.

Moving Stake With Consolidations

Large validators also require a way to move existing stake. For that, the proposal adds a consolidation pipeline. It migrates stake from Curated Module v1, which uses 0x01 keys, to Curated Module v2, which uses 0x02 keys.

The pipeline is delayed and proof-verified, and anyone can execute it once a motion passes. It runs through an Easy Track motion into a set of consolidation contracts. Because the flow relies on EIP-7251 consolidations, validators merge their balances instead of exiting and redepositing.

Lido has tested this path on public testnets, according to the proposal. The team frames the design as a safer way to reshape stake without taking validators offline.

Lean Validator Management

The third headline feature targets day-to-day overhead. To address this, Lido Staking Router v3 adds a dedicated Easy Track factory for module settings. As a result, governance can adjust a module’s stake share limit and exit share within pre-set bounds. At the same time, the framework preserves operational guardrails and limits administrative complexity.

A new narrow permission, the staking module share manage role, controls that factory. So the DAO can tune module limits quickly, yet within safe guardrails. The proposal also adds a deposit reserve that protects buffered ETH for deposits and rebalancing.

Balance-based exits round out the set. Since accounting now follows ETH rather than validator counts, exits and rebalancing become balance-aware. As a result, the protocol can manage stake with fewer keys and less manual work.

Why Lido Staking Router v3 Matters

The upgrade arrives while Lido remains the largest player in Ethereum staking. Its share of all staked ETH sits at roughly 22 to 29 percent in recent Dune Analytics data. Lido reports about 8.9 million ETH staked through stETH.

Larger validators could make that base more efficient, because fewer keys mean less overhead for operators and the network. According to DefiLlama, Lido’s total value locked sits near $15.8 billion. The LDO token traded around $0.31 to $0.32 on June 4, with no clear move tied to the proposal yet.

There is a trade-off, though. Bigger validators concentrate more stake behind each key, so a single compromised operator could carry more slashing risk. Lido points to its modular design and proof-verified flows as mitigations. Critics of Lido’s staking share may still watch this closely.

What Happens Next for Lido Staking Router v3

For now, the proposal remains in community review, and the authors have invited feedback from stakeholders. Meanwhile, the four listed authors, Maksim Kuraian, KRogLA, Alexander Kolesnikov, and Anna Mukharram, continue refining the proposal. In addition, audits by Certora, Statemind, Composable Security, and MixBytes are currently underway.

If approved, a Snapshot signaling vote could follow in late June 2026. Afterward, deployment is tentatively targeted for July. Subsequently, a phased migration would run through late 2026, while a full Curated Module v1 sunset is expected around Q1 2027. For additional details, readers can review the complete proposal in the LIP-35 forum post and the accompanying GitHub spec.

None of this is financial advice. Dates and parameters remain tentative until governance votes and audits conclude.