[OP Stack Deployment] L1 Origin Stuck at a Certain Block After L1 RPC Downtime

[dev-jb]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I encountered an issue where the L1 origin got stuck at block 15281250 following a period of L1 RPC downtime (approximately 3 hours). During this time, the sequencer encountered an error due to the maxSequencerDrift configuration.

The error message was as follows:

Next L2 block time is past the sequencer drift + current origin time

At the time, I had the maxSequencerDrift parameter set to 10 minutes. To resolve this, I updated the maxSequencerDrift to 4 hours. This allowed the sequencer to start generating new blocks from the last finalized block on L2.

However, even after making this change, the L1 origin remains stuck at block 15281250, and it does not appear to be progressing as expected.

Could this behavior be related to the sequencer configurations such as sequencerWindowSize or other parameters? Or is there a potential issue with the state synchronization process after an extended L1 RPC downtime?

Any guidance on resolving this would be greatly appreciated.

Logs

op-node log:
l1 origin at block 15281250.

op-geth log:

op-batcher log:

op-proposer log:

Additional Information

Rollup config:
Update the max sequencer drift after L1 downtime.
{
...
"block_time": 1,
"max_sequencer_drift": 14400,
"seq_window_size": 600,
"channel_timeout": 600,
...
}

Feedback

No response