Storage-layout collision risk across upgrades
Sanctum'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 #
Solana BPFLoaderUpgradeable replaces entire program bytecode; data accounts are separately managed via Anchor discriminators. EVM-style storage slot collision does not apply. The primary risk is data migration when account schemas change across upgrades — relevant for the V1-to-V2 Infinity migration. Not fully assessable from public evidence. Yellow (low confidence, potential risk but not confirmed).
Sources #
- DocsSolana program model documentationAnchor framework documentation: account discriminators and data account separation; Solana BPFLoaderUpgradeable specretrieved 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 →