You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're deploying an op-stack chain as an L3 rolling up to Base, but the l2_finalized block only updates when op-node is restarted.
The value of finalityLookback is currently hard-coded to 4*32 + 1, which If my understanding is correct doesn't work well when rolling up to an L2, because a finalization event there can take 4*32*6 blocks, or longer depending on the L2's configuration.
Deploying with v1.7.4, I keep seeing the following error in the logs:
received L1 finality signal, but missing data for immediate L2 finalization
I deployed op-node with an increased value for finalityLookback and I don't see this issue anymore. Blocks are finalizing and the error message disappeared from the logs.
Would it be possible to make finalityLookback configurable?
The text was updated successfully, but these errors were encountered:
We're deploying an op-stack chain as an L3 rolling up to Base, but the l2_finalized block only updates when op-node is restarted.
The value of finalityLookback is currently hard-coded to
4*32 + 1
, which If my understanding is correct doesn't work well when rolling up to an L2, because a finalization event there can take4*32*6
blocks, or longer depending on the L2's configuration.Deploying with
v1.7.4
, I keep seeing the following error in the logs:I deployed op-node with an increased value for finalityLookback and I don't see this issue anymore. Blocks are finalizing and the error message disappeared from the logs.
Would it be possible to make
finalityLookback
configurable?The text was updated successfully, but these errors were encountered: