build(deps): bump github.com/cosmos/ibc-go/modules/light-clients/08-wasm from 0.1.1-0.20231213092633-b306e7a706e1 to 0.1.1-ibc-go-v7.3-wasmvm-v1.5

[dependabot]

Bumps github.com/cosmos/ibc-go/modules/light-clients/08-wasm from 0.1.1-0.20231213092633-b306e7a706e1 to 0.1.1-ibc-go-v7.3-wasmvm-v1.5.

Release notes

Sourced from github.com/cosmos/ibc-go/modules/light-clients/08-wasm's releases.

modules/light-clients/08-wasm/v0.2.0+ibc-go-v8.3-wasmvm-v2.0

Highlights 🌟

We present here a summary of the most relevant changes, please see the changelog for the full set of changes included in this release.

• Update of wasmvm to v2.0.1.
• A CLI command to broadcast a transaction with MsgMigrateContract. See the documentation for more details.
• In v8.3.0 we added the VerifyMembershipProof query service gRPC endpoint to query an IBC light client for proof verification. And now in this release we have added a defaultAcceptList with the query route /ibc.core.client.v1.Query/VerifyMembership to allow for light client smart contracts to delegate parts of their workflow to other light clients for auxiliary proof verification.

Migration 🦆

Please check out the migration docs to upgrade to this release from v0.1.x compatible with wasmvm v1.5.x.

In order to use this release, please follow the steps to import git commit 4b45d1822fb6a0698e7621112b92c13679061c40.

modules/light-clients/08-wasm/v0.1.1+ibc-go-v7.3-wasmvm-v1.5

This release:

• Adds the registration of the transaction CLI commands for 08-wasm, which was missing in v0.1.0+ibc-go-v7.3-wasmvm-v1.5. Thanks to @​Farhad-Shabani and @​nicolaslara, who both reported this.
• Bumps wasmvm to v1.5.2.

The changelog for this release is available here.

modules/light-clients/08-wasm/v0.1.0+ibc-go-v8.0-wasmvm-v1.5

This is the first release (compatible with ibc-go v8.0) of the anticipated 🥁🎺 08-wasm light client proxy module 🌈🤩 Read the blog post by @​adiraviraj announcing the release, for more information.

What is the 08-wasm module?

The 08-wasm client module comprises a Wasm VM capable of hosting light client bytecode, offering the flexibility to write new light clients in any language that compiles to Wasm (Rust, C/C++, JS, Go, etc.). With a consistent interface aligned with ICS 02, this module serves as a proxy light client, facilitating interaction with the actual light client contracts deployed as Wasm bytecode. To learn more about what it means to be a proxu light client, please read this section of the documentation.

Why do we need it?

The expansion of IBC into new blockchain ecosystems necessitates adding support for new light clients. Light clients for non-Cosmos ecosystem chains are, in many cases, implemented in Rust, and thus there are probably libraries used in their light client implementations for which there is no equivalent in Go. This makes the development of a light client in Go very difficult, but relatively simple to do it in Rust. Therefore, writing a CosmWasm smart contract in Rust that implements the light client algorithm becomes a lower effort. However, The light client can actually be implemented in any language that compiles to Wasm and implements the interfaces of a CosmWasm contract. Even though in theory other languages could be used, in practice (at least for the time being) the most suitable language to use would be Rust, since there is already good support for it for developing CosmWasm smart contracts.

At the moment of this release there are two contracts available: one for Tendermint and one GRANDPA (which is being used in production in Composable Finance's Centauri bridge). And there are others in development (e.g. for Near).

How can I use it?

First the 08-wasm module needs to be integrated in the chain. For more details about how to integrate the module in your own chain, please read this section of the documentation. Then, adding a new light client to a chain is just as simple as submitting a governance proposal with the message that stores the byte code of the light client contract. No coordinated upgrade is needed. When the governance proposal passes and the message is executed, the contract is ready to be instantiated upon receiving a relayer-submitted MsgCreateClient. The process of creating a Wasm light client is the same as with a regular light client implemented in Go. Please read this section of the documentation, for more information.

Our e2e tests used the GRANDPA contract at this hash of Composable Finance's composable-ibc repository. To build the bytecode for the contract we have followed these steps:

# set up environment
rustup toolchain install nightly
rustup target add wasm32-unknown-unknown
rustup +nightly target add wasm32-unknown-unknown
cargo install wasm-opt --locked
</tr></table>

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.