feat: l1/l2 indexer service#2001
Closed
tuxcanfly wants to merge 107 commits intoethereum-optimism:developfrom
Closed
feat: l1/l2 indexer service#2001tuxcanfly wants to merge 107 commits intoethereum-optimism:developfrom
tuxcanfly wants to merge 107 commits intoethereum-optimism:developfrom
Conversation
|
mslipper
reviewed
Jan 12, 2022
mslipper
reviewed
Jan 12, 2022
mslipper
reviewed
Jan 12, 2022
mslipper
reviewed
Jan 12, 2022
mslipper
reviewed
Jan 12, 2022
tynes
reviewed
Feb 28, 2022
| } | ||
| return common.Address{}, fmt.Errorf("invalid address: %v", address) | ||
| } | ||
|
|
Contributor
There was a problem hiding this comment.
It should be safe to just use the upstream common package for address parsing
Collaborator
|
Closing in favor of a smaller PR with a single commit. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 PR adds L1/L2 indexer that is a background service for indexing deposits and withdrawals on L1 and L2 respectively.
The goal is to have all the deposit/withdrawal history by account in the database, that can improve the response time of the frontend that requires these results (for e.g. the gateway bridge).
The L1 deposit indexer starts from a configurable block height and scans blocks for the
CanonicalTransactionChainTransactionEnqueuedevent and adds the deposit transaction details to the database.To be done:
Additional context
Metadata