-
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
pindexer: ⏰ add AppView
mapping height to timestamps
#4675
Comments
github-actions
bot
added
the
needs-refinement
unclear, incomplete, or stub issue that needs work
label
Jun 27, 2024
cratelyn
added
A-indexing
Area: Relates to event indexing.
and removed
needs-refinement
unclear, incomplete, or stub issue that needs work
labels
Jun 27, 2024
This was referenced Jul 17, 2024
vacekj
added a commit
that referenced
this issue
Jul 18, 2024
## Describe your changes this makes a non-consensus-breaking change, adding a timestamp field to the EventBlockRoot proto. This will be used to keep track of the timestamp of the block for use in pindexer. I tested this by running a local devnet with the changes to core. Pd runs fine and the timestamps are correctly propagated to the raw events db. ## Issue ticket number and link prerequisite for #4675 ## 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: - only adds a field - adds this field to an Event proto
cronokirby
pushed a commit
that referenced
this issue
Jul 22, 2024
this makes a non-consensus-breaking change, adding a timestamp field to the EventBlockRoot proto. This will be used to keep track of the timestamp of the block for use in pindexer. I tested this by running a local devnet with the changes to core. Pd runs fine and the timestamps are correctly propagated to the raw events db. prerequisite for #4675 - [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: - only adds a field - adds this field to an Event proto
2 tasks
cronokirby
added a commit
that referenced
this issue
Jul 22, 2024
this makes a non-consensus-breaking change, adding a timestamp field to the EventBlockRoot proto. This will be used to keep track of the timestamp of the block for use in pindexer. I tested this by running a local devnet with the changes to core. Pd runs fine and the timestamps are correctly propagated to the raw events db. prerequisite for #4675 - [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: - only adds a field - adds this field to an Event proto ## Describe your changes ## Issue ticket number and link ## Checklist before requesting a review - [ ] 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: > REPLACE THIS TEXT WITH RATIONALE (CAN BE BRIEF) --------- Co-authored-by: Josef <[email protected]> Co-authored-by: Conor Schaefer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
other indexes include a mapping from block height to timestamp. add an app view that does just that, as a stepping stone towards the views for block contents (#4674) and trading volume (#4673).
penumbra-zone/dex-explorer#25
The text was updated successfully, but these errors were encountered: