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

Consider sync committee participation for exiting validators #694

Open
Tracked by #698
DaniSchenk opened this issue May 29, 2024 · 0 comments
Open
Tracked by #698

Consider sync committee participation for exiting validators #694

DaniSchenk opened this issue May 29, 2024 · 0 comments

Comments

@DaniSchenk
Copy link

defaultMessage="{exitEpochLabel} - epoch at which your validator is no longer active, no longer earning rewards, and is no longer subject to slashing rules."

image

I think this explanation does not consider an exiting validator being part of the sync committee. This validator (beaconcha.in) was elected to be part of the sync committee (SC) starting at 201472. Before the SC started, the validator exited at 201320. The validator kept running, was marked withdrawable and was even fully swept 26 epochs before the SC ended. It earned SC rewards throughout the entire SC epochs and there's a partial withdrawal after the full withdrawal and end of the SC.
image

So this statement from the launchpad does not seems to be accurate, or at least not accurate regarding SC participation, right?

validator is no longer active, no longer earning rewards

TBH, SC participation is a very rare event for operators and this scenario is probably an edge case. But since it's a very lucrative situation for operators, it might be worth mentioning:

  • to keep the validator running if it's part of the current or next SC
  • to keep the validator running for 512 (256*2 = 2 SCs) epochs after exiting by default, if the SC participation check is not feasible

What do you think?

Credits to the Figment team for providing the illustration and validator example.

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