lib: Create simple block watcher without blockstream #27
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
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.
When running this against Arbitrum Goerli, the blockstream cannot really keep up with all the blocks
being generated by Arbitrum.
So what happens is that each iteration gets longer and longer, taking up to 20 hours to reconcile blocks
after leaving it running for a couple days (meaning: no rounds initialized for that period).
This creates a simpler version of the block streamer which doesn't stream blocks at all, it just fetches the
latest and calls the callback if it changed. This is all that the
roundInitializeractually needs, since thecallback just gets the latest block anyway and only uses the number from it.