-
Notifications
You must be signed in to change notification settings - Fork 326
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
hermes query channels --chain chain_id
to output the counterparty chain_id
#2429
Comments
Hi @AlianBenabdallah I am wondering if this change is necessary as there are two optional flags which allow to retrieve the information required.
What do you think ? |
Hi @ljoss17, I think I did not know about |
Indeed the verbose is not ideal for this scenario. In order to test the With this
Don't forget to setup the correct global
Then if you run
And if you run
|
Indeed that's convenient. However, this flag applies filtering and I think that usually, filtering should be done on a visible attribute. Also, in some sense, using the command without any flag is not very useful. @adizere, you have any opinion regarding the output of |
I think the current default behavior of For the issue raised here specifically -- about introducing the counterparty chain identifier in each output element -- maybe we can do it by introducing an additional option to this CLI, say So we would end-up with 3 possible invocations of this CLIm, first two described by Luca above:
The third:
to
|
This new flag would be a great idea. |
@AlianBenabdallah Do you want to take a stab at it? |
Summary
hermes query channels --chain chain_id
currently retrieves all the channel_ids and associated ports.To this information, I think adding the counterparty chain's id would be helpful.
Problem Definition
In order to transfer packets from A to B, if the user does not know which channel should be used, he need to retrieve all the channels on A then for every channel use
hermes query channel --chain --channel --port
to retrieve information about the counterparty.In a situation with many chains, it can be exhausting.
I propose to add information about the counterparty in
hermes query channels
Proposal
hermes query channels --chain chain_id
would produce an output of this format :Instead of :
Acceptance Criteria
hermes query channels --chain ibc-0
gives all the channels and the counterparty chain's id.For Admin Use
The text was updated successfully, but these errors were encountered: