55 releases (5 stable)

1.1.2 Nov 23, 2023
1.1.0 Jun 19, 2023
1.0.1 Dec 19, 2022
1.0.0 Nov 29, 2022
0.3.2 Oct 28, 2020

#1443 in Magic Beans

Download history 13130/week @ 2023-08-17 13052/week @ 2023-08-24 13378/week @ 2023-08-31 13359/week @ 2023-09-07 13487/week @ 2023-09-14 8048/week @ 2023-09-21 9413/week @ 2023-09-28 8421/week @ 2023-10-05 12026/week @ 2023-10-12 13713/week @ 2023-10-19 11333/week @ 2023-10-26 13524/week @ 2023-11-02 12841/week @ 2023-11-09 11928/week @ 2023-11-16 15277/week @ 2023-11-23 10122/week @ 2023-11-30

52,564 downloads per month
Used in 354 crates (224 directly)


202 lines

CW2 Spec: Contract Info

Most of the CW* specs are focused on the public interfaces of the contract. The APIs used for ExecuteMsg or QueryMsg. However, when we wish to migrate or inspect smart contract info, we need some form of smart contract information embedded on state.

This is where CW2 comes in. It specifies a special Item to be stored on disk by all contracts on instantiate.

ContractInfo must be stored under the "contract_info" key which translates to "636F6E74726163745F696E666F" in hex format. Since the state is well defined, we do not need to support any "smart queries". We do provide a helper to construct a "raw query" to read the ContractInfo of any CW2-compliant contract.

You can query using:

wasmd query wasm contract-state raw [contract_addr] 636F6E74726163745F696E666F --node $RPC

When the migrate function is called, then the new contract can read that data and see if this is an expected contract we can migrate from. And also contain extra version information if we support multiple migrate paths. This crate provides an ensure_from_older_version helper that handles this.

Data structures


All CW2-compliant contracts must store the following data:

  • key: contract_info
  • data: Json-serialized ContractVersion
pub struct ContractVersion {
    /// contract is a globally unique identifier for the contract.
    /// it should build off standard namespacing for whichever language it is in,
    /// and prefix it with the registry we use.
    /// For rust we prefix with `crates.io:`, to give us eg. `crates.io:cw20-base`
    pub contract: String,
    /// version is any string that this implementation knows. It may be simple counter "1", "2".
    /// or semantic version on release tags "v0.7.0", or some custom feature flag list.
    /// the only code that needs to understand the version parsing is code that knows how to
    /// migrate from the given contract (and is tied to it's implementation somehow)
    pub version: String,

Thus, an serialized example may looks like:

    "contract": "crates.io:cw20-base",
    "version": "v0.1.0"


~116K SLoC