Lido vs Rocket Pool: Two Different Theories on How to Decentralize Ethereum Staking

Liquid staking on Ethereum is dominated by two protocols that took opposite approaches to the same problem. Lido is the largest: it holds roughly a third of all staked ETH, issues a liquid token (stETH) that circulates widely in DeFi, and relies on a curated set of professional node operators selected by governance. Rocket Pool is smaller, more decentralized by design, and requires node operators to put up their own capital as a form of accountability.

The comparison looks simple from the outside — big vs small, centralized vs decentralized. But the actual mechanisms are more interesting than that framing suggests. Both protocols made deliberate tradeoffs, and those tradeoffs determine who they're useful for, what risks they carry, and what would have to change for the picture to shift.

The Shared Problem Both Protocols Solve

To stake ETH natively on Ethereum, a validator needs exactly 32 ETH and the technical infrastructure to keep a node running around the clock. That's a high bar — enough to exclude most participants either by capital requirements or operational complexity.

Liquid staking protocols solve this by pooling ETH from many depositors, running validators on their behalf, and issuing a token that represents the depositor's staked position. That token can then be used in DeFi — as collateral, in liquidity pools, or simply held as a yield-bearing asset. The question both protocols face: who runs those validators, and under what conditions?

How Lido Works

When you deposit ETH into Lido, you receive stETH at a 1:1 ratio. stETH is a rebasing token — your wallet balance adjusts daily to reflect accumulated staking rewards. If you hold 10 stETH and the protocol earns rewards, tomorrow you'll hold 10.05 stETH (or whatever the current rate is). The token tracks the value of staked ETH directly rather than appreciating against it.

Lido doesn't run validators itself. It maintains a curated list of node operators — around 40 professional entities as of early 2026, selected through LDO governance. These operators run the actual validators, hold the validator keys, and receive a portion of staking rewards as compensation. Lido takes a 10% fee on total rewards, split between node operators and the DAO treasury.

Critically, those node operators don't put up their own ETH as collateral. They're trusted by virtue of their reputation, the governance process that selected them, and increasingly, Distributed Validator Technology. Lido's Simple DVT module, launched in 2024 using Obol and SSV Network, distributes validator key management across multiple independent operators — no single entity can sign for a given validator alone. This addresses single-point failure risk at the key level without changing the governance structure above it.

The result is a protocol that scaled fast. Lido holds roughly 9-10 million staked ETH — about 28-32% of all ETH on Ethereum's beacon chain depending on when you're reading this.

How Rocket Pool Works

Rocket Pool's design is structured around a different trust assumption: rather than selecting trusted operators through governance, anyone can join as a node operator. But they have to put up their own capital to do it.

Rocket Pool node operators contribute 8 ETH of their own (reduced from 16 ETH in the April 2023 Atlas upgrade), plus RPL tokens as collateral — a minimum of 10% of the bonded ETH value in RPL. This creates what Rocket Pool calls a minipool: the 8 ETH from the operator combines with 24 ETH from the rETH depositor pool to form a standard 32 ETH validator.

The node operator's stake functions as a buffer. If they behave dishonestly or let their validator get slashed, they lose their own ETH before depositors are affected. It's skin in the game, not reputation — and that's the structural distinction.

Depositors receive rETH rather than stETH. Unlike stETH's rebasing approach, rETH is an exchange-rate token: its value grows relative to ETH over time. If you deposit when rETH is priced at 1.05 ETH per rETH, you receive approximately 0.952 rETH. When you redeem, you get back more ETH than you put in (absent slashing). Different DeFi protocols handle these two token models differently — some prefer rebasing, others prefer exchange-rate — which is why both models have found their niches.

Rocket Pool's total staked ETH sits around 500,000-600,000 ETH at the time of writing. About one-twentieth of Lido's scale.

Where the Constraints Live

Lido's centralization concern is architectural, not behavioral. Ethereum has a specific property: if any single entity controls more than 33% of staked ETH, it could theoretically influence finality under specific adversarial conditions. Lido has stated publicly it wouldn't exercise such influence, and it's taken steps toward operator diversification through DVT. But stated intentions and structural capacity are different things. A governance process selecting 40 validators — regardless of how well-intentioned that governance is — creates a concentration that's worth understanding clearly.

Rocket Pool's binding constraint is different. The RPL collateral requirement means node operators must hold RPL and are exposed to RPL price movements. If RPL falls sharply against ETH, the minimum collateral threshold can be breached, putting nodes in a position where they can't accept new depositor ETH until they add RPL. This has historically slowed Rocket Pool's operator growth relative to protocols with no token requirement for validators. Running a Rocket Pool node means accepting two exposures — ETH staking risk and RPL price risk — where Lido's curated operators only bear the first.

What's Changing

Rocket Pool has a significant upgrade in development: Megapools. Currently, each minipool is its own 8 ETH + RPL construct, which doesn't scale efficiently. Megapools would allow a single node operator to run many validators from a shared collateral position, dramatically improving capital efficiency. The RPL tokenomics model is also under active governance debate — if the collateral requirement changes, the node operator ceiling could expand considerably.

On Lido's side, the Simple DVT module continues to expand. The goal is to grow the effective number of independent key-holders from dozens to hundreds, which addresses operator concentration at the key level even if LDO governance concentration remains. It's a partial answer — but it's a structural one, not just a policy commitment.

At the Ethereum protocol level, EIP-7251 (Maximum Effective Balance) is on the roadmap. It would allow validators to hold more than 32 ETH, reducing operational overhead for large staking operations. Both protocols are affected, but Lido more directly, as its operators would be able to consolidate their validator sets.

What Would Confirm the Current Direction

For Lido: meaningful growth in the Simple DVT operator count — not just dozens of DVT clusters but hundreds — and governance moving to actively cap its own network share. Either of those would represent a real structural shift, not just a stated intention.

For Rocket Pool: Megapools successfully deployed and a measurable increase in total node operators beyond current levels. Sustained rETH/stETH yield parity would indicate the fee premium is justified and the permissionless model is competitive.

What Would Break or Invalidate the Picture

For Lido: a governance attack on the node operator selection process, or Ethereum's core developers moving toward a protocol-level response to concentrated staking. The latter isn't current policy, but it's an active research discussion — if consensus coalesced around a cap, Lido's current architecture would need to change fundamentally.

For Rocket Pool: an RPL collateral crisis triggered by sustained ETH/RPL price divergence, or a slashing event material enough to harm rETH holders. The permissionless model relies on the collateral mechanism absorbing losses; a failure there would damage trust in the model itself.

Timing

Now: The structural difference is live and relevant. Lido offers significantly deeper DeFi liquidity — stETH trading volumes and collateral integrations dwarf rETH's. Rocket Pool offers a demonstrably more decentralized validator set with a different risk profile. Anyone staking ETH through a liquid staking protocol is making this choice implicitly.

Next: Rocket Pool's Megapools deployment and the RPL tokenomics debate are the two variables to watch over the next 12-18 months. Lido's DVT expansion is the corresponding signal. Neither is resolved.

Later: EIP-7251 and any Ethereum-level changes to staking concentration limits. The question of whether Ethereum's protocol layer eventually constrains large staking entities isn't settled — it's under active research.

Boundary Statement

This is a mechanism explanation. It doesn't constitute a recommendation to stake ETH through either protocol, nor does it address the tax treatment of staking rewards or liquid staking tokens in any jurisdiction.

Both protocols function as described. The choice between them depends on factors — yield requirements, DeFi integration needs, trust model preferences, and risk tolerance for RPL exposure — that this post doesn't resolve. The static explanation is here. Tracked signals live elsewhere.