Storage-layout collision risk across upgrades

Babylon Protocol'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 uses module-keyed key/value store (IAVL tree), not EIP-1967 proxy storage slots. No Solidity storage layouts or slot assignment conflicts exist. Module upgrades use Cosmos SDK RegisterMigration and ConsensusVersion patterns, not EVM storage slot migration. The EVM storage-layout collision risk class is architecturally absent.

Sources #

GitHub
Babylon Genesis — Custom Modules (Cosmos SDK architecture)Cosmos SDK IAVL store — no EIP-1967 proxy storage slots; module-keyed KV storeretrieved 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 →

rubric_version v1.7.0 protocol babylon-protocol factor RD-F-142 score not_applicable collected_at 2026-05-04 19:43:27