Contract Migration

Optionally perform code and state migrations of Secret Network smart contracts

In some cases, for example when wanting to deliver support to users and deploy bug fixes, it makes sense to have the ability to change the code. This is especially true for services which wish to change algorithms, add features, etc. For these use cases, contracts can be written to allow various modes of migration. Doing so means that anyone inspecting the source code will be able to know that such a migration is possible and will require that users have a higher level of trust in the contract administrators, as they can effectively install a backdoor in their product.

Secret used to not support the native CosmWasm implementation of contract migratability, since v1.11 it does. The old manual examples are still displayed here as a reference.

During the v1.11 upgrade a set of old contracts were allowed to become migrateable, these contracts behave slightly different in that they are callable by both their new and old code hash. For more information about the transition period please read this forum post!

Last updated