The control finding
Rocket Pool staked ETH. Permissionless validator set across 3,000+ independent operators — the most decentralised liquid staking option. Reward-bearing: your balance stays constant while its ETH value grows.
- Named controller
- No token-freeze administrator; Rocket Pool protocol governance
- Holder’s position
- rETH represents a claim on ETH staked across Rocket Pool's permissionless validator set, spanning more than 3,000 independent node operators, the most decentralized liquid staking option available.
- Redemption or exit
- Holders burn rETH through the Rocket Pool contracts for ETH, subject to available deposit-pool or withdrawal liquidity, or sell rETH on a market instead.
Dependencies an advisor should record
- Rocket Pool protocol governance
- The distributed node operator set and its slashing exposure
- Deposit pool and withdrawal liquidity at exit time
- Ethereum consensus and validator exit mechanics
- Any wrapper, bridge, or protocol built on rETH
Why this distinction matters
rETH is reward-bearing, so the balance an advisor records today understates the ETH claim over time; the exchange rate, not the token count, carries the growth. Its operator decentralization is itself a control fact worth recording alongside the freeze answer.
No single issuer or administrator has an address-level freeze function at this layer. That finding can coexist with a sound reserve, useful product, or appropriate client role. The grade prevents the on-chain wrapper from being mistaken for the absence of an administrator.
Questions before use
- Does the exact contract and chain match the instrument reviewed here?
- Which party can mint, burn, pause, upgrade, block, or redeem?
- Does the client have direct redemption access or only secondary liquidity?
- What protocol, bridge, wallet, and custodian dependencies are added?
- Which event would force review or exit?
Primary sources
Primary documents can change. This profile records the control interpretation reviewed on 2026-08-06; verify current terms before implementation.