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.

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

do not unwind/prune l1 sync data #1072

Merged
merged 1 commit into from
Aug 30, 2024
Merged

do not unwind/prune l1 sync data #1072

merged 1 commit into from
Aug 30, 2024

Conversation

hexoscott
Copy link
Collaborator

As we unwind now on sequencer restart this process can take a long time on each sequencer restart. As we only sync finalised data from the L1 this will not change anyway so no point unwinding it

@cla-bot cla-bot bot added the cla-signed label Aug 29, 2024
As we unwind now on sequencer restart this process can take a long time on each sequencer restart.  As we only sync finalised data from the L1 this will not change anyway so no point unwinding it
Copy link

sonarcloud bot commented Aug 30, 2024

@hexoscott hexoscott merged commit 867e99c into zkevm Aug 30, 2024
10 checks passed
@hexoscott hexoscott deleted the no-unwind-l1-sync branch August 30, 2024 09:20
hexoscott added a commit that referenced this pull request Aug 30, 2024
As we unwind now on sequencer restart this process can take a long time on each sequencer restart.  As we only sync finalised data from the L1 this will not change anyway so no point unwinding it
Stefan-Ethernal pushed a commit that referenced this pull request Sep 20, 2024
As we unwind now on sequencer restart this process can take a long time on each sequencer restart.  As we only sync finalised data from the L1 this will not change anyway so no point unwinding it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants