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

q ibc-transfer denom-trace {denom} should allow denom to begin with ibc #1489

Closed
3 tasks
ValarDragon opened this issue Jun 6, 2022 · 1 comment
Closed
3 tasks

Comments

@ValarDragon
Copy link
Contributor

The CLI command for osmosisd q ibc-transfer denom-trace {denom} do not accept the ibc prefix.

The natural UX of copy/pasting an IBC denom and querying it does not work as a consequence, e.g. copying ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2 yields:

osmosisd q ibc-transfer denom-trace ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2
Error: rpc error: code = InvalidArgument desc = rpc error: code = InvalidArgument desc = invalid denom trace hash ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2, encoding/hex: invalid byte: U+0069 'i': invalid request

Instead one has to manually edit, to get

osmosisd q ibc-transfer denom-trace 27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2
denom_trace:
  base_denom: uatom
  path: transfer/channel-0

Summary of Bug

q ibc-transfer denom-trace should accept ibc prefixes

Version

IBC v2.x


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@crodriguezvega
Copy link
Contributor

Thanks for the suggestion, @ValarDragon, but this is a duplicate of #101, which has already been solved by #1342. The fix will be released this or next week. I think we can therefore close this issue.

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

No branches or pull requests

2 participants