Fix: Use settings key to sync reward snapshots #297
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
seedStakerRewardSnapshotsnow we use a key on the Settings table to store the last synced timestamp. Previously, we incorrectly assumed that all snapshots would have the same date and just made a prisma call to theStakerRewardSnapshottable to find the latest timestamp. However, the table actually stores the latest timestamp for a given record rather than the latest timestamp of the snapshot requested from the EL bucket.Additionally, a minor optimization is made to the AVS APY monitor prisma call to consider only those AVSs that have reward submissions