-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add SSZ support to register validator api #110
Conversation
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.
LGTM
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
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.
LGTM, thanks @nflaig!
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.
lgtm
Follow up on #104 to also add SSZ support to
registerValidator
api, which should help in cases where the validator client runs a lot of keys and reduce amount of failed requests.Since we can't really know if the server supports sending the validator registration as SSZ encoded payload the client will be responsible to retry the request using JSON which ideally should only be done if the error status code is 415, indicating an unsupported media type, but since right now we don't really know if all servers properly follow the spec, it is recommended to retry all HTTP errors and after the first error, the client should stop sending SSZ encoded validator registrations.