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

batcher: batchSubmitter.checkExpectedProgress #12430

Draft
wants to merge 1 commit into
base: gk/batcher-node-progress
Choose a base branch
from

Conversation

geoknee
Copy link
Contributor

@geoknee geoknee commented Oct 11, 2024

towards #12124

@geoknee geoknee changed the title implement batchSubmitter.checkExpectedProgress batcher: batchSubmitter.checkExpectedProgress Oct 11, 2024
@geoknee geoknee added this to the Holocene: Derivation milestone Oct 11, 2024
Copy link
Contributor

semgrep-app bot commented Oct 11, 2024

Semgrep found 1 err-todo finding:

  • op-program/client/l2/engineapi/l2_engine_api.go

TODO in error handling code

Ignore this finding from err-todo.

// Set to 1 to allow e.g. 12s for the safe head to advance
// after the L1 inclusion block was ingested.
// TODO extract this into a config variable
// TODO should we also wait numConfirmations (this is a txmgr config variable, not in scope of the batch submitter)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

What we really want to know is the verifier numConfirmations, but I don't think we can get access to that. We probably have to proceed with our own conservative buffer / confirmation depth.

When this is a CLI config variable, it can be set in a coordinated way with how the verifier node / sequencer is configured.

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.

1 participant