Skip to content

Update consensus-config.mdx #1688

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

Merged
merged 5 commits into from
Jul 14, 2025
Merged

Conversation

siljapetasch
Copy link
Contributor

@siljapetasch siljapetasch commented Jul 9, 2025

docs: document p2p.sync.onlyreqtostatic flag for restricting sync to static peers
@siljapetasch siljapetasch requested a review from a team as a code owner July 9, 2025 14:36
Copy link

netlify bot commented Jul 9, 2025

Deploy Preview for docs-optimism ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 0bdc7c6
🔍 Latest deploy log https://app.netlify.com/projects/docs-optimism/deploys/686fd6aba0f7800008cf9f28
😎 Deploy Preview https://deploy-preview-1688--docs-optimism.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

coderabbitai bot commented Jul 9, 2025

📝 Walkthrough

Walkthrough

A new configuration option, p2p.sync.onlyreqtostatic, has been added to the consensus layer configuration documentation for op-node. This option allows users to restrict RequestL2Range synchronization requests to only static peers, bypassing non-static peers during synchronization. The documentation update provides the command line flag syntax, an example usage, and the corresponding environment variable. No changes were made to exported or public entities; this update is limited to documentation.

Suggested reviewers

  • krofax

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

🧹 Nitpick comments (1)
pages/operators/node-operators/configuration/consensus-config.mdx (1)

642-646: Indent <Tabs.Tab> rows to match existing style

Every other Tabs block in this file indents the <Tabs.Tab> elements by two spaces.
Aligning these three lines keeps the markup consistent and prevents future lint or style-check noise.

 <Tabs items={['Syntax', 'Example', 'Environment Variable']}>
-<Tabs.Tab>`--p2p.sync.onlyreqtostatic=[true|false]`</Tabs.Tab>
-<Tabs.Tab>`--p2p.sync.onlyreqtostatic=true`</Tabs.Tab>
-<Tabs.Tab>`OP_NODE_P2P_SYNC_ONLYREQTOSTATIC=true`</Tabs.Tab>
+  <Tabs.Tab>`--p2p.sync.onlyreqtostatic=[true|false]`</Tabs.Tab>
+  <Tabs.Tab>`--p2p.sync.onlyreqtostatic=true`</Tabs.Tab>
+  <Tabs.Tab>`OP_NODE_P2P_SYNC_ONLYREQTOSTATIC=true`</Tabs.Tab>
 </Tabs>
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between afe1950 and 4a8fcdf.

📒 Files selected for processing (1)
  • pages/operators/node-operators/configuration/consensus-config.mdx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with the following criter...

**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • First, check the frontmatter section at the top of the file:
    1. For regular pages, ensure ALL these fields are present and not empty:
    ---
    title: [non-empty]
    lang: [non-empty]
    description: [non-empty]
    topic: [non-empty]
    personas: [non-empty array]
    categories: [non-empty array]
    content_type: [valid type]
    ---
    1. For landing pages (index.mdx or files with ), only these fields are required:
    ---
    title: [non-empty]
    lang: [non-empty]
    description: [non-empty]
    topic: [non-empty]
    ---
    1. If any required fields are missing or empty, comment:
      'This file appears to be missing required metadata. Please check keywords.config.yaml for valid options and add the required fields manually. You can validate your changes by running:
    pnpm validate-metadata
    ```'
  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
  • For H1, H2, and H3 headers:
    1. Use sentence case, capitalizing only the first word.
    2. Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
    3. Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
  • Flag any headers that seem to inconsistently apply these rules for manual review.
  • When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
    "

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

  • pages/operators/node-operators/configuration/consensus-config.mdx
🧠 Learnings (2)
📓 Common learnings
Learnt from: qbzzt
PR: ethereum-optimism/docs#1216
File: pages/stack/interop/security.mdx:136-144
Timestamp: 2025-01-08T11:04:45.361Z
Learning: In the ethereum-optimism/docs repository, sections that are commented out in documentation files are intentionally excluded due to accuracy concerns and should not be suggested for inclusion until the information becomes accurate.
Learnt from: smartcontracts
PR: ethereum-optimism/docs#241
File: public/tutorials/standard-bridge-standard-token.sh:3-6
Timestamp: 2024-06-10T19:38:04.907Z
Learning: User `smartcontracts` has requested that `.mdx` files always be reviewed according to the instructions in the `.yaml` configuration file. This preference should be remembered for future interactions.
Learnt from: smartcontracts
PR: ethereum-optimism/docs#241
File: public/tutorials/standard-bridge-standard-token.sh:3-6
Timestamp: 2024-10-13T07:16:50.980Z
Learning: User `smartcontracts` has requested that `.mdx` files always be reviewed according to the instructions in the `.yaml` configuration file. This preference should be remembered for future interactions.
Learnt from: sbvegan
PR: ethereum-optimism/docs#1001
File: pages/builders.mdx:11-12
Timestamp: 2024-10-22T02:58:02.175Z
Learning: Prefer using 'OP Stack' over 'OP Mainnet' in documentation for consistency.
pages/operators/node-operators/configuration/consensus-config.mdx (1)
Learnt from: sbvegan
PR: ethereum-optimism/docs#1001
File: pages/builders.mdx:11-12
Timestamp: 2024-10-22T02:58:02.175Z
Learning: Prefer using 'OP Stack' over 'OP Mainnet' in documentation for consistency.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
  • GitHub Check: pr-workflow
🔇 Additional comments (1)
pages/operators/node-operators/configuration/consensus-config.mdx (1)

639-641: Addition looks good

The new option is clearly explained, avoids pronouns, follows sentence-case, and mirrors the wording style used in nearby options.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

🧹 Nitpick comments (1)
words.txt (1)

269-269: Add ONLYREQTOSTATIC for env-var spelling parity

Many flags in this list include an upper-case form for the corresponding
environment variable (DATADIR, MAXPEERS, etc.).
Consider appending the upper-case variant so spell-checks don’t complain about
OP_NODE_P2P_SYNC_ONLYREQTOSTATIC.

+ONLYREQTOSTATIC
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a8fcdf and 61eb620.

📒 Files selected for processing (1)
  • words.txt (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: qbzzt
PR: ethereum-optimism/docs#1216
File: pages/stack/interop/security.mdx:136-144
Timestamp: 2025-01-08T11:04:45.361Z
Learning: In the ethereum-optimism/docs repository, sections that are commented out in documentation files are intentionally excluded due to accuracy concerns and should not be suggested for inclusion until the information becomes accurate.
Learnt from: smartcontracts
PR: ethereum-optimism/docs#241
File: public/tutorials/standard-bridge-standard-token.sh:3-6
Timestamp: 2024-06-10T19:38:04.907Z
Learning: User `smartcontracts` has requested that `.mdx` files always be reviewed according to the instructions in the `.yaml` configuration file. This preference should be remembered for future interactions.
Learnt from: smartcontracts
PR: ethereum-optimism/docs#241
File: public/tutorials/standard-bridge-standard-token.sh:3-6
Timestamp: 2024-10-13T07:16:50.980Z
Learning: User `smartcontracts` has requested that `.mdx` files always be reviewed according to the instructions in the `.yaml` configuration file. This preference should be remembered for future interactions.
Learnt from: sbvegan
PR: ethereum-optimism/docs#1001
File: pages/builders.mdx:11-12
Timestamp: 2024-10-22T02:58:02.175Z
Learning: Prefer using 'OP Stack' over 'OP Mainnet' in documentation for consistency.
words.txt (1)
Learnt from: sbvegan
PR: ethereum-optimism/docs#1001
File: pages/builders.mdx:11-12
Timestamp: 2024-10-22T02:58:02.175Z
Learning: Prefer using 'OP Stack' over 'OP Mainnet' in documentation for consistency.
🪛 LanguageTool
words.txt

[duplication] ~95-~95: Možný preklep: zopakovali ste slovo
Context: ...r DATADIR Defi Defillama's delegatecall devnet Devnet devnets Devnets devs direnv disabletxpo...

(WORD_REPEAT_RULE)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
  • GitHub Check: pr-workflow
🔇 Additional comments (1)
words.txt (1)

95-95: delegatecall uniqueness verified

Only one occurrence of delegatecall was found in words.txt (line 95). No duplicates are present, so no changes are needed.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6e94e14 and 0bdc7c6.

📒 Files selected for processing (1)
  • words.txt (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: qbzzt
PR: ethereum-optimism/docs#1216
File: pages/stack/interop/security.mdx:136-144
Timestamp: 2025-01-08T11:04:45.361Z
Learning: In the ethereum-optimism/docs repository, sections that are commented out in documentation files are intentionally excluded due to accuracy concerns and should not be suggested for inclusion until the information becomes accurate.
Learnt from: smartcontracts
PR: ethereum-optimism/docs#241
File: public/tutorials/standard-bridge-standard-token.sh:3-6
Timestamp: 2024-06-10T19:38:04.907Z
Learning: User `smartcontracts` has requested that `.mdx` files always be reviewed according to the instructions in the `.yaml` configuration file. This preference should be remembered for future interactions.
Learnt from: smartcontracts
PR: ethereum-optimism/docs#241
File: public/tutorials/standard-bridge-standard-token.sh:3-6
Timestamp: 2024-10-13T07:16:50.980Z
Learning: User `smartcontracts` has requested that `.mdx` files always be reviewed according to the instructions in the `.yaml` configuration file. This preference should be remembered for future interactions.
Learnt from: sbvegan
PR: ethereum-optimism/docs#1001
File: pages/builders.mdx:11-12
Timestamp: 2024-10-22T02:58:02.175Z
Learning: Prefer using 'OP Stack' over 'OP Mainnet' in documentation for consistency.
words.txt (1)
Learnt from: sbvegan
PR: ethereum-optimism/docs#1001
File: pages/builders.mdx:11-12
Timestamp: 2024-10-22T02:58:02.175Z
Learning: Prefer using 'OP Stack' over 'OP Mainnet' in documentation for consistency.
🪛 LanguageTool
words.txt

[duplication] ~96-~96: Možný preklep: zopakovali ste slovo
Context: ...Defillama's delegatecall devnet datadir Devnet devnet Devnets devnets devs direnv DISABLETXPO...

(WORD_REPEAT_RULE)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
  • GitHub Check: pr-workflow
🔇 Additional comments (1)
words.txt (1)

269-270: Addition is fine

onlyreqtostatic is inserted in the correct alphabetical slot and reflects the new flag.

@krofax krofax merged commit 5660366 into ethereum-optimism:main Jul 14, 2025
12 checks passed
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.

2 participants