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

pindexer: insights dashboard support #4896

Closed
10 tasks
Tracked by #4883
aubrika opened this issue Oct 17, 2024 · 0 comments · Fixed by #4898
Closed
10 tasks
Tracked by #4883

pindexer: insights dashboard support #4896

aubrika opened this issue Oct 17, 2024 · 0 comments · Fixed by #4898
Assignees
Labels
A-indexing Area: Relates to event indexing.

Comments

@aubrika
Copy link
Contributor

aubrika commented Oct 17, 2024

Following internal discussion, some design notes accepted for the insights dashboard:

  • Pindexer should have a new AppView specifically for the insights dashboard data.

  • One table for the token info, containing (at each height where the values change):

    • total supply
    • the total amount of tokens staked
    • the price
    • the market cap.
  • Another table for the shielded pool, for each asset, at each time:

    • total value shielded
    • current value shielded
    • number of transparent addresses who have shielded

The intention is that the changes can then be calculated on demand by querying the current value, the value 24h ago, etc.

@aubrika aubrika mentioned this issue Oct 17, 2024
3 tasks
@github-actions github-actions bot added the needs-refinement unclear, incomplete, or stub issue that needs work label Oct 17, 2024
@aubrika aubrika added A-indexing Area: Relates to event indexing. and removed needs-refinement unclear, incomplete, or stub issue that needs work labels Oct 17, 2024
@aubrika aubrika changed the title insights dashboard pindexer: insights dashboard support Oct 17, 2024
conorsch pushed a commit that referenced this issue Oct 21, 2024
Closes #4896.

This adds the requisite tables, with a component parametrized by the
numeraire for price information. Price information uses candlestick data
for generating the price, so the recently added event will need to be
used there.

This also backfills in rich domain types into old crates as necessary,
for convenience.

Also closes #4883, since at this point we've refactored out all
requisite schemas.

## Checklist before requesting a review

- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:

  > indexing only
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-indexing Area: Relates to event indexing.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants