-
Notifications
You must be signed in to change notification settings - Fork 3k
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
op-batcher: Properly drain state on L2 reorgs #5536
Conversation
|
✅ Deploy Preview for opstack-docs canceled.
|
e5f179d
to
0aff62e
Compare
When a L2 reorg occurs the batcher should close out the pending channel and submit everything that it has before clearing the channel builder. The reason for this is that even though it may be submitting incorrect data it should not leave dangling channels. After the pending state is drained it can begin tracking the new L2 chain.
0aff62e
to
66f9e8e
Compare
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.
LGTM.
This PR has been added to the merge queue, and will be merged soon. |
This PR is next in line to be merged, and will be merged as soon as checks pass. |
Description
When a L2 reorg occurs the batcher should close out the pending channel and submit everything that it has before clearing the channel builder. The reason for this is that even though it may be submitting incorrect data it should not leave dangling channels. After the pending state is drained it can begin tracking the new L2 chain.
Tests
Unfortunately the action tests are not suitable for testing this because they have rewritten the batcher. It might be possible in op-e2e, but I don't see an easy way to trigger a L2 reorg & also asserts that it does this flushing.
Metadata