-
Notifications
You must be signed in to change notification settings - Fork 1k
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
study freezing of validators #14515
Comments
The inactive validators should be pruned and validator index should be reused for later validator. |
Hello, I would like to work on this, but I need some help.
How do I go about this change? Should I make a And before doing all of this, should I look at any other client implementations to see if they have this implemented? |
@threewebcode Reusing validator index must be followed by a core proposal. It seems like EIP-6914 once generates a discussion about this. @tushar994 I am interested this topic also, since it will be a huge burden especially after consolidation comes into. Rough note here:
|
To date we have 1.6M validators in the validator slice, but less than 1.1M active validators. This proposal is to study replacing the corresponding exited validators by their HTR in the state structure. This should result in savings of about 45MB per beacon state. We could study how other clients have implemented this (I believe Nimbus already did this). A straw-man design is to have pointers to a validator interface in the state instead of pointers to the actual validator. We would have two types of structures satisfying this interface, a usual validator and an
FrozenValidator
. This last one would return errors for anything other thanActive()
(it can be hardcoded to false in the root version) andHashTreeRoot()
(which would return the frozen root).The text was updated successfully, but these errors were encountered: