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

Add support query ibc-denoms for a given chain id and path #1416

Closed
tnv1 opened this issue Mar 7, 2024 · 3 comments · Fixed by #1436
Closed

Add support query ibc-denoms for a given chain id and path #1416

tnv1 opened this issue Mar 7, 2024 · 3 comments · Fixed by #1436
Labels
C: CLI COMPONENT: Command-Line Interface good first issue Good for newcomers R: Minor RELEASE: Minor

Comments

@tnv1
Copy link

tnv1 commented Mar 7, 2024

Context:

I'm working with fee-abstraction and I need a cli to query ibc token denom when relayer is created between 2 chains.

Need support add query looks like:

rly q ibc-denoms <chain_name> <path>

Example:
rly q ibc-denoms osmosis transfer/channel-6072

should be returns:

62DDD1848B6F9182A658B6E88D7625F71D863E678ED043660692BD307C9217A0

@jtieri jtieri added good first issue Good for newcomers R: Minor RELEASE: Minor C: CLI COMPONENT: Command-Line Interface labels Mar 27, 2024
@jtieri
Copy link
Member

jtieri commented Mar 27, 2024

Thanks for opening an issue. This seems like a useful command to have and should be easy enough to add, perhaps it can be included in a future release.

@jtieri
Copy link
Member

jtieri commented Mar 27, 2024

I actually just opened a PR to add this new query now. Feel free to checkout and use that branch or the main branch once it is merged until it is included in our next release.

Hope this helps!

@tnv1
Copy link
Author

tnv1 commented Mar 28, 2024

Awesome! Thanks very much @jtieri

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: CLI COMPONENT: Command-Line Interface good first issue Good for newcomers R: Minor RELEASE: Minor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants