Storage-layout collision risk across upgrades
Symbiotic'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 #
Core contracts (OperatorRegistry, NetworkRegistry, DefaultCollateral) are non-upgradeable — storage layout collision is structurally impossible. For MigratablesFactory-managed vaults using migration pattern, factory owner controls whitelisted implementations; storage layout compatibility is the factory owner's responsibility. No storage collision flagged in any of the 6 audits.
Sources #
- GitHubMigratablesFactory.sol — Implementation Whitelist ControlMigratablesFactory.sol — whitelist() only adds implementations owner-approved; storage compatibility is precondition for whitelistingretrieved 2026-05-16
- Symbiotic Core Audits — No Storage Collision FindingAudit directory — 6 firms reviewed core contracts; no storage collision finding 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 symbiotic factor RD-F-142 score green collected_at 2026-05-16 09:25:24