★ Immutable oracle address
Rocket Pool's assessment for RD-F-180 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ CRITICAL-CANDIDATE — PD-017 tracked] Rocket Pool does not use any external oracle service (Chainlink, Pyth, UMA, Redstone, etc.) whose address could be marked 'immutable'. The oracle function is the internal oDAO committee system using RocketNetworkBalances.sol and RocketNetworkPrices.sol. Both contracts retrieve all sibling contract addresses dynamically via getContractAddress() from the RocketStorage registry — none are immutable. No external oracle address field exists in any core contract. F180 requires an external oracle to potentially be immutable; Rocket Pool has no external oracle. Score: not_applicable. Flagged per PD-017: F180 [★ CRITICAL-CANDIDATE] is not_applicable for rocket-pool — orchestrator can record zero F180 promotion candidates for this protocol.
Sources #
- GitHubRocketNetworkPrices.sol sourceRocketNetworkPrices.sol: no 'immutable' keyword; all addresses via getContractAddress()retrieved 2026-05-04
- RocketNetworkBalances.sol sourceRocketNetworkBalances.sol: no 'immutable' keyword on oracle address variables; all addresses via getContractAddress()retrieved 2026-05-04
- RocketStorage (Etherscan)Profile §3: RocketStorage dynamic dispatch pattern — all contract addresses registry-resolved, not hardcodedretrieved 2026-05-04
Methodology #
Determine whether any collateral oracle address is marked `immutable` in protocol config with no admin-replaceable adapter wrapper, preventing the protocol from repricing when the upstream asset depegs.
See the full factor methodology and distribution across all protocols →