RPIP-XXX: 5% RPL Gatekeeper for Megapool Queue Entry
Author: THe-D
Status: Draft
Type: Core
Created: 2026-09-02
Abstract
This proposal introduces a one-time “gatekeeper” requirement for new validators entering the Rocket Pool queue via megapools. Node Operators (NOs) will be required to stake a minimum of 5% of their borrowed ETH in RPL solely at the time of queue entry. Once the validator has successfully passed through the queue and become active, this collateral requirement is lifted, allowing operators to freely withdraw or manage their RPL without ongoing penalties or reward cliffs.
Motivation
Recent tokenomic shifts lowered the barrier to entry by removing strict ongoing RPL bonding requirements. While this successfully drove validator growth, it stripped the RPL token of its baseline utility and demand mechanics.
Mandating a permanent, ongoing bond exposes operators to long-term token price volatility, which has historically been a point of friction. However, allowing completely bondless entry removes all economic friction to utilizing the protocol’s infrastructure.
By implementing a 5% RPL gatekeeper strictly for queue entry, we achieve a middle ground: every new validator generates tangible upfront utility and demand for RPL, without burdening the Node Operator with permanent price exposure or the anxiety of managing collateral ratios to avoid reward cliffs. It ensures skin in the game during the onboarding phase while maintaining the attractive, low-friction appeal of operating a Rocket Pool node long-term.
Specification
The protocol will introduce an initial RPL staking requirement tailored to the current megapool architecture.
-
Queue Entry Gatekeeper (5% Initial Stake):
- Before any new validator can enter the beacon chain queue through a megapool, the operator must stake RPL equivalent to 5% of the borrowed ETH value for that specific validator.
- If appending multiple validators to a megapool, the 5% RPL requirement applies to the aggregate borrowed ETH of the new validators entering the queue.
-
Post-Activation Freedom (No Ongoing Maintenance):
- The 5% threshold is enforced only as a prerequisite for queue entry.
- Once the validator is active on the beacon chain, the 5% threshold is no longer enforced.
- No Reward Cliffs: If the staked RPL drops below 5% due to price fluctuations, or if the operator chooses to withdraw their RPL entirely post-activation, there are zero penalties. The operator will continue to earn their full ETH staking yields, MEV-boost rewards, and any applicable protocol commissions.
- The operator is free to withdraw, hold, or sell the initial RPL stake once the validator is out of the queue.
Rationale
This approach targets the primary pain point of previous tokenomics—ongoing price exposure—while still capturing value for the RPL token. A 5% upfront gatekeeper is a reasonable toll for utilizing the protocol’s liquidity.
Because the requirement is dropped post-queue, operators are not forced into complex, continuous collateral management. This model creates a consistent transactional demand for RPL correlated directly with protocol growth, rather than relying on forced, permanent lockups that deter prospective node operators.
Backwards Compatibility
This proposal introduces no friction for existing operators:
- Existing Validators: Every existing legacy minipool and existing validator within a megapool is completely unaffected. Because the requirement only applies at the moment of queue entry, validators that are already active bypass this entirely.
- No Maintenance Overhead: Since ongoing reward cliffs are not a part of this proposal, no existing operator needs to adjust their current collateral to maintain their status or rewards.
- Expanding Megapools: If an existing operator wishes to add a new validator to their current megapool, they must meet the 5% gatekeeper requirement for the newly borrowed ETH at the time of entry.
Security Considerations
- Capital Cycling / Looping: Because the RPL can be withdrawn post-activation, a well-capitalized operator could theoretically cycle the same RPL stack to spin up multiple validators sequentially. This is considered acceptable within the scope of this proposal, as it inherently rate-limits massive, instant megapool spin-ups and still requires initial market acquisition of the token.
- Smart Contract Execution: Megapool contracts will need to be updated to verify the 5% RPL equivalent at the exact block of queue entry and subsequently unlock that specific collateral requirement upon validator activation.