Update melextraction package to use logs instead of receipts and implement logs and headers fetcher #4063
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ement logs and headers fetcher
ganeshvanahalli
requested review from
Tristan-Wilson,
magicxyyz and
rauljordan
|
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR pulls in two changes from the main MEL PR
melextractionpackage where the functions have been updated to utilize logs instead of tx receipts, andPreviously MEL Processed parent chain blocks by going over all txs- fetching receipts for each tx- to eventually work on the tx log- this was inefficient leading to significant delay in catchup times and once caught up to stay catch up was just very hard. We solve this by directly processing the MEL relevant logs in a block! And to even speed this up- we have a
logsAndHeadersFetcherto fetch relevant logs (througheth_getLogsquery) and headers (by making batch rpc requests toeth_getBlockByNumber) ahead of time.