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

Query for all available denoms of a network #3293

Closed
4 tasks
faboweb opened this issue Jan 14, 2019 · 12 comments
Closed
4 tasks

Query for all available denoms of a network #3293

faboweb opened this issue Jan 14, 2019 · 12 comments

Comments

@faboweb
Copy link
Contributor

faboweb commented Jan 14, 2019

Summary

I want to show users all denoms available on a network. Currently I need to parse the genesis for this. It would be nicer to just be able to query this from the stargate. This way the frontend doesn't need to know about the genesis and therefor is a lot more flexibel.

Problem Definition

Proposal


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@fedekunze
Copy link
Collaborator

+++

@jackzampolin
Copy link
Member

I think this is something we need to have. Which module would this likely live in? auth or bank?

@alexanderbez
Copy link
Contributor

Something that might be covered via @sunnya97's bank supply PR?

@faboweb
Copy link
Contributor Author

faboweb commented Jan 22, 2019

@sunnya97 ping

@jackzampolin
Copy link
Member

We decided to push that bank work to #postlaunch This will need to be a separate PR.

@sunnya97
Copy link
Member

The easiest way to do this would be to copy the bank store stuff from that PR, but don't the Supply stuff, just the denom names (and probably the decimals).

@cwgoes
Copy link
Contributor

cwgoes commented Jan 22, 2019

Voyager will always need to have the genesis anyways, because it's the root-of-trust for lite client proofs.

@faboweb
Copy link
Contributor Author

faboweb commented Jan 22, 2019 via email

@cwgoes
Copy link
Contributor

cwgoes commented Jan 22, 2019

Yes, but we'll need it later when we do (I don't disagree with the REST endpoint though).

@fedekunze
Copy link
Collaborator

the supply module will support this query

@fedekunze
Copy link
Collaborator

closed via #4255

@jbibla
Copy link
Contributor

jbibla commented Jul 2, 2019

@faboweb for your reference

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

No branches or pull requests

7 participants