-
Notifications
You must be signed in to change notification settings - Fork 178
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
Update create-l2-rollup.mdx #824
Conversation
WalkthroughThe recent changes enhance the configuration options for batchers and proposers in the Optimism framework. Key updates include adjustments to the Changes
Possibly related issues
Recent review detailsConfiguration used: .coderabbit.yaml Files selected for processing (1)
Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
pages/builders/chain-operators/tutorials/create-l2-rollup.mdx (1)
664-670
: Clarify the explanation for--max-channel-duration
.The change to
--max-channel-duration=25
is correct. The explanation in the callout is clear, but consider adding a brief example to illustrate the impact of setting this parameter low versus high.- When it is high, transactions are written to L1 less frequently and the batcher spends less ETH. + For example, when set to 25, transactions are written to L1 less frequently, reducing ETH expenditure by the batcher.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ty simple! lgtm
Description
Removed
--rpc.port=8547
fromop-node
:Use the default value to align with the JSON-RPC API documentation.
Flag description:
--rpc.port value
(default: 9545) ($OP_NODE_RPC_PORT)RPC listening port.
Changed
--max-channel-duration
forop-batcher
:Updated
--max-channel-duration=1
to--max-channel-duration=25
, referencing the corresponding configuration value fromop-sepolia
.Added link target for
--max-channel-duration=n
:Added a link to "Set Your OP_BATCHER_MAX_CHANNEL_DURATION" to provide relevant recommendations.
Updated
op-proposer
command for L1StandardBridgeProxy address:Changed the command from
cat deployments/getting-started/L1StandardBridgeProxy.json | jq -r .address
to
cat ../packages/contracts-bedrock/deployments/getting-started/.deploy | jq -r .L2OutputOracleProxy
as the previous command was no longer valid.
Updated command to retrieve L1StandardBridgeProxy address:
Changed the command from
cat deployments/getting-started/L1StandardBridgeProxy.json | jq -r .address
to
cat deployments/getting-started/.deploy | jq -r .L1StandardBridgeProxy
due to the previous command becoming invalid.
Tests
Please describe any tests you've added. If you've added no tests, or left important behavior untested, please explain why not.
Additional context
Add any other context about the problem you're solving.
Metadata