fix(docs): Remove op-node Rollup Config CLI Flag #6813
Merged
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
The
op-nodehas been updated to dynamically load the rollup config from the superchain registry. This pr updates the OP Stack Chain docs to specify a network instead of using a static json file. This avoids the need to have arollup.jsonconfig file locally so instead you can just specify the network name.Also note, specifying both the
networkandrollup.configis deprecated in theop-node. See https://github.com/ethereum-optimism/optimism/blob/develop/op-node/service.go#L216-L228