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.

Sign up for GitHub

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

Jump to bottom

Prune fork choice equivocating indices #3373

Open
michaelsproul opened this issue Jul 26, 2022 · 0 comments
Open

Prune fork choice equivocating indices #3373

michaelsproul opened this issue Jul 26, 2022 · 0 comments
Labels
consensus An issue/PR that touches consensus code, such as state_processing or block verification. optimization Something to make Lighthouse run more efficiently.

Comments

@michaelsproul
Copy link
Member

Description

We added tracking of equivocating indices to fork choice in #3371, but no mechanism to prune the set of equivocators.

The spec states that we should maintain the set of equivocating indices since "at least finalization", but I think this is perhaps slightly too short, as validators remain active and capable of attesting until their exit_epoch. We could prune all validators whose exit_epoch <= finalized_epoch.
@michaelsproul michaelsproul mentioned this issue Jul 26, 2022
Closed
5 tasks
@michaelsproul michaelsproul added optimization Something to make Lighthouse run more efficiently. consensus An issue/PR that touches consensus code, such as state_processing or block verification. labels Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
consensus An issue/PR that touches consensus code, such as state_processing or block verification. optimization Something to make Lighthouse run more efficiently.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michaelsproul