-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Comments
+++ |
I think this is something we need to have. Which module would this likely live in? |
Something that might be covered via @sunnya97's bank supply PR? |
@sunnya97 ping |
We decided to push that bank work to #postlaunch This will need to be a separate PR. |
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). |
Voyager will always need to have the genesis anyways, because it's the root-of-trust for lite client proofs. |
We don't have lite client proofs right now.
Christopher Goes <[email protected]> schrieb am Di., 22. Jan. 2019
um 19:14 Uhr:
… Voyager will always need to have the genesis anyways, because it's the
root-of-trust for lite client proofs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3293 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFmO2TTZ5AHmwxgVNCV3jh3NiyBWIJfsks5vF1UEgaJpZM4Z-T-x>
.
|
Yes, but we'll need it later when we do (I don't disagree with the REST endpoint though). |
the supply module will support this query |
closed via #4255 |
@faboweb for your reference |
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
The text was updated successfully, but these errors were encountered: