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.

Sign up for GitHub

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

Jump to bottom

Trusted sequencer should be aware of L2 reorgs #796

Closed

4 tasks

arnaubennassar opened this issue Jun 22, 2022 · 1 comment

Closed

4 tasks

Trusted sequencer should be aware of L2 reorgs #796

arnaubennassar opened this issue Jun 22, 2022 · 1 comment

Labels

sequencer synchronizer

Member

arnaubennassar commented Jun 22, 2022

Sequencer should be notified if a L2 reorg happens (trusted state != virtual state) as it may have WIP sequences being built on top of a wrong state.

Synchronizer notifies when a reorg is detected
Trusted sequencer halts operation
Synchronizer notifies when the reorg has been re-processed (this can take a while as it could imply processing a few batches)
Trusted sequencer will most likely need to drop the WIP sequences and then resume operation

arnaubennassar added sequencer synchronizer 2.0 labels

arnaubennassar removed the 2.0 label

Contributor

tclemos commented Aug 5, 2022

@arnaubennassar how is the state of this task after your Sequencer refactoring?

Mikelle mentioned this issue

Implement L2 reorg on sequencer level #1065

Closed

arnaubennassar closed this as completed

tony-armstrong mentioned this issue

fatal error: TRUSTED REORG DETECTED b2network/b2-zkevm-node#23

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment