Rocket Pool Minipool Decentralization Trends

The protocol has permanently disabled the pDAO guardian, transferring complete control to the Protocol DAO after the Houston upgrade delivered a functioning on-chain voting system and an established security council. This structural shift removes the last central point of failure in governance, leaving node operators with direct authority over roadmap decisions. The core team initially comprises the security council, but plans to include community members over time as the infrastructure matures.

Governance and Upgrade Mechanics

Community debate centers on RPIP 47, "Enable Forced Delegate Upgrades," which would allow the protocol to force updated smart contracts on node operators via the smart node software. Critics describe this mechanism as a "back door" that risks installing software capable of closing nodes against operator wishes, effectively acting like malware for those unaware of protocol affairs. The proposal challenges the foundational promise that nobody can force an operator to exit, a guarantee previously upheld through on-chain proof. Proponents argue the protocol must retain the right to use its resources for network benefit, while opponents urge transparency by requiring a distinct smart node version that explicitly warns users about potential forced exits during installation.

This tension highlights a deeper conflict: the protocol’s decentralization narrative relies on permissionless participation, yet operational efficiency demands standardized upgrades. If the community forces migration to megapools by closing old nodes, the risk of regulatory or technical capture increases. Operators who refuse the update will continue using older versions, which will no longer receive significant updates, creating a fragmented ecosystem where compliance is voluntary but economically penalized.

Technical Roadmap and Security Audits

Development priorities shifted toward rETH redemptions and protections ahead of remaining Saturn 2 features following a community alignment session. The team launched Devnet-4, incorporating all Saturn 1 features including the v11 reward tree that delivers voter share to RPL-staking node operators. However, congestion on the Hoodi Ethereum testnet significantly impacted testing, prompting exploration of the Ephemeral testnet and isolated devnet environments. Three independent firms, Sigma Prime, Spearbit/Cantina, and Bailsec, conducted comprehensive reviews of the Saturn 1 codebase. Sigma Prime completed its audit, while Spearbit/Cantina delivered its report and is currently completing fix verification checks. Bailsec provided an interim report, with the core team actively addressing identified issues.

These audits uncovered several significant findings requiring code updates and additional testing, extending the timeline to a target of 19 January 2026. The discoveries substantially strengthen protocol security and robustness, though they delay the deployment of Devnet-5 for final testing. Node operators must factor in RPL price volatility and gas costs for minipool creation when calculating profitability, as the collateral requirement introduces market risk absent in solo staking. The integration of RockSolid vaults and CowSwap provides rETH stakers with MEV-protection and better pricing, yet liquidity depth remains lower than Lido’s stETH. Does the added complexity of managing RPL collateral and validator infrastructure justify the marginal yield advantage over delegating to professional services?