-
Notifications
You must be signed in to change notification settings - Fork 919
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
Ensure Slashing Protection Exports and Keymanager API Work According to Spec #9938
Conversation
keys []*keyCase | ||
wantStatuses []ethpbservice.DeletedKeystoreStatus_Status | ||
}{ | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Table driven test to match what the specification wants
Ready @james-prysm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will deprecate in favor of keystore standards in the future after implementation is done.
As defined in the validator keymanager API standard, there are a few intricate details that we must ensure we support and behave as required. This PR adds a few fixes to ensure the behavior is up to spec:
For
ImportKeystores
ImportKeystores
endpoint has a corresponding password. Even if using one password to encrypt everything, we should just duplicate that password N times in the request where N = len(keystores)For
DeleteKeystores