Features
Styles
Chores
- use neutron's latest main branch and update wasmbindings #73 (Lockwarr)
- bump versions and use neutron release v0.4.0 #73 (Lockwarr)
- update dependencies and use neutron v0.4.1 #73 (Lockwarr)
- bump wasmd, wasmvm for neutron v1.0.0-rc1 #73 (Lockwarr)
- upgrade wasmvm to v1.2.3 #73 (Lockwarr)
Commits
- 63d4045: [scripts]update: Remove contracts_owner account from the deployment logic (Desislava) #74
- 3b334ca: [scripts]fix: Hermes config ws addr (Desislava)
Upgrade instructions
Since we are bumping versions of dependencies with this upgrade, one of it will be the wasmvm which would cause a Wasm module cache issue. It is a known one when upgrading the version of wasmvm. For this reason, once you replace your binary with the new one from the release, you need to delete the Wasm cache directory - <path-to-node>/wasm/wasm/cache/ before you restart with the new binary. Otherwise, the app will panic.
Upgrade the chain by submitting a gov proposal for software upgrade
nolusd tx gov submit-proposal software-upgrade "v0.3.0" --title "Upgrade v0.3.0" --description "lorem ipsum dolorem asterix" --from reserve --upgrade-height <number> --deposit 10000000unls --fees 500unls