[OP Stack Deployment] L2 finalized height stuck at 0 #543
Replies: 3 comments 3 replies
-
This is interesting that the safe block is being marked and the finalized is not. Can you please share your:
|
Beta Was this translation helpful? Give feedback.
-
This is because you have |
Beta Was this translation helpful? Give feedback.
-
Have you observed whether the op-node log indicates that L1 may be reorganized or dropped batch? |
Beta Was this translation helpful? Give feedback.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
After running the chain for a few days,
op-node
reports some questionable behaviors:finalized
L2 blocks (see sync status output).safe
height is somewhat consistently 25.3k blocks away fromlatest
block.safe
height, and seemingly unaware of thelatest
blocks produced by the Sequencer node.optimism_syncStatus
returns thesafe
height=unsafe
height.Custom configurations: v1.7.7, Alt-DA (Avail) with Plasma enabled.
L1 Batch Inbox: 0xff00000000000000000000090000000000016481
L2 Explorer: https://sepolia.pivotalscan.xyz/
Setup: 1 sequencer with 3 replicas.
Replica Sync:
syncmode=full
,gcmode=archive
, p2p enabledLogs
No errors/warnings found in the recent logs.
Additional Information
Sequencer `optimism_syncStatus` output
Deploy config
Rollup config
Run Configs
Sequencer Consensus Client Config
Replica Consensus Client Config
Edits:
2024-07-30: added deploy config and rollup json.
2024-08-02: added op-node run configs for sequencer and replica.
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions