During a recent incident on sepolia-devnet-0 where proxyd-l1 didn't return any L1 blocks, the network halted. op-node was logging in an infinity loop gigabytes of the same repetitive message for 2 days, thousands per second, those three on repeat:
t=2024-03-25T17:35:43+0000 lvl=eror msg="sequencer failed to start building new block with unclassified error" err="cannot build next L2 block past current L1 origin 0xe294a28445e3a391466ec04d5416d28853614ece9f3c85fd4d19964a039545c4:5540790 by more than sequencer time drift, and failed to find next L1 origin: not found"
t=2024-03-25T17:35:43+0000 lvl=warn msg="Next L2 block time is past the sequencer drift + current origin time" current=0xe294a28445e3a391466ec04d5416d28853614ece9f3c85fd4d19964a039545c4:5540790 current_time=1711148172 l2_head=0x58e6c5de339f21ef6d736d0add7cd1f90d573775fa52fa8887198f53f7df7350:2332362 l2_head_time=1711148772
t=2024-03-25T17:35:43+0000 lvl=eror msg="Error finding next L1 Origin" err="cannot build next L2 block past current L1 origin 0xe294a28445e3a391466ec04d5416d28853614ece9f3c85fd4d19964a039545c4:5540790 by more than sequencer time drift, and failed to find next L1 origin: not found"
During a recent incident on sepolia-devnet-0 where proxyd-l1 didn't return any L1 blocks, the network halted. op-node was logging in an infinity loop gigabytes of the same repetitive message for 2 days, thousands per second, those three on repeat: