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

bug: Archiver reports epoch as complete too early #10800

Closed
spalladino opened this issue Dec 17, 2024 · 0 comments · Fixed by #10801
Closed

bug: Archiver reports epoch as complete too early #10800

spalladino opened this issue Dec 17, 2024 · 0 comments · Fixed by #10801
Assignees
@spalladino

Comments

@spalladino
Copy link
Collaborator

No description provided.

@spalladino spalladino self-assigned this Dec 17, 2024
@spalladino spalladino mentioned this issue Dec 17, 2024
Merged
spalladino added a commit that referenced this issue Dec 18, 2024
@spalladino
fix: Archiver does not jump the gun on epoch completed (#10801)
51d82aa 
Archiver's isEpochComplete would return `true` when the first L1 block
of the last epoch L2 slot was mined, ignoring the fact that the L2 block
could be posted on a later L1 slot.

This fixes the check so it reports the epoch as completed only once the
last L1 block of the last L2 slot of the epoch is mined.

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

@spalladino spalladino

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Archiver does not jump the gun on epoch completed AztecProtocol/aztec-packages
1 participant
@spalladino