FR: Refactor CosmWasm messages to use distinct response types for each query

[srdtrk]

Feature Summary

Currently, the contract API messages defined in the CosmWasm context return the same response type for each query type. This necessitates an aggregate struct with all fields optional. This approach is not ideal. Instead, the response types should be distinct and specific to each query type, similar to how they are defined in the 08-wasm module.

Proposal

I have created a wrapper contract around the ics07-tendermint context that implements this improved approach. Here are the types I used in that contract: response definitions and query definitions. Note that I am using this contract for other purposes (not in 08-wasm). (This repository successfully implements all of IBC-lite in CosmWasm, allowing for end-to-end packet passing with an ibc-go counterparty without any dependency on ibc-go.)

By adopting distinct response types for each query, we can enhance clarity, maintainability, and adherence to best practices in the contract API.

[Farhad-Shabani]

Much appreciate the details @srdtrk. Makes a lot of sense.

I have created a wrapper contract around the ics07-tendermint context that implements this improved approach. Here are the types I used in that contract

Do you feel up for opening a PR and upstream your changes to ibc-rs?

This repository successfully implements all of IBC-lite in CosmWasm, allowing for end-to-end packet passing with an ibc-go counterparty without any dependency on ibc-go.

Awesome news! It's great to hear that ibc-rs could assist with the ibc-lite PoC 🚀.

[srdtrk]

Ok, I'll open a PR

[srdtrk]

In this PR, I've also removed ExportGenesis. This is because it is no longer in the 08-wasm contract api. The reason for this is that in 02-client, the genesis metadata of all the light clients are exported anyway. Which always includes the light client's genesis metadata. And similarly, if this light client is used in cosmwasm directly, then x/wasm would export the metadata of all contracts.