Storage-layout collision risk across upgrades

Centrifuge'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 #

Centrifuge V3 uses immutable-core architecture with no proxy for core contracts (Root, Gateway, PoolManager, InvestmentManager are all deployed as non-upgradeable monolith contracts). Storage layout collision risk is definitionally N/A. The ward-based upgrade pattern (deploy new contract, re-wire ward permissions) avoids storage layout collision by design.

Sources #

Etherscan
https://etherscan.io/address/0x0C1fDfd6a1331a875EA013F3897fc8a76ada5DfCretrieved 2026-04-28
URL
https://docs.centrifuge.io/developer/protocol/overview/retrieved 2026-04-28
Etherscan
https://etherscan.io/address/0x09ab10a9c3E6Eac1d18270a2322B6113F4C7f5E8retrieved 2026-04-28

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 centrifuge factor RD-F-142 score green collected_at 2026-04-30 21:19:10