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
A call to /eth/v1/validator/duties/sync with a future slot returns an error when it should not.
/eth/v1/validator/duties/sync
The slot should be considered valid if it is in the current or next sync epoch, with the next sync epoch being in the future.
No.
POST to /eth/v1/validator/duties/sync with a slot in the future.
{ "message": "Could not get sync committee state: slot cannot be in the future", "code": 500 }
develop
The text was updated successfully, but these errors were encountered:
This can be closed. The wrong issue was reopened.
Sorry, something went wrong.
rkapka
Successfully merging a pull request may close this issue.
🐞 Bug Report
Description
A call to
/eth/v1/validator/duties/sync
with a future slot returns an error when it should not.The slot should be considered valid if it is in the current or next sync epoch, with the next sync epoch being in the future.
Has this worked before in a previous version?
No.
🔬 Minimal Reproduction
POST to
/eth/v1/validator/duties/sync
with a slot in the future.🔥 Error
🌍 Your Environment
develop
The text was updated successfully, but these errors were encountered: