Ethereum News
Managing RPL collateral and minipool risks in Rocket Pool

The risk of undercollateralization
Node operators face risk when the price of ETH increases against the price of RPL. The protocol requires staking 10% of borrowed ETH as RPL collateral for most minipools. This requirement leads to undercollateralization if the ETH/RPL ratio shifts. Many operators hold rewards in cold wallets as ETH or rETH. These funds do not automatically increase the node’s collateral to prevent such issues. To increase a bond, an operator must execute a bond-increase, which burns 1% of the bond-increase amount from their staked RPL. This action only works if the deposit contract has sufficient capacity. For example, Bob runs a LEB8 and holds 2 ETH in RPL. He holds 4 rETH in a cold wallet, but 4.5 ETH is not enough to spin up another minipool. To get rewards at the next checkpoint, he must swap some rETH for RPL or borrow RPL using rETH as collateral in a Maker vault. Alice faces a similar situation. She swaps 4 rETH for 4.5 ETH and executes a bond-increase on her minipool. Her variable minipool now has a bond of 12.5 ETH and she is staking RPL worth 1.955, which is above the needed 1.95.
Minipool deployment and Saturn 0
The Saturn 0 upgrade changes minipool deployment for solo stakers. This upgrade removes the RPL stake requirement for new minipools, so stakers can deploy with just 8 ETH. RPIP-30 implements a rewards calculation that weights rewards on a curve to favor 8 ETH minipools. This change phases in linearly over five intervals, starting at interval 18 and reaching full effect at interval 23. Additional RPL staked above the minimum results in diminishing returns. ETH-only minipools earn a 5% base commission. Opportunities to increase yield exist through the Dynamic Commission model by joining the Smoothing Pool. Saturn 0 is the first in a series of three planned upgrades. Future upgrades will include protocol fee sharing and lower minimum stake requirements. This upgrade also included a Houston Hotfix and RPL Tokenomics Rework.
| Feature | Specification |
|---|---|
| Minipool Minimum (Saturn 0) | 8 ETH |
| Base Commission (ETH-only) | 5% |
| RPL Collateral Requirement | 10% of borrowed ETH |
| RPIP-30 Reward Weighting | Favors 8 ETH minipools |
| Reward Distribution | Discrete intervals |
Slashing hierarchy and rewards
The slashing hierarchy protects rETH holders from immediate losses. If the validator receives penalties or slashing, the node operator’s ETH bond is penalized first, followed by their RPL collateral, and only if the loss exceeds both amounts does rETH suffer a socialized loss. Node operators contribute a bond of 8 or 16 ETH as well as supplemental RPL collateral. The amount of RPL needed is 10% of the matched ETH. This means a 2.4 ETH match requires 0.24 ETH worth of RPL, while a 1.6 ETH match requires 0.16 ETH worth of RPL. Post-Atlas, commissions for rETH holders trend from 15% toward 14%. ETH-only minipools earn a 5% base commission. Because rETH is a value-accruing token, staking rewards accumulate and the value of the rETH token increases relative to ETH. This mechanism protects the pool from socialized losses during black swan events. Node operators must fund the validator wallet to avoid penalties.
Maintenance and reward timing
Reward distribution relies on the Oracle DAO and trusted nodes. The system uses 14 trusted nodes to provide balance information and manage the oDAO. These nodes submit rewards snapshots and penalties to the protocol. They can also propose, vote on, and cancel proposals. The amount of proposals a trusted node can submit in a given window of time is limited. To execute a proposal, more than 50% of the trusted nodes must vote in favor. These nodes are controlled by EOAs. They also report the total amount of ETH in the Rocket Pool network and the supply of the rETH token. If the Oracle DAO fails to report a rewards checkpoint during one interval, the missed rewards roll into the next one. This delay does not cause a loss of rewards. The number of eligible intervals is the latest block’s timestamp minus the startTime, divided by the intervalTime. The system determines a target Beacon slot and a target Execution block to snapshot state for rewards calculation. The target slot is the first slot after the endTime where the slotTime is greater than the endTime. If that slot was missed, the target slot becomes the previous slot. You should monitor validator performance using tools like Beaconcha.in or BeaconScan. Users may need access to archive nodes if their clients cannot look far back to query the state of both the target slot and the target block. Will future upgrades eventually remove the need for ETH-only minipools to rely on the Smoothing Pool?