Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

finalized block doesn't update when rolling up to an L2 #10380

Open
arshsingh opened this issue May 2, 2024 · 0 comments
Open

finalized block doesn't update when rolling up to an L2 #10380

arshsingh opened this issue May 2, 2024 · 0 comments

Comments

@arshsingh
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant