Skip to content
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

Handle incomplete data around restarts of beacons #94

Open
aimxhaisse opened this issue Nov 22, 2023 · 0 comments
Open

Handle incomplete data around restarts of beacons #94

aimxhaisse opened this issue Nov 22, 2023 · 0 comments

Comments

@aimxhaisse
Copy link
Member

Currently the watcher depends on the liveness API to know if attestations are missed:

https://ethereum.github.io/beacon-APIs/#/Validator/getLiveness

A beacon node that was recently started or suffered a network partition may indicate that a validator is not live when it actually is.

We sometimes end up reporting missed attestations at around beacon restart due to this, one improvement here would be to wait at start that the beacon has at least 2 epochs of uptime. Unsure how we can infer this from the beacon API but there may be ways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant