Storage-layout collision risk across upgrades

Meteora'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 BPF programs use account data with Anchor discriminator-based layout rather than EVM storage slots. Account data layout breaks between program versions are possible but structurally different from EVM storage-layout collisions. No known instance of account-data layout collision in Meteora program upgrades. Anchor discriminator pattern reduces risk. Yellow for Solana-analog concern rather than confirmed EVM-style collision risk.

Sources #

GitHub
MeteoraAg Audits RepositoryMeteoraAg/audits — no account layout collision findings noted across audit reportsretrieved 2026-05-16
GitHub
DLMM SDK GitHubMeteoraAg/dlmm-sdk — Anchor framework account structureretrieved 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 meteora factor RD-F-142 score yellow collected_at 2026-05-16 10:03:05