-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues during testing interchain accounts application #1191
Closed
3 of 5 tasks
Comments
6 tasks
This was referenced Aug 19, 2021
Merged
romac
added a commit
that referenced
this issue
Aug 23, 2021
* temp fix * Debugability, add check for chan try for counterparty ch * Get events from RPC event's data insead of events * Fix error message * Debug for proof bytes and getter of other_proof * fmt fix * Remove event conversion, redundant with current tendermint-rs refpoint * Review comments * Add .changelog entry for #1191 * Fix clippy warning Co-authored-by: Romain Ruetschi <romain@informal.systems>
hu55a1n1
pushed a commit
to hu55a1n1/hermes
that referenced
this issue
Sep 13, 2022
) * temp fix * Debugability, add check for chan try for counterparty ch * Get events from RPC event's data insead of events * Fix error message * Debug for proof bytes and getter of other_proof * fmt fix * Remove event conversion, redundant with current tendermint-rs refpoint * Review comments * Add .changelog entry for informalsystems#1191 * Fix clippy warning Co-authored-by: Romain Ruetschi <romain@informal.systems>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Crate
relayer
Summary
With the new revision of ics-27, hermes does not relay the interchain account transfers anymore. This is mainly caused by the different
message.action
tags and dynamic port-id information.Version
master
Steps to Reproduce
Use the interchain account repo from cosmos/interchain-accounts-demo#52 that implements the new spec. Run the steps described here with latest hermes.
This step fails:
Acceptance Criteria
Running the steps described here should be successful up to the channel closing.
For Admin Use
The text was updated successfully, but these errors were encountered: