-
Notifications
You must be signed in to change notification settings - Fork 162
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
why op-node always onto old blocks after recharge batcher #244
Comments
The team is looking into it |
For a while batcher failed to submit batches for having no bnb. After recharging batcher address, op-node shows the log. We found the problem due to batcher having no bnb, so i think if batcher used all bnb would trige the problem. And even stopping batcher, |
How long did the batcher stop submitting to L1 due to insufficient balance? |
4 hours |
what's the config of your SequencerWindowSize? From the log it seems unsafe:2381876 and pending safe:2345040 gap is about 10 hours, If SequencerWindowSize is less than this, it may cause a fork leading to a mismatch |
SequencerWindowSize is 14400 |
Can i fix it? SequencerWindowSize doesn't effect For the problem, |
Forget to charge batcher, after charging batcher restart batcher, op-node always build old headers
The text was updated successfully, but these errors were encountered: