Storage-layout collision risk across upgrades

Yearn Finance'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 #

V3 uses EIP-1167 minimal proxies (create_minimal_proxy_to) with a fixed VAULT_ORIGINAL implementation address. Implementation is never upgraded in-place; new versions use new VaultFactory with new VAULT_ORIGINAL. No storage layout collision risk because existing vault implementation slots are immutable. V2 vaults: fully immutable Vyper, no proxy pattern.

Sources #

GitHub
VaultFactory.vy — yearn-vaults-v3 GitHubVaultFactory.vy: create_minimal_proxy_to(VAULT_ORIGINAL) — VAULT_ORIGINAL is immutable, no in-place impl updateretrieved 2026-05-16
Docs
VaultFactory Docs — Yearn DocsVaultFactory docs — 'factory clones from VAULT_ORIGINAL immutable address'retrieved 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 yearn-finance factor RD-F-142 score green collected_at 2026-05-16 08:34:32