-
Notifications
You must be signed in to change notification settings - Fork 296
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
Total supply api #4835
Comments
We will prioritize this - I scheduled a team design meeting for tomorrow to discuss the best way to implement it. |
Even just an upper bound on the amount penumbra that exists would be sufficient. |
The computation that needs to be done is:
This should be very simple to implement, and provide in a new RPC as part of the staking component's |
Where does the staking component track total UM? |
Update following discussion of this internally: a legacy supply tracking implementation was removed from the shielded pool on account of being the wrong place to do this work, but not replaced before launch with another implementation. In the absence of something doing that for us, we will need to utilize our indexer to perform this calculation using historical block data - which is more involved than was initially thought, as it was assumed the protocol was tracking events that it was not. We are actively working on this, just ran into some friction. |
#4835 --------- Co-authored-by: Lucas Meier <[email protected]>
This is completed by the total supply indexer work, which can support any number of UI layers |
To get the Penumbra correctly listed on sites like Coinmarket cap and Coingecko, we need an API that they can query for the total supply of penumbra tokens.
The text was updated successfully, but these errors were encountered: