-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
Wrong state in attestation validation #4831
Labels
prio-medium
Resolve this some time soon (tm).
Comments
dapplion
added
prio-high
Resolve issues as soon as possible.
prio-medium
Resolve this some time soon (tm).
and removed
prio-high
Resolve issues as soon as possible.
labels
Nov 30, 2022
got this error right after
|
it has happened until node is synced. Stack trace of the above error:
|
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
packages/beacon-node/src/chain/validation/attestation.ts:81
retrieves the wrong state.It causes signature validation to fail if the first slot of a fork is missed. The domain of the state will be wrong, since it will pick the domain of the previous fork, due to updated getDomain logic
The text was updated successfully, but these errors were encountered: