Wasmd 0.43 released
Why Wasmd 0.43?
On the 20th of September, Wasmd 0.42 was released. This release included CosmWasm 1.4.0, along with new features and essential bug fixes. However, just a week later, a critical bug that manifested on a chain upgrade was discovered within CosmWasm 1.4.0. After thorough debugging sessions, the issue was addressed, leading to the release of CosmWasm 1.4.1. See CosmWasm 1.4.1 fixes regression. On September 28th, we were made aware… | by Simon Warta | CosmWasm | Oct 2023 | Medium for more details.
Consequently, CosmWasm 1.4.0 and Wasmd 0.42 were retracted, and on the 10th of October, Wasmd 0.43 was released, introducing the new patch release CosmWasm 1.4.1.
What’s New Since Wasmd 0.41?
The latest release of Wasmd brings several noteworthy updates:
- As mentioned above, CosmWasm 1.4.1 was introduced.
- Cosmos-SDK dependency was upgraded to v0.47.5, which is the latest release for cosmos-sdk 0.47.x
- A new Wasmd extension to the SDK authz module has been introduced, allowing authorities to grant permission to specific addresses for uploading codes to the chain. With this permission, much more fine-grained rules can be applied by specifying a set of code hashes and associated instantiation permissions, or it can be open-ended, utilizing a wildcard approach to grant permission for any code and instantiation permissions.
- A new message, MsgUpdateContractLabel, has been added to enable contract label updates.
- Deprecated wasm governance proposals have been entirely removed from the codebase, along with all govv1beta1 dependencies.
- To enhance node stability and prevent out-of-memory (OOM) issues, various limitations and safeguards have been introduced. These measures include setting a pagination limit of 100 and restricting pin/unpin operations to a maximum of 50 code IDs per operation.
Additionally, some bugs have been successfully resolved, particularly an issue related to the gas calculation and an issue in the IbcQuery::ListChannels implementation when the port remains unspecified. With this latest update, if the port_id is not specified, only channels linked to the contract’s port will be listed.
Get Involved
Like what you see? Let the world know on Twitter or join the discussion on Discord. To stay informed, make sure to follow us on Medium and keep an eye out for CosmWasm Academy if you want to learn CosmWasm and become an awesome smart contract developer.
