da1suk8
commented
2 years ago Summarize
v0.27.0 → v0.28.0, there were three fix changes.
- https://github.com/CosmWasm/wasmd/pull/917
- https://github.com/CosmWasm/wasmd/commit/2a9c5c1ea542d3d968bebeea7031a7d0a4e38ffa
- https://github.com/CosmWasm/wasmd/commit/288609255ad92dfe5c54eae572fe7d6010e712eb
v0.28.0 → v0.29.0, there were many changes. I put notable changes of CHANGELOG.
Notable changes
- BaseAccount and pruned vesting account types can be re-used for contracts addresses
- A new MsgInstantiateContract2 was introduced which is an additional value for message type events
- Store event contains a new attribute with the code checksum now
- New wasmd tx wasm instantiate2 CLI command for predictable addresses on instantiation
- New cosmwasm_1_1 CosmWasm capability (former "feature") was introduced in cosmwasm/#1356 to support total supply queries
- Protobuf files are published to buf.build
Summary
Check the changed from cosmwasm/wasmd v0.27 to v0.29.
Problem Definition
The latest cosmwasm/wasmd version is v0.29.0-rc0 (https://github.com/CosmWasm/wasmd/releases/tag/v0.29.0-rc0) and our wasm is based cosmwasm/wasmd v0.27 (refer #570) So we need to check the changes of v0.28 and v0.29. If the critical bug is fixed through these versions, we need to upgrade the base version.
Compatibility
<!DOCTYPE html>
Proposal
For Admin Use