You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can have 2 situations for updating the forID:
1- It is a scheduled update and we wait until all the virtual batches are verified.
2- We face problems in a batch and we need to update the forkID.
For the first situation we don't need to add extra logic.
Regarding the second situation:
When a forkID is detected, the synchronizer has to force a trustedReorg. This will force the sequencer to start building batches again using the correct forkID.
If the event has the batchNumber 15, the synchronizer will delete batches after batch 14.
we would also need to delete the proof table for proofs after proof 14
The text was updated successfully, but these errors were encountered:
We can have 2 situations for updating the forID:
1- It is a scheduled update and we wait until all the virtual batches are verified.
2- We face problems in a batch and we need to update the forkID.
For the first situation we don't need to add extra logic.
Regarding the second situation:
When a forkID is detected, the synchronizer has to force a trustedReorg. This will force the sequencer to start building batches again using the correct forkID.
If the event has the batchNumber 15, the synchronizer will delete batches after batch 14.
we would also need to delete the proof table for proofs after proof 14
The text was updated successfully, but these errors were encountered: