Skip to content

Conversation

@dailinsubjam
Copy link
Collaborator

@dailinsubjam dailinsubjam commented Mar 28, 2025

Closes https://app.asana.com/0/1209392461754458/1209743779164691/f

This PR:

  • Add L1 origin finalization check on caff node
  • Passed existing tests

This PR does not:

  • Have its own specific test yet

Key places to review:

Usage: "Enable use of only finalized L1 blocks as L1 origin. Overwrites the value of 'sequencer.l1-confs'.",
EnvVars: prefixEnvVars("SEQUENCER_USE_FINALIZED"),
Value: false,
Value: false, // Sishan TODO: So Celo set it to false by default? Do we want to change to true if deriving from caff node?
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to turn it on?

Copy link
Collaborator Author

@dailinsubjam dailinsubjam Mar 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe due to Celo is actively working on it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to turn it on?

Yeah, I think so!

Maybe due to Celo is actively working on it.

Looks like this PR has been merged.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but I guess the reason they haven't turned it on is because later they'll send some other fix relevant to this feature.

Usage: "Enable use of only finalized L1 blocks as L1 origin. Overwrites the value of 'sequencer.l1-confs'.",
EnvVars: prefixEnvVars("SEQUENCER_USE_FINALIZED"),
Value: false,
Value: false, // Sishan TODO: So Celo set it to false by default? Do we want to change to true if deriving from caff node?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to turn it on?

Yeah, I think so!

Maybe due to Celo is actively working on it.

Looks like this PR has been merged.

@dailinsubjam dailinsubjam requested a review from shenkeyao April 1, 2025 16:36
Copy link
Collaborator

@philippecamacho philippecamacho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@shenkeyao shenkeyao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Pasting the note from [Zulip](#eng-integrations-optimism > Review requests @ 💬):

Sishan and I just discussed this PR and concluded that we shouldn't update messagesWithHeights when the L1 status fetch fails. In this way we won't drop the current block, which can then be proceeded when we retry.

A potential issue of doing so is that if the L1 fetch always fails, we'll get stuck. We think this is fine because if we fail to fetch the L1 status for this block, we probably will fail to fetch the status for the next block too. There might be a better way to handle it, which we could discuss later.

@dailinsubjam dailinsubjam merged commit de846c2 into celo-integration Apr 3, 2025
25 of 28 checks passed
@dailinsubjam dailinsubjam deleted the sishan/L1_finalization branch April 4, 2025 19:00
QuentinI pushed a commit that referenced this pull request May 27, 2025
QuentinI pushed a commit that referenced this pull request May 27, 2025
QuentinI pushed a commit that referenced this pull request Jun 18, 2025
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

Successfully merging this pull request may close these issues.

4 participants