Storage-layout collision risk across upgrades
Liquid Collective (LsETH)'s assessment for RD-F-142 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Protocol uses custom library-slot based storage (LibRiver, LibAllowlist etc.) rather than sequential struct storage — this architecture is inherently resistant to storage layout collisions across upgrades. Multiple Spearbit audits (Jul 2023, Oct 2023) and Certora (Nov 2024) reviewed the upgrade path. No storage collision finding surfaces in public audit summaries. Custom slot pattern is the industry standard collision-avoidance approach.
Sources #
- AuditSpearbit Jul 2023 — reviewed upgrade pathSpearbit Jul 2023 — PR 222 review including upgrade safetyretrieved 2026-05-17
- Certora Nov 2024 — no storage collision findingCertora Nov 2024 — formal verification covering storage accountingretrieved 2026-05-17
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 →