We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think we should pause light client computations if the fork epoch is misaligned in a way that breaks our calculations.
This should be necessary only for ~1 sync committee period around the fork.
It would be nice to avoid error logs, even if they are harmless, like:
Feb 13 20:25:36.228 ERRO error computing light_client updates LightClientUpdateError(BeaconStateError(IncorrectStateVariant)), service: lc_update
The text was updated successfully, but these errors were encountered:
eserilev
Successfully merging a pull request may close this issue.
I think we should pause light client computations if the fork epoch is misaligned in a way that breaks our calculations.
This should be necessary only for ~1 sync committee period around the fork.
It would be nice to avoid error logs, even if they are harmless, like:
The text was updated successfully, but these errors were encountered: