Storage-layout collision risk across upgrades

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

Evidence summary #

V4 to V5 upgrade (2025-08-14) renamed state variables (reserve1, reserve2 to buidlTreasury, etc.) without publicly published OZ upgrades-plugin validation. Renaming without reordering is generally safe in proxy storage, but no formal storage layout check output was published. Risk not confirmed but not cleared.

Sources #

GitHub
V5 upgrade commit — variable renames without published storage layout checkCommit 47a77ab: state variable renames (reserve1→buidlTreasury, reserve3→reserve5/depositAmountMap); no OZ upgrades-plugin output publishedretrieved 2026-05-16

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 openeden factor RD-F-142 score yellow collected_at 2026-05-16 10:11:45