beacon: Fix OP Legacy block hash checks #228
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This fixes the OP Legacy Consensus engine
VerifyHeaders
function. WhenVerifyHeaders
is called, only the first block is stored in the database & the reset are passed in as a slice. We previously calledVerifyHeader
fromVerifyHeaders
which would expect that the block's parent was in the database. This modifiesVerifyHeaders
to check that the first block is in the database & then checks the blocks one by one through the slice.Tests
I have tested this on op-goerli & op-mainnet.