Network Upgrade to v2.0.0

General Information


What’s New in v2.0.0 (Short Overview)

  • Added CosmWasm module (x/wasm)

  • Added Authz and Feegrant modules

  • Introduced new KV-stores: wasm, authz, feegrant

  • Requires libwasmvm version 1.5

  • Upgrade is performed as an in-place software upgrade


Upgrade Options

Choose the appropriate section depending on how your node is deployed:

  • Upgrade using a custom or manually downloaded binary

  • Upgrade using Cosmovisor


Upgrade Using a Custom or Manually Downloaded Binary

Requirements

  • Node binary v2.0.0

  • libwasmvm version 1.5

Upgrade Procedure

  1. Download the new binary and place it next to the old one

  2. Install libwasmvm.x86_64.so on your system

  3. Wait until the network halts at the upgrade block height

  4. Start the node using the new binary


Upgrade Using Cosmovisor


Verify that the variable is set correctly:


Step-by-Step Instructions

1. Create the Upgrade Directory


2. Download the v2.0.0 Binary

Set executable permissions:


3. Install libwasmvm (Required)


4. Verify Versions

Check node version:

Expected output:

Check wasmvm version:


5. Fix Directory Ownership if needed


After the Upgrade

Once the upgrade block height is reached:

  • Cosmovisor will automatically switch to the new binary

  • The node will continue running without manual intervention

  • No additional actions are required from validators

Recommended checks after upgrade:

  • Node logs

  • Chain synchronization

  • Validator participation in consensus

  • RPC / gRPC responsiveness


Common Issues

  • ❌ Missing libwasmvm β†’ node fails to start after upgrade

  • ❌ Incorrect binary version β†’ upgrade application error

  • ❌ Wrong directory permissions β†’ Cosmovisor cannot switch binaries


Support

If you encounter issues during the upgrade:

  • Ensure all steps were completed before the upgrade block

  • Double-check binary and libwasmvm versions

  • Contact the core team or validator support channels

Last updated