-
Notifications
You must be signed in to change notification settings - Fork 313
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
[HOLESKY PECTRA] onBlockImport accessing a missing state #9178
Comments
ok basically we've got a block we've just imported, but we're getting the state from the target of the attestation. its super important we just use a state we have if we can, and in this specific case we're importing a block that contained the attestation so the post state from the attestation should have the data we need already. It's a bit of jigging around so will come back to this if noone picks up, but its a legitimate issue, not just logging. potentially |
possibly one of the best candidates is |
I think we can even avoid putting attestations in the pool when they are older than 64 slots (from current slot). this happens while we are syncing and those attestations are not interesting. |
yep 100%, if we're at head - they probably should fail this:
if we're outside the propagation slot range, we should ignore it coming in, it should never get processed... (rules as at deneb) |
The path here is different I guess because its We would be able to use the same state as the pre-state from the block (or the postState really) to verify that aggregate, as it made it into the block when being built. |
fixes Consensys#9178 Signed-off-by: Paul Harris <[email protected]>
way too much noise here.
The text was updated successfully, but these errors were encountered: