Note:
This release amends the release of 08-wasm v0.3.0 with ibc-go v7.3 to bump the version of ibc-go to v7.4 as v7.3 was redacted. No additional commits have been made.
Highlights 🌟
We present here a summary of the most relevant changes, please see the changelog for more details.
- In v0.3.1+ibc-go-v7.4-wasmvm-v1.5 we added a new
MerklePath
type and used it for thePath
field of theVerifyMembershipMsg
andVerifyNonMembershipMsg
structs of the contract API. This change was API breaking for light contracts and it required a migration for existing contracts to correctly handle deserialization of theKeyPath
field (which had changed from[]string
to[][]byte
). In this release we are making an extra change to explicitly break the contract API JSON message field name: thepath
field of the JSON-encodedVerifyMembershipMsg
andVerifyNonMembershipMsg
messages has been ranamed tomerkle_path
, so that light client contracts would not silently unmarshal a key as a base64 encoded string value (and instead fail to unmarshal the message entirely).
All previous releases of the 08-wasm compatible with ibc-go v7.3 and wasmvm v1.5 have been retracted and we strongly recommend contract developers to update their JSON API message structure for the SudoMsg
payloads VerifyMembershipMsg
and VerifyNonMembershipMsg
.
For chains on v7.3 or above in the v7 line that have not deployed a light client contract yet, we strongly recommend to upgrade to this release first and then deploy the updated contract. Otherwise, chains will need to migrate the contract later on.
Migration 🦆
Please check out the migration docs to upgrade to this release from v0.2.x compatible with ibc-go v7.3.x.
In order to use this release, please follow the steps to import git commit 13c071f.