WIP: validator set persistence #200
Draft
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.
This PR adds a validators table to the db and persists the finalized validator set there.
The validator cache is responsible for writing and updating validator entries.
It uses a batched approach for mass updates to keep the db load manageable.
This PR touches a lot of code as the validator set accessors changed.
Instead of fetching the full validator set and doing filtering/aggregation logic in the page handlers, the page handlers will now only fetch a filtered subset of the validator set.
This PR should significantly lower the memory consumption of dora when running in a network with large validator sets (holesky, mainnet)