-
Notifications
You must be signed in to change notification settings - Fork 120
fix: Allow for stream event redrive #2283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sergerad
wants to merge
3
commits into
next
Choose a base branch
from
sergerad-stream-redrive
base: next
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+76
−0
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is true.
What is true is that the validator allows replacing the latest block it has personally signed. But such a "replaced" block is never committed and therefore should never be considered the chain tip.
As an example:
Nis proposed andNis now the new committed chain tip and may be sent to downstream subscribersN+1is proposedN+1is proposedN+1is now the new committed chain tip and may be sent to downstreamIn other words, the validators chain tip is irrelevant. It is never streamed. Only the sequencer's committed chain tip is streamed.
A separate concern is what happens if we discover that some block
Mproof fails, or is rejected by L1. Then we need some sort of rollback mechanism but that is a different issue.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use the same machinery for streaming blocks for the validator backup stream and the RPC replica streams. This PR is trying to solve the problem we have ATM where a redriven Validator block would be ignored. So we would potentially have a bad backup (backup contains the wrong version of a block that was overwritten).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The validator should be used for sequencer recovery. In other words, there cannot be a redriven block because there is no sequencer and therefore no new blocks.
Or if you prefer a stricter model - the validator should reject all new blocks while it has a subscription active. But I don't think we need to go that route because, again, this is intended as a last resort data recovery.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though maybe that isn't such a bad idea. Reject all block signing requests with
cannot sign, recovery in progress.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand what this means. The redrive is made by the sequencer in the first place - overwriting the N'th block (next-1).