Lido vs Rocket Pool

Operator Model: Permissioned vs Permissionless

The most fundamental difference between Lido and Rocket Pool is their approach to validator operation. Lido uses a curated, permissioned set of approximately 30 professional node operators selected through governance. These operators are vetted for technical competence, infrastructure quality, and track record. The Lido DAO, governed by LDO token holders, votes on which operators can join the set. This model prioritizes reliability and performance: Lido has maintained near-perfect uptime and minimal slashing incidents precisely because every operator meets a high professional bar.

Rocket Pool, by contrast, is fully permissionless. Anyone with 8 ETH (reduced from 16 ETH with the Atlas upgrade) and a minimum RPL stake can run a minipool validator. There are over 2,800 independent node operators in the Rocket Pool network, making it one of the most decentralized staking protocols in existence. This permissionless design means no single entity or small committee can censor validators or extract rent from the system. The tradeoff is that individual node operators may have less sophisticated infrastructure than Lido's professional operators, though Rocket Pool's penalty system and RPL collateral requirements help mitigate poor performance.

Client Diversity

Client diversity is critical for Ethereum's resilience. If a supermajority of validators run the same execution or consensus client, a bug in that client could cause mass slashing or a chain split. Lido has made significant efforts to improve client diversity among its operator set, mandating that no single client exceed 33% of Lido validators. As of early 2025, Lido's operator set runs a mix of Lighthouse, Teku, Prysm, Lodestar, and Nimbus consensus clients, and Geth, Nethermind, Besu, and Erigon execution clients.

Rocket Pool's client diversity is naturally better due to its permissionless nature. With thousands of independent operators choosing their own clients, the distribution tends to be more organic and spread across available options. The Rocket Pool community actively encourages minority client usage, and the protocol's Smartnode software makes it straightforward to run any client combination. However, Rocket Pool cannot enforce client diversity the way Lido can mandate it among its curated set, so individual operator choices still matter.

Governance and Protocol Control

Lido governance operates through the LDO token. LDO holders vote on critical protocol decisions including operator additions and removals, fee structure changes, treasury allocation, and protocol upgrades. The Lido DAO controls a substantial treasury and the protocol's multisig. Critics point out that LDO governance is relatively concentrated among a small number of large holders, and that the DAO's power over operator selection creates a form of centralization in the staking layer. The Lido community has been working on "dual governance" proposals that would give stETH holders veto power over LDO governance decisions.

Rocket Pool's governance is tied to the RPL token, but the protocol is designed to minimize governance surface area. Node operators must stake RPL as collateral (minimum 10% of their ETH value), which aligns their incentives with protocol health. The Oracle DAO, a group of trusted entities, provides price feeds and handles certain protocol functions, representing a centralization vector that the Rocket Pool team has been working to reduce. The protocol's smart contracts are designed to be more autonomous, with fewer parameters subject to governance changes compared to Lido.

Systemic Risk to Ethereum

Lido's dominance raises important questions about Ethereum's decentralization. With over 30% of all staked ETH, Lido is approaching the critical 33% threshold beyond which a single entity could theoretically delay finality. While Lido is not a monolithic entity (its validators are distributed across 30 operators), the DAO's governance over operator selection and the protocol's unified withdrawal credentials mean that LDO governance decisions could affect a massive portion of Ethereum's validator set. This concentration risk has led to vigorous debate in the Ethereum community, with some researchers advocating for self-limiting mechanisms.

Rocket Pool, by design, contributes to Ethereum's decentralization rather than threatening it. By enabling permissionless node operation with only 8 ETH, Rocket Pool lowers the barrier to running validators and distributes staking power across thousands of independent operators. Even if Rocket Pool grew to match Lido's TVL, its permissionless structure would mean that power remains distributed among individual operators rather than concentrated in a governance-controlled set. This makes Rocket Pool philosophically more aligned with Ethereum's decentralization ethos.

Slashing Protection

Both protocols have mechanisms to protect stakers from slashing losses, but they work differently. Lido maintains a slashing insurance fund and has historically covered any slashing penalties so that stETH holders experience no loss. The Lido DAO can also penalize underperforming operators by reducing their share of fees. Lido's professional operators use sophisticated anti-slashing infrastructure including redundant key management and slashing protection databases.

Rocket Pool requires each node operator to post RPL collateral worth at least 10% of their borrowed ETH. If a minipool validator is slashed, the penalty comes first from the node operator's ETH bond, then from their RPL collateral, before any rETH holder funds are affected. This economic alignment means that node operators bear the primary risk of their own operational failures, creating strong incentives for proper setup and maintenance. The RPL collateral requirement also ensures that bad actors cannot cheaply attack the network.