Check the changes of cosmwasm/wasmd v0.29

[zemyblue]

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

asmd	wasmvm	cosmwasm-vm	cosmwasm-std
0.29	v1.1.0		1.0-1.1
0.28	v1.0.0		1.0-1.1
0.27	v1.0.0		1.0

Proposal

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[da1suk8]

Summarize

v0.27.0 → v0.28.0, there were three fix changes.

• Don't pass non-wasm events to reply() CosmWasm/wasmd#917
• CosmWasm/wasmd@2a9c5c1
• CosmWasm/wasmd@2886092

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