finalized block doesn't update when rolling up to an L2 #580
Unanswered
arshsingh
asked this question in
Deploying the OP Stack
Replies: 1 comment
-
I'm trying to do the same thing but every time I try to bridge ETH into the L3, my op-node logs the Also, op-geth updates chain head with a new block about 5 min later, so it seems it should be working. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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?Beta Was this translation helpful? Give feedback.
All reactions