Storage-layout collision risk across upgrades
Rocket Pool's assessment for RD-F-142 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Architectural N/A. Rocket Pool uses a storage-registry pattern (RocketStorage key-value store) rather than EIP-1967 transparent proxies or UUPS. Individual contract replacements do not share storage slots. The traditional storage layout collision problem (OZ upgrades plugin domain) does not apply to this architecture. Each new contract reads/writes RocketStorage keys independently.
Sources #
- GitHubRocketStorage.solRocketStorage.sol: central key-value registry, not EIP-1967 proxy storage slotretrieved 2026-05-04
Methodology #
Determine whether the OZ upgrades-plugin or manual review flags a storage-layout collision risk between implementation versions.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol rocket-pool factor RD-F-142 score gray collected_at 2026-05-04 15:40:28