upgrade-stellar-contracts

To upgrade Soroban contracts safely, you apply storage-key safety checks to preserve existing state and use upgradeable derive macros. This ensures cross-version compatibility and prevents data loss during native WASM replacement.

The atomic upgrade-and-migrate pattern uses an Upgrader contract to execute both the WASM replacement and state migration in a single operation. This guarantees that contract upgrades and migrations succeed or fail together without partial execution.

Yes, implementing secure Soroban contract upgrades requires the OpenZeppelin Stellar Soroban upgradeable module. It provides the necessary Upgradeable and UpgradeableMigratable derive macros and foundational logic for native WASM replacement.

You validate Soroban contract upgrade paths by deploying and testing on local testnets or dev networks. This workflow verifies that storage key compatibility and state migrations remain consistent before executing mainnet upgrades.

Upgradeable contracts support direct native WASM replacement, while UpgradeableMigratable contracts add state migration logic. The migratable variant enables atomic upgrade-and-migrate patterns to transform existing storage data safely during the WASM update.

Soroban contract upgrades break existing storage keys when cross-version compatibility is ignored. Applying storage-key safety checks and derive macros prevents data loss by ensuring new contract versions correctly map and preserve prior state structures.