Network Upgrade to v2.0.0
General Information
IMPORTANT!
Version v2.0.0 introduces consensus-breaking changes. The upgrade will be performed via a governance software upgrade proposal with a specified block height, after all validators have prepared the new node version.
Before the upgrade block is reached, do not restart your node.
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,feegrantRequires 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
Download Links
Upgrade Procedure
Download the new binary and place it next to the old one
Install
libwasmvm.x86_64.soon your systemWait until the network halts at the upgrade block height
Start the node using the new binary
Important: Do not start the new binary before the upgrade block is reached.
Upgrade Using Cosmovisor
Important: If you are using Cosmovisor, do not restart the node manually β Cosmovisor will handle the upgrade automatically at the upgrade height.
Environment Variable (Recommended)
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
libwasmvmversionsContact the core team or validator support channels
Last updated
