How Rocket Pool’s rETH minipool queue works after Saturn I upgrade

The end of the old queue

The Saturn I upgrade, which launched in February 2026, introduced 4 ETH minipools and megapools. This update replaced the three distinct deposit types, including half, full, and empty, which previously sat in separate queues. In the previous design, the minipool queue worked around these three types, and items were dequeued in series. This meant all half minipools were assigned first, and only after all half pools were assigned did the full queue start to receive assignments. I find the old system completely broken because it could not support variable deposit amounts or mixed 16 ETH and 8 ETH pools in one place. RPIP-74 aimed to close the minipool queue by December 08, 2025, to ensure protocol resources go toward megapools instead. This closure protects uninformed node operators from starting less desirable minipools near the Saturn 1 launch. This change helps the protocol handle the massive 4,000 ETH deposit backlog that recently overtook Lido’s node operator waitlist.

The old queue system failed.

Megapools changed everything.

Node mechanics and validator exit

Node operators bond either 8 or 16 ETH to launch a minipool. They must also stake RPL as collateral, which ranges from 10% to 150% of their bonded ETH value. The Saturn I upgrade halved the minimum bond from 8 ETH to 4 ETH. Existing operators use express queue tickets for easier migration. These tickets grant a 4:1 matching advantage over the standard queue. I think the technical command line requirement creates a steep barrier for many. You know that managing a node requires constant attention to detail. Operators can use the CLI to manage validator deposits, such as entering the number of validators they wish to create. They must monitor their node and transactions to avoid a dissolved state if a transaction fails. For a first minipool, the protocol multiplies the number of active minipools by 16 ETH to find the matched ETH value. Node operators earn ETH staking rewards on their bonded ETH and a 14% commission on the rewards from the 16 or 24 ETH supplied by regular stakers.

Node operators who choose to run a 16 ETH minipool earn a 14% commission on the rewards generated from the 16 ETH matched from the staking pool, while 8 ETH nodes find the higher capital efficiency more attractive.

Use command line skills.

Exiting a minipool involves removing the validator from the Beacon Chain and unstaking the 32 ETH. After the validator reaches its withdrawal epoch, the node operator must close the minipool to distribute funds. This process includes a 28-day waiting period for RPL withdrawals following any staking or restaking action.

Staking models and rewards

Lido holds 8.9 million ETH and uses professional operators to manage its validators. Rocket Pool maintains a network of 3,900 independent node operators across 150 geographic regions. While Lido stETH rebases, Rocket Pool rETH remains non-rebasing. The rETH/ETH exchange rate rises as rewards accumulate. I find the lower liquidity for rETH compared to stETH the most disappointing aspect of the protocol. Users can trade rETH on Uniswap or Balancer if the withdrawal buffer of 5,090 ETH runs low. Lido stETH has deeper DeFi integration across over 100 protocols.

The Rocket Pool protocol uses an Oracle DAO and a Protocol DAO to manage network parameters and treasury funds. Node operators receive rewards from the 5% annual inflation of RPL. This distribution gives 70% to node operators, 15% to the Oracle DAO, and 15% to the Protocol DAO treasury. Rocket Pool emphasizes decentralization by dispersing responsibilities across many independent operators. Lido targets consistent results through coordinated professional validators. Does the higher technical requirement of Rocket Pool eventually limit its growth against Lido?