Skip to content
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

Unable to close channel with misconfiguration #3945

Open
5 tasks
redemdev opened this issue Apr 15, 2024 · 2 comments
Open
5 tasks

Unable to close channel with misconfiguration #3945

redemdev opened this issue Apr 15, 2024 · 2 comments

Comments

@redemdev
Copy link

Summary of Bug

Unable to close channel with misconfiguration.
I created IBC channel but the destination channel show as the channel-id I use for other IBC path (that one works well)
Not sure if it's error while creating this one.
Which results in transferring token failed.

I try closing channel following this doc:
https://hermes.informal.systems/advanced/troubleshooting/patch-gaia.html
https://hermes.informal.systems/documentation/commands/tx/channel-close.html

But still got error "user cannot close channel"

How can I close channel with misconfiguration.

Version

hermes 1.8.2

Steps to Reproduce

Acceptance Criteria


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@romac
Copy link
Member

romac commented Apr 15, 2024

Is this for a live chain or a development app you are building yourself?

The patch instructions above only work if you running your own devnet, but not for a testnet or livenet.

@redemdev
Copy link
Author

I see, it's our live chain on mainnet which create IBC path with Hermes.
If it's on mainnet, is there anyway to close the channels we created.

By the way, I think there's something error when I try to create channels.

The working path:

Our chain <> Chain A
channel-0 <> channel-xxx

Our chain <> Chain B
channel-1 <> channel-yyy

Then there's a trouble path comes up like
Our chain <> Chain B
channel-0 <> channel-zzz

So the token sent through channel-zzz got stucked as the destination channel is channel-0, which actually belong to Chain A path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🩹 Triage
Development

No branches or pull requests

2 participants