Role separation: upgrade ≠ fee ≠ oracle

Rocket Pool's assessment for RD-F-035 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Role separation: post-Oct 2025, guardian role no longer overlaps domains. Upgrade role: pDAO governance approves; oDAO registers into RocketStorage. Fee/reward settings: pDAO governance via RocketDAOProtocolProposals. Oracle (rETH rate, RPL price): oDAO via RocketNetworkBalances + RocketNetworkPrices. The remaining role-separation gap: oDAO holds BOTH upgrade-execution power (RocketStorage registration) AND oracle submission power. Upgrade != oracle is NOT cleanly satisfied at the oDAO level. Yellow because two of three role separations hold (upgrade != fee, fee != oracle) but oDAO still conflates upgrade-execution + oracle reporting.

Sources #

URL
https://notonlyowner.com/articles/permissions-of-a-permissionless-staking-pool/retrieved 2026-05-06
Docs
Oracle DAO OverviewRocketDAONodeTrusted (oDAO) — 18 members, 51% quorumretrieved 2026-05-04

Methodology #

Determine whether the upgrade role, fee-collection role, and oracle-config role are assigned to distinct addresses.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol rocket-pool factor RD-F-035 score yellow collected_at 2026-05-04 15:40:28