This repository was archived by the owner on Jan 16, 2026. It is now read-only.
feat(protocol): make fjord_max_sequencer_drift configurable via RollupConfig #3244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
fjord_max_sequencer_driftfield toRollupConfigto allow chains to customize the max sequencer drift value when Fjord is activegranite_channel_timeoutMotivation
Celo chains require a different
FJORD_MAX_SEQUENCER_DRIFTvalue (2892 vs the default 1800). With the default value, ZK proving fails for some historical Celo blocks that exceeded the default max sequencer drift. These blocks were valid and included on the Celo chain, but are rejected as invalid batches when using the defaultFJORD_MAX_SEQUENCER_DRIFT. To support these blocks, Celo chains need to configure thefjord_max_sequencer_drift.Solution
Following the existing pattern established by
granite_channel_timeout, this PR adds afjord_max_sequencer_driftfield toRollupConfigthat:FJORD_MAX_SEQUENCER_DRIFT(1800) if not specified