fix: cdk node l1infotree sync configuration #380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
While deploying the stack on external L1s like Sepolia using kurtosis-cdk, some users noticed that the cdk node was syncing from genesis instead of syncing from the rollup manager deployment block. It turns out the cdk node configuration is a bit outdated. Some settings are not set, instead, we rely on default values. For example, the L1 InfoTreeSync initial block is set to zero by default which explains why the cdk node syncs from the genesis block. This PR addresses this specific issue.
References (if applicable)
https://discord.com/channels/893151281848406016/1306202853244665867/1306593102902857780