op-node: workaround alchemy eth_getProof by blockhash RPC issue #4644
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
Alchemy does not yet support
eth_getProof
calls with blockhash parameter like other RPC providers due to incomplete execution-apis spec (fixed in ethereum/execution-apis#326 )To work-around it, we check if it's Alchemy & if it's a blockhash argument, then first fetch the block header by hash, and then the proof by number, and verify the retrieved proof against the header to make sure the data is correct.
Tests
Alchemy-only functionality, run with
--l1.rpckind=alchemy
to test.Metadata
Fix ENG-3178