Rocket Pool works by pairing liquid stakers with node operators. Liquid stakers enter through rETH, while node operators create minipools that combine their bonded ETH with ETH from the protocol's deposit pool to form full Ethereum validators. The protocol's smart contracts, node software, and governance rules coordinate how stake is deployed, how rewards are split, and how the system evolves over time.
Two sides of one protocol
Rocket Pool's own protocol introduction describes two main user groups. One side is liquid stakers who want tokenized staking through rETH, and the other side is node operators who run validators and earn commission for providing validator capacity.
That split is the core of how the protocol works. Rocket Pool is not just a token and not just a validator toolkit; it is a system designed to connect those two groups through shared protocol rules.
How validators get created
Rocket Pool node operators create validators through minipools. A minipool takes the operator's bonded ETH and combines it with protocol ETH from the deposit pool to reach the 32 ETH required by Ethereum's validator system.
The node-creation guide makes clear that this process is governed by both Rocket Pool's own deposit queue and Ethereum's Beacon Chain queue. So validator creation depends on protocol liquidity as well as Ethereum's own activation timing.
- The node operator provides the bond.
- The protocol provides the borrowed ETH from pooled stake.
- Together they create a validator on Ethereum.
How liquid staking fits in
On the liquid-staker side, users hold rETH instead of running a validator themselves. Rocket Pool's staking guides explain that rETH is meant to appreciate relative to ETH as staking rewards accrue.
That means the liquid-staker experience is much simpler than operating a validator, but it is still connected to the performance of the underlying Rocket Pool validator set and protocol liquidity.
How the protocol is steered
Rocket Pool is not purely static software. RPIP-5 explains that governance is divided across DAO units with different roles, including broad project governance, protocol parameter and upgrade responsibilities, and oracle-related duties.
In practice, that means Rocket Pool works through both smart-contract mechanics and governance processes. Questions about node economics, queue behavior, redemptions, and upgrades often depend on both.