Problem: missing ibc message MsgTransfer in Cosmos SDK (fix #167)

[stevenatcrypto]

Close #167

Summary

1. Add crate ibc-rs for struct of IBC message MsgTransfer in common.

2. Add C++ and wasm binding.

3. Add a wasm test case. Only test if the signed MsgTransfer message could be parsed by crypto.org chain of integration-test.

TODO

Suppose to submit new issues and fix them in following PRs.

1. Support hex address for receiver when invoking binding function get_ibc_transfer_signed_tx (may use crate bech32).

2. Try to support full test case for MsgTransfer in integration-test. Should validate both sender and receiver balances (in different chains).

[tomtau]

thanks for this! just one question -- is there any reason not to use the ibc or ibc-proto crates?

[stevenatcrypto]

thanks for this! just one question -- is there any reason not to use the ibc or ibc-proto crates?

I am sorry that I didn't find the crate ibc. It should be better to use MsgTransfer of ibc directly. I will give a try to update. Thanks for the info.

[tomtau]

no problem!

[SHH-HaoZhang]

Tested data is correct

[stevenatcrypto]

Hi @tomtau, I update code to use crate ibc-rs. But there is a dependency issue of crate tendermint for both cosmos-rust and ibc-rs as below:

versions that meet the requirements `=0.23.3` are: 0.23.3

all possible versions conflict with previously selected packages.

  previously selected package `tendermint v0.23.5`

The current version of tendermint is =0.23.3. But ibc-rs upgraded tendermint from =0.23.2 to =0.23.4 directly in this-commit. So I could not find the match version for both crates.

I forked the Github repository cosmos-rust, and sent PR-178 to fix it. But I could only specified dependecy cosmrs and cosmos-sdk-proto from my forked Github repository in this PR. Could you help review if it is all right? Or we need to fork cosmos-rust to Orgnazation crypto-com. What do you think? Thanks.

[tomtau]

@stevenatcrypto looks all right -- I forked your repo to https://github.com/crypto-com/cosmos-rust so we can maintain all dependencies under one org until the upstream is updated