Storage-layout collision risk across upgrades

Veda (BoringVault)'s assessment for RD-F-142 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

BoringVault is non-upgradeable (constructor-based, no proxy). Peripheral contracts replaced via new deployment, not proxy upgrade. Storage layout collision is not a risk in this architecture.

Sources #

GitHub
BoringVault.sol — non-upgradeable architecture confirmedBoringVault.sol: constructor-only init, no proxy pattern, no _disableInitializers, no initialize()retrieved 2026-05-17

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 veda factor RD-F-142 score not_applicable collected_at 2026-05-17 12:41:22