Storage-layout collision risk across upgrades

dYdX v4 (dYdX Chain)'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 #

Not applicable. Cosmos SDK state is stored in IAVL Merkle trees keyed by module prefix bytes — no EVM storage-slot layout, no OpenZeppelin upgrades plugin, no proxy storage collision risk. State migrations for breaking changes use upgrade handlers reviewed as part of governance proposals. N/A by substrate.

Sources #

Docs
Types of Upgrades - dYdX v4dYdX upgrade types documentation — upgrade handlers for Cosmos state migrationretrieved 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 dydx-v4 factor RD-F-142 score not_applicable collected_at 2026-05-17 09:58:47