-
Notifications
You must be signed in to change notification settings - Fork 342
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
verifying logs from in between synced blocks #342
Comments
Ah this is a good catch. We should be backfilling blocks if we miss one, but as it stands right now we do not. For the case of log fetching it will miss that log, which is definitely a bug. We'll get on this soon. |
Happy to help 😁 If I'm not clear, what i mean is that whenever you fetch an |
So an easy way to do this if we have the latest block (let's call this block n) but are missing the prior block n-1, then we can fetch the previous blockhash pointer from block n, ask the rpc for block n-1, hash it, and confirm that it matches the pointer from block n. |
Block backfill is not implemented and available in 0.7.0. Fixed in #391 |
Hey everyone,
I am encountering an issue while syncing blocks from
MAINNET
. The blocks transmitted from the consensus layer to the execution’s state do not always follow a consecutive order by block number.For example, I've added an info log at the point where the execution's state receives the execution payloads from the consensus, to understand which block are getting cached in the state.

Here's an illustrative screenshot:
In the picture we can see that block
20420065
is successfully synced to the execution state, and then the subsequent block is20420067
, and no syncing of20420066
.The same goes for
20420069
,20420071
- not synced.My questions is, what should I do if I need to use
get_logs
to retrieve and verify logs from one of these missing blocks? In the code, for verifying logs, it queries the entire block from the state to accomplish this - however, the block appears to be missing.For example, if I have a log I wish to query from block
20420069
, is it possible to verify this log?The text was updated successfully, but these errors were encountered: