-
Notifications
You must be signed in to change notification settings - Fork 191
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
[DataApi][Stage1] Deregistered operators endpt for LameDuck Operators #152
[DataApi][Stage1] Deregistered operators endpt for LameDuck Operators #152
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.
You may want to generate swagger docs for this interface
Note: Would like to merge this PR, if i can get an approval |
done |
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, would be nice to put an example of the output in the description of the PR.
added |
Why are these changes needed?
Definition LameDuckOperator: Operator who was deregistered recently past
14
days as an example. Even if the Operator is DeRegistered their is responsibility to be available for the blobs they signed before DeRegisteration.If that operator is offline, but is in the 14 day window they are termed as LameDuck Operator
Sample Query
Query: GET "/v1/operatorsInfo/deregisteredOperators/?days=14"
Response: {"meta":{"size":2},"data":[{"operator_id":"0xe22dae12a0074f20b8fc96a0489376db34075e545ef60c4845d264a732568311","block_number":22,"ip_address":"localhost:32007","is_online":false},{"operator_id":"0xe23cae12a0074f20b8fc96a0489376db34075e545ef60c4845d264b732568312","block_number":24,"ip_address":"localhost:32009","is_online":true}]}
Stages
[Stage1][Current]: Implementation to query and check if DeRegistered Operators are online or not. A very simple check and provide a list
[Stage2]: Implementation to follow with block timestamp for last signed batch and possibly stats on how many days was operator offline for in the 14 day window.
Checks