feat(l2): add deposit watcher checks #1205
Open
+80
−15
Conversation
This file contains 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
fborello-lambda
approved these changes
Nov 19, 2024
| max_block_step: watcher_config.max_block_step, | ||
| last_block_fetched: U256::zero(), | ||
| l2_proposer_pk: watcher_config.l2_proposer_private_key, | ||
| l2_proposer_address: watcher_config.l2_proposer_address, |
There was a problem hiding this comment.
I think we are not using this variable. Should we remove the variable from the watcher_config and delete the env variable in the .env.example?
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.
Motivation
As L1 watcher may fall down and restart, we need to check if the events read from L1 were already processed or not.
Description
When the L1 watcher reads a new log, it will check pending logs on L1 to ensure it matches.
Closes #1190