- Rocket Pool community members concluded voting on the Saturn 2 ballot on Oct. 13, 2026, approving a randomized validator exit mechanism under RPIP-71 to service rETH redemption shortfalls.
- Governance voters overwhelmingly decided by 85.4% to maintain the 4 ETH operator bond requirement, rejecting both a proposed reduction to 1.5 ETH and an increase to 6 ETH.
- Voters deferred RPIP-85 with an 83.4% majority against inclusion, keeping RocketDash as the platform for signaling votes while preparations begin for the full Saturn 2 package ratification.
Decentralized Liquidity Management Under RPIP-71
Following the close of polls on Oct. 13, 2026, the Rocket Pool community established key structural parameters for its upcoming Saturn 2 upgrade package, according to data from RocketDash tracking shares of voting power cast. A central component of the ballot, RPIP-71, introduces an in-protocol withdrawal queue for rETH holders. Under this mechanism, users depositing rETH into the queue will no longer accrue staking rewards, and queued requests become irreversible once submitted. Incoming ETH from newly minted rETH will be utilized first to service these withdrawal demands, while protocol-directed validator exits will be leveraged to cover larger liquidity deficits.
The operational framework for RPIP-71 initially targets legacy minipools to generate exit liquidity, with Rocket Pool’s oracle DAO handling selection alongside an official recommendation to prioritize pools with higher commission rates. A subsequent governance-activated phase will extend these liquidity exits to megapools, which consolidate individual node operators’ validators into grouped contracts. Through an instant-runoff voting process, participants selected a random selection model by 59.2% of voting power in the final round. This framework ensures that every eligible megapool validator faces an equal probability of exit selection, regardless of top-tier performance. To compensate affected node runners, operators forced to exit validators for protocol liquidity will receive priority reentry tickets, granting them expedited positioning in the deposit queue once ETH demand rebounds.
Staker Bond Allocations Maintained at 4 ETH
Voters also delivered a decisive verdict regarding node operator capital efficiency, with 85.4% of cast voting power favoring the retention of the existing 4 ETH bond requirement per 32 ETH validator. This decision effectively sets aside the provisions of RPIP-42, which had outlined a pathway to reduce operator bonds to 1.5 ETH for any validators deployed past an operator’s initial two. Concurrently, the community declined an alternative proposal seeking to elevate operator bonds to 6 ETH alongside a mandate using operator staking rewards to top up bonding thresholds.
The sentiment surrounding stability was echoed by Rocket Pool leadership during the governance deliberations. Rocket Pool general manager Darren Langley wrote in his bond ballot that increasing the bond to 6 $ETH feels too disruptive.
By settling on the 4 ETH baseline, governance participants averted potential disruption, keeping baseline capital entry requirements intact for both new and established node runners across the network.
Signaling Infrastructure and Saturn 2 Implementation Timeline
The governance round also addressed network signaling frameworks through the RPIP-85 ballot, which saw an 83.4% majority vote against inclusion. The decision delays the rollout of more flexible onchain signaling systems, leaving RocketDash as the recognized venue for non-binding sentiment polling. However, the ballot explicitly keeps RPIP-85 eligible for reconsideration in subsequent protocol upgrades.
With the initial ballot round concluded, core contributors will integrate the finalized outcomes directly into the formal proposal specifications ahead of the comprehensive sentiment-poll and ratification stages for the Saturn 2 release. Per the governance draft of RPIP-71, the rETH withdrawal queue is scheduled to activate 28 days following the deployment of the implementing upgrade, providing node operators an operational grace period to update node software and prepare their systems.
Why This Matters
The Saturn 2 governance decisions define how Rocket Pool balances liquid staking token (LST) liquidity against node operator stability. By formalizing direct rETH-to-ETH redemptions backed by validator exits, the protocol mitigates secondary-market liquidity reliance during steep market discounts. The choice of a randomized exit model inside megapools paired with priority reentry tickets attempts to distribute exit burdens equitably without permanently penalizing high-uptime operators. Furthermore, preserving the 4 ETH bond reflects a conservative capital preservation strategy, prioritizing network collateral stability over the aggressive operator scaling promised by lower bond minimums.
Frequently Asked Questions
How will the new rETH withdrawal queue fund user redemptions?
Under RPIP-71, queued rETH redemptions are filled first by ETH arriving from new rETH minting activity. If mint volume is insufficient to satisfy the queue, the protocol systematically exits validators—first legacy minipools directed by the oracle DAO, and later randomly selected validators from megapools—to liquidate underlying staked assets.
What happens to node operators whose validators are exited for protocol liquidity?
Because the adopted megapool exit model uses random selection, any active validator can be chosen regardless of performance. Node operators subjected to liquidity exits receive priority reentry tickets, permitting them to bypass standard queue wait times and redeploy validators as new ETH deposits enter the protocol.
Why did Rocket Pool decide against lowering or raising the node operator bond?
With 85.4% support, the community opted to preserve the current 4 ETH bond, shelving both RPIP-42’s 1.5 ETH reduction plan and an alternative increase to 6 ETH. Leadership and voters considered an increase too disruptive to existing operator mechanics, opting to preserve current capital obligations for network predictability.
