Skip to content
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

syncrhonizer: event initialBatch must have a eventOrder and it's own processor #3318

Closed
joanestebanr opened this issue Feb 20, 2024 · 1 comment · Fixed by #3347 or #3361
Closed

syncrhonizer: event initialBatch must have a eventOrder and it's own processor #3318

joanestebanr opened this issue Feb 20, 2024 · 1 comment · Fixed by #3347 or #3361
Assignees
@joanestebanr
Labels
synchronizer zkevm-bridge-sync-rpc
Milestone
v0.8.0

Comments

@joanestebanr
Copy link
Contributor

Rationale

Currently the event initialSequenceBatch is set as SequenceBatches and inside de processor of sequenced batches check if it's a initialSequence because the batchNumber == 1

Implementation

Separete this event to another processor
@joanestebanr joanestebanr added this to the v0.7.0 milestone Feb 20, 2024
@joanestebanr joanestebanr self-assigned this Feb 20, 2024
@joanestebanr joanestebanr mentioned this issue Feb 28, 2024
Merged
This was linked to pull requests Feb 28, 2024
fix initial sequenced batch event #3347
Merged
cherry-pick: fix initial sequenced batch event (#3347) #3361
Merged
@joanestebanr
Copy link
Contributor Author

included in v0.6.0 and develop

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

@joanestebanr joanestebanr

Labels
synchronizer zkevm-bridge-sync-rpc
Projects
None yet
Milestone
v0.8.0
1 participant
@joanestebanr