Skip to content

Page for reorgs and sequencing errors #1277

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 14 commits into from
Feb 14, 2025
Merged

Conversation

qbzzt
Copy link
Contributor

@qbzzt qbzzt commented Jan 24, 2025

Description

A page about reorgs, and how we can survive them while doing 1 block asset transfers

Tests

N/A

Additional context

N/A

Metadata

N/A

Copy link

netlify bot commented Jan 24, 2025

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit df30b6f
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/67af5fddbdc4f0000875d450
😎 Deploy Preview https://deploy-preview-1277--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 site configuration.

@qbzzt qbzzt marked this pull request as ready for review January 24, 2025 16:09
@qbzzt qbzzt requested a review from a team as a code owner January 24, 2025 16:09
Copy link
Contributor

coderabbitai bot commented Jan 24, 2025

📝 Walkthrough

Walkthrough

This pull request introduces a new entry in the _meta.json file by adding the key "reorg" with the value "Interop reorg awareness", which enhances the metadata related to interoperability functionalities. Additionally, a new markdown file titled reorg.mdx is created, detailing how Superchain interoperability enables low-latency cross-chain communication while addressing the double-spend problem. The document defines chain reorganizations (reorgs), critiques common solutions such as waiting for Ethereum finality, and explains the implications of double spending when transactions are invalidated due to reorgs. It also discusses block safety levels, the invisibility of L1 reorgs to L2, and the concept of equivocation, concluding with potential causes of invalid blocks and their effects on transaction integrity.

Possibly related PRs

  • Moved interop tutorials to their own directory #1253: The changes in the main PR, which involve adding a new key to the JSON metadata for interop awareness, are related to the modifications in the retrieved PR that also involve changes to the same JSON file, specifically the _meta.json file, albeit with different key-value pairs.
  • docs(interop/architecture): first version #1181: The changes in the main PR, which involve adding a new key to the metadata JSON for interop awareness, are related to the retrieved PR's addition of a key for architecture in the same metadata file, indicating a shared focus on enhancing interop documentation.

Suggested labels

documentation

Suggested reviewers

  • zainbacchus
  • bradleycamacho

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?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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: 2

🧹 Nitpick comments (3)
pages/stack/interop/sequencing.mdx (3)

1-11: Consider enhancing the description for better clarity.

The current description could be more specific about the content. Consider expanding it to mention reorgs and block safety levels.

-description: How interop avoids the double-spending problem.
+description: Learn about blockchain reorganizations, sequencing errors, and how interop prevents double-spending through block safety levels.

151-151: Improve technical accuracy with correct preposition.

When referring to posting blocks, use "to L1" instead of "on L1".

-If a block is invalid, even if it is posted on L1, the canonical chain replaces it with a block that only includes the deposit transactions, those transactions posted to L1.
+If a block is invalid, even if it is posted to L1, the canonical chain replaces it with a block that only includes the deposit transactions, those transactions posted to L1.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~151-~151: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


169-169: Improve readability with proper punctuation.

Add a comma to separate independent clauses.

-In this case an L1 block is replaced and the new block either contains the same blob with chain data that was contained in the old block or it doesn't.
+In this case, an L1 block is replaced, and the new block either contains the same blob with chain data that was contained in the old block, or it doesn't.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~169-~169: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c1d920b and ddd4356.

📒 Files selected for processing (2)
  • pages/stack/interop/_meta.json (1 hunks)
  • pages/stack/interop/sequencing.mdx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/interop/sequencing.mdx (1)

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

  • 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.
    "
🪛 LanguageTool
pages/stack/interop/sequencing.mdx

[uncategorized] ~36-~36: Possible missing comma found.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_HYDRA_LEO_MISSING_COMMA)


[grammar] ~56-~56: The plural noun “phenomena” cannot be used with the article “a”. Did you mean “a transient phenomenon”?
Context: ... In Ethereum incorrect state is usually a transient phenomena. If a sequencer equivocates (sends one ...

(A_NNS)


[style] ~63-~63: To strengthen your wording, consider using a synonym for ‘bad’.
Context: ...ridge/withdraw) works. That solution is really bad from the usability perspective. ## Blo...

(EXTREME_ADJECTIVES)


[grammar] ~102-~102: The pronoun ‘they’ must be used with a non-third-person form of a verb.
Context: ...e of them are cross-safe because they depends on a block that isn't. If all goes wel...

(NON3PRS_VERB)


[uncategorized] ~146-~146: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~151-~151: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~161-~161: Possible missing comma found.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_HYDRA_LEO_MISSING_COMMA)


[formatting] ~168-~168: Consider inserting a comma after an introductory phrase for better readability.
Context: ...s but only those blocks. ### L1 reorg In this case an L1 block is replaced and the new blo...

(IN_THAT_CASE_COMMA)


[uncategorized] ~169-~169: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


[grammar] ~171-~171: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)

🔇 Additional comments (3)
pages/stack/interop/_meta.json (1)

8-8: LGTM!

The new entry follows the existing pattern and is correctly positioned in the file.

pages/stack/interop/sequencing.mdx (2)

108-148: LGTM!

The explanation of equivocation is clear, accurate, and well-illustrated with the diagram.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~146-~146: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


175-179: LGTM!

The explanation of L2 reorgs is clear and technically accurate.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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 (6)
pages/stack/interop/sequencing.mdx (6)

36-36: Add missing comma for better readability.

-In a normal asset transfer tokens are burned on the source chain first
+In a normal asset transfer, tokens are burned on the source chain first
🧰 Tools
🪛 LanguageTool

[uncategorized] ~36-~36: A comma might be missing here.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


63-63: Consider using more formal language.

-That solution is really bad from the usability perspective.
+That solution significantly impacts usability.
🧰 Tools
🪛 LanguageTool

[style] ~63-~63: To strengthen your wording, consider using a synonym for ‘bad’.
Context: ...ridge/withdraw) works. That solution is really bad from the usability perspective. ## Blo...

(EXTREME_ADJECTIVES)


159-159: Fix typo in the word "incorrect".

-The block posted to L1 includes incorret information
+The block posted to L1 includes incorrect information
🧰 Tools
🪛 LanguageTool

[uncategorized] ~159-~159: A comma might be missing here.
Context: ...o L1 includes incorret information, for example because it relied on a node on a differ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


161-161: Add missing comma after the time expression.

-After a timeout of twelve hours all the verifiers will assume
+After a timeout of twelve hours, all the verifiers will assume
🧰 Tools
🪛 LanguageTool

[uncategorized] ~161-~161: A comma might be missing here.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


169-169: Add missing comma in compound sentence.

-that was contained in the old block or it doesn't
+that was contained in the old block, or it doesn't
🧰 Tools
🪛 LanguageTool

[uncategorized] ~169-~169: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


171-171: Fix verb tense for parallel structure.

-the sequencer on the chain will know it is missing and repost it
+the sequencer on the chain will know it is missing and reposts it
🧰 Tools
🪛 LanguageTool

[grammar] ~171-~171: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ddd4356 and d1b150c.

📒 Files selected for processing (1)
  • pages/stack/interop/sequencing.mdx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/interop/sequencing.mdx (1)

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

  • 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.
    "
🪛 LanguageTool
pages/stack/interop/sequencing.mdx

[uncategorized] ~36-~36: A comma might be missing here.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[style] ~63-~63: To strengthen your wording, consider using a synonym for ‘bad’.
Context: ...ridge/withdraw) works. That solution is really bad from the usability perspective. ## Blo...

(EXTREME_ADJECTIVES)


[uncategorized] ~146-~146: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~151-~151: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~159-~159: A comma might be missing here.
Context: ...o L1 includes incorret information, for example because it relied on a node on a differ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~161-~161: A comma might be missing here.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[formatting] ~168-~168: Consider inserting a comma after an introductory phrase for better readability.
Context: ...s but only those blocks. ### L1 reorg In this case an L1 block is replaced and the new blo...

(IN_THAT_CASE_COMMA)


[uncategorized] ~169-~169: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


[grammar] ~171-~171: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
🔇 Additional comments (1)
pages/stack/interop/sequencing.mdx (1)

1-13: LGTM!

The frontmatter and imports are properly structured.

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 (6)
pages/stack/interop/reorg.mdx (6)

1-4: Update title to use proper capitalization.

The title should capitalize "Interop" as it's a proper noun.

-title: Interop reorg awareness
+title: OP Stack Interop reorg awareness

52-52: Fix grammatical error in double-spending explanation.

The sentence is missing the verb "are".

-When that happens, the tokens are still on the source chain, but they also on the destination chain.
+When that happens, the tokens are still on the source chain, but they are also on the destination chain.

66-66: Add missing comma for better readability.

Add a comma before "preventing" to separate the clauses.

-This means users can transfer assets across chains in the Superchain with 1-block latency, and should a reorg happen, both the source and destination transaction would revert preventing a double spend problem.
+This means users can transfer assets across chains in the Superchain with 1-block latency, and should a reorg happen, both the source and destination transaction would revert, preventing a double spend problem.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~66-~66: A comma might be missing here.
Context: ...ource and destination transaction would revert preventing a double spend problem. {/*...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


68-102: Consider removing or uncommenting the diagram section.

There's a large commented-out mermaid diagram section. Either remove it if it's no longer needed or uncomment it if it provides valuable information.


185-185: Fix typo and improve readability.

There's a typo in "incorret" and the sentence needs better punctuation.

-The block posted to L1 includes incorret information, for example because it relied on a node on a different blockchain for interop and that node reported incorrect information.
+The block posted to L1 includes incorrect information, for example, because it relied on a node on a different blockchain for interop, and that node reported incorrect information.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~185-~185: A comma might be missing here.
Context: ...o L1 includes incorret information, for example because it relied on a node on a differ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


201-207: Consider removing commented-out section about L2 reorg.

There's a commented-out section about L2 reorg. If this information is not ready for publication, consider removing it or adding a TODO comment explaining when it will be added.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d1b150c and 70d6d86.

📒 Files selected for processing (2)
  • pages/stack/interop/_meta.json (1 hunks)
  • pages/stack/interop/reorg.mdx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/stack/interop/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/interop/reorg.mdx (1)

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

  • 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.
    "
🪛 LanguageTool
pages/stack/interop/reorg.mdx

[uncategorized] ~36-~36: A comma might be missing here.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~59-~59: Possible missing article found.
Context: ...orrect block for the blockchain. On L1, new block can be replaced through a reorg, ...

(AI_HYDRA_LEO_MISSING_THE)


[uncategorized] ~66-~66: A comma might be missing here.
Context: ...ource and destination transaction would revert preventing a double spend problem. {/*...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~172-~172: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~177-~177: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~185-~185: A comma might be missing here.
Context: ...o L1 includes incorret information, for example because it relied on a node on a differ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~187-~187: A comma might be missing here.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[formatting] ~194-~194: Consider inserting a comma after an introductory phrase for better readability.
Context: ...s but only those blocks. ### L1 reorg In this case an L1 block is replaced and the new blo...

(IN_THAT_CASE_COMMA)


[uncategorized] ~195-~195: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


[grammar] ~197-~197: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
🔇 Additional comments (1)
pages/stack/interop/reorg.mdx (1)

1-207: Overall document structure and content look good!

The document provides a clear and comprehensive explanation of reorgs and sequencing errors. The technical content is accurate, and the mermaid diagrams effectively illustrate the concepts. After addressing the minor grammar and formatting issues, this will be a valuable addition to the documentation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~36-~36: A comma might be missing here.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~59-~59: Possible missing article found.
Context: ...orrect block for the blockchain. On L1, new block can be replaced through a reorg, ...

(AI_HYDRA_LEO_MISSING_THE)


[uncategorized] ~66-~66: A comma might be missing here.
Context: ...ource and destination transaction would revert preventing a double spend problem. {/*...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~172-~172: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~177-~177: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~185-~185: A comma might be missing here.
Context: ...o L1 includes incorret information, for example because it relied on a node on a differ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~187-~187: A comma might be missing here.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[formatting] ~194-~194: Consider inserting a comma after an introductory phrase for better readability.
Context: ...s but only those blocks. ### L1 reorg In this case an L1 block is replaced and the new blo...

(IN_THAT_CASE_COMMA)


[uncategorized] ~195-~195: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


[grammar] ~197-~197: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)

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 (5)
pages/stack/interop/reorg.mdx (5)

36-37: Fix grammar: Add missing comma.

Add a comma after "transfer" for better readability.

-In a normal asset transfer tokens are burned on the source chain first, then a message is sent to the destination chain.
+In a normal asset transfer, tokens are burned on the source chain first, then a message is sent to the destination chain.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~36-~36: Possible missing comma found.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_HYDRA_LEO_MISSING_COMMA)


52-52: Fix grammar: Add missing verb.

Add the missing verb "are" in the sentence.

-When that happens, the tokens are still on the source chain, but they also on the destination chain.
+When that happens, the tokens are still on the source chain, but they are also on the destination chain.

137-137: Fix grammar issues in L1 reorg section.

  1. Add a comma before "or" in line 137.
  2. Fix verb agreement in line 139.
-In this case an L1 block is replaced and the new block either contains the same blob with chain data that was contained in the old block or it doesn't.
+In this case an L1 block is replaced and the new block either contains the same blob with chain data that was contained in the old block, or it doesn't.

-If the new block does not contain the same blob, then the sequencer on the chain will know it is missing and repost it.
+If the new block does not contain the same blob, then the sequencer on the chain will know it is missing and reposts it.

Also applies to: 139-139

🧰 Tools
🪛 LanguageTool

[uncategorized] ~137-~137: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


145-145: Fix grammar: Correct noun/verb agreement.

The word "Sequencer" should be plural as it refers to multiple sequencers in the system.

-Sequencer inform the rest of the Superchain about a new block in two ways:
+Sequencers inform the rest of the Superchain about a new block in two ways:
🧰 Tools
🪛 LanguageTool

[grammar] ~145-~145: There seems to be a noun/verb agreement error. Did you mean “informs” or “informed”?
Context: ...ble to L2. ### Equivocation Sequencer inform the rest of the Superchain about a new ...

(SINGULAR_NOUN_VERB_AGREEMENT)


202-202: Fix spelling and grammar issues in invalid block section.

  1. Fix the spelling of "incorrect" in line 202.
  2. Add a comma after the time phrase in line 204.
-The block posted to L1 includes incorret information, for example because it relied on a node on a different blockchain for interop and that node reported incorrect information.
+The block posted to L1 includes incorrect information, for example because it relied on a node on a different blockchain for interop and that node reported incorrect information.

-After a timeout of twelve hours all the verifiers will assume that the block that should have been posted is a deposit-only block.
+After a timeout of twelve hours, all the verifiers will assume that the block that should have been posted is a deposit-only block.

Also applies to: 204-204

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 70d6d86 and 95289cf.

📒 Files selected for processing (1)
  • pages/stack/interop/reorg.mdx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/interop/reorg.mdx (1)

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

  • 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.
    "
🪛 LanguageTool
pages/stack/interop/reorg.mdx

[uncategorized] ~36-~36: Possible missing comma found.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~59-~59: Possible missing article found.
Context: ...e blockchain, barring L1 reorgs. On L1, new block can be replaced through a reorg, ...

(AI_HYDRA_LEO_MISSING_THE)


[formatting] ~136-~136: Consider inserting a comma after an introductory phrase for better readability.
Context: ...e destination chain (B). ### L1 reorg In this case an L1 block is replaced and the new blo...

(IN_THAT_CASE_COMMA)


[uncategorized] ~137-~137: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


[grammar] ~139-~139: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)


[grammar] ~145-~145: There seems to be a noun/verb agreement error. Did you mean “informs” or “informed”?
Context: ...ble to L2. ### Equivocation Sequencer inform the rest of the Superchain about a new ...

(SINGULAR_NOUN_VERB_AGREEMENT)


[uncategorized] ~189-~189: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~194-~194: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~204-~204: Possible missing comma found.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_HYDRA_LEO_MISSING_COMMA)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
🔇 Additional comments (3)
pages/stack/interop/reorg.mdx (3)

1-13: LGTM!

The frontmatter is well-structured with appropriate metadata, and all necessary components are properly imported.


69-103: Verify if the commented diagram should be removed.

There's a commented-out mermaid diagram that appears to be more complex than the current one. Please verify if this should be removed or uncommented.


210-216: Verify if the commented L2 reorg section should be removed.

There's a commented-out section about L2 reorgs. Please verify if this should be removed or uncommented for the current documentation.

@qbzzt qbzzt requested a review from zainbacchus February 11, 2025 20:11
@qbzzt qbzzt requested a review from zainbacchus February 13, 2025 21:29
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: 3

🧹 Nitpick comments (2)
pages/stack/interop/reorg.mdx (2)

16-18: Improve clarity and formality in the introduction.

Replace personal pronouns and improve sentence structure for better clarity:

-[A chain reorganization, or "reorg",](https://www.alchemy.com/overviews/what-is-a-reorg#what-happens-to-reorgs-after-the-merge) happens when validators disagree on the most accurate version of the blockchain.
-If not handled correctly, reorgs in a cross-chain context could result in a [double-spend problem](https://en.wikipedia.org/wiki/Double-spending). 
-The most frequent solution to mitigate the double-spend problem is to wait for Ethereum finality; however, that solution results in high latency cross-chain communication and a poor user experience.
+[A chain reorganization, or "reorg",](https://www.alchemy.com/overviews/what-is-a-reorg#what-happens-to-reorgs-after-the-merge) occurs when validators disagree on the most accurate version of the blockchain.
+Chain reorganizations in a cross-chain context can result in a [double-spend problem](https://en.wikipedia.org/wiki/Double-spending) without proper handling. 
+While waiting for Ethereum finality is the most common mitigation strategy, this approach leads to high latency in cross-chain communication and degrades the user experience.

164-164: Add missing comma after introductory phrase.

-After a timeout of twelve hours all the verifiers will assume that the block that should have been posted is a deposit-only block.
+After a timeout of twelve hours, all the verifiers will assume that the block that should have been posted is a deposit-only block.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~164-~164: Possible missing comma found.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 95289cf and d2b23a7.

📒 Files selected for processing (2)
  • pages/stack/interop/_meta.json (1 hunks)
  • pages/stack/interop/reorg.mdx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/stack/interop/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...

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

  • 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.
    "
  • pages/stack/interop/reorg.mdx
🪛 LanguageTool
pages/stack/interop/reorg.mdx

[formatting] ~96-~96: Consider inserting a comma after an introductory phrase for better readability.
Context: ...e destination chain (B). ### L1 reorg In this case an L1 block is replaced and the new blo...

(IN_THAT_CASE_COMMA)


[uncategorized] ~97-~97: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...data that was contained in the old block or it doesn't. If the new block contains t...

(COMMA_COMPOUND_SENTENCE)


[grammar] ~99-~99: Did you mean the verb “reposts”? For a parallel structure in formal text, use “it reposts”, because ‘missing’ is an adjective.
Context: ...n the chain will know it is missing and repost it. So L1 reorgs are basically invisib...

(PRP_IS_JJ_AND_VB)


[grammar] ~105-~105: There seems to be a noun/verb agreement error. Did you mean “informs” or “informed”?
Context: ...ble to L2. ### Equivocation Sequencer inform the rest of the Superchain about a new ...

(SINGULAR_NOUN_VERB_AGREEMENT)


[uncategorized] ~164-~164: Possible missing comma found.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_HYDRA_LEO_MISSING_COMMA)

🔇 Additional comments (2)
pages/stack/interop/reorg.mdx (2)

170-176: Consider including L2 reorg information.

The commented-out section about L2 reorgs contains valuable information about decentralized sequencers. Consider including this information if it's relevant to the current state of the documentation.


178-182: LGTM! Clear and actionable next steps.

The next steps section provides clear guidance for users to continue their learning journey.

krofax and others added 4 commits February 14, 2025 13:45
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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 (3)
pages/stack/interop/reorg.mdx (3)

37-38: Fix grammar in asset transfer explanation.

Add a comma after "transfer" for better readability.

-In a normal asset transfer tokens are burned on the source chain first, then a message is sent to the destination chain.
+In a normal asset transfer, tokens are burned on the source chain first, then a message is sent to the destination chain.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~37-~37: Possible missing comma found.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_HYDRA_LEO_MISSING_COMMA)


149-150: Fix punctuation in block dependency explanation.

Add a comma for better readability.

-Note that a block can only depend directly on a block in a separate chain if the block includes an executing message that uses an initiating message from that block.
+Note that a block can only depend directly on a block in a separate chain if the block includes an executing message that uses an initiating message from that block.
So the change from A<sub>101</sub> to A'<sub>101</sub> cannot invalidate any existing safe blocks.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~149-~149: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


154-154: Improve preposition usage.

Replace "on" with "to" for better clarity.

-If a block is invalid, even if it is posted on L1, the canonical chain replaces it with a block that only includes the deposit transactions, those transactions posted to L1.
+If a block is invalid, even if it is posted to L1, the canonical chain replaces it with a block that only includes the deposit transactions, those transactions posted to L1.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~154-~154: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d2b23a7 and e8182eb.

📒 Files selected for processing (1)
  • pages/stack/interop/reorg.mdx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...

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

  • 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.
    "
  • pages/stack/interop/reorg.mdx
🪛 LanguageTool
pages/stack/interop/reorg.mdx

[uncategorized] ~37-~37: Possible missing comma found.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~149-~149: Possible missing comma found.
Context: ... an initiating message from that block. So the change from A101 to A'<s...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~154-~154: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)

🔇 Additional comments (6)
pages/stack/interop/reorg.mdx (6)

1-13: LGTM!

The frontmatter and imports are properly structured.


14-62: LGTM!

The introduction and double-spending explanation are clear, well-structured, and effectively illustrated with diagrams.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~37-~37: Possible missing comma found.
Context: ... minted) end ``` In a normal asset transfer tokens are burned on the source chain f...

(AI_HYDRA_LEO_MISSING_COMMA)


63-94: LGTM!

The block safety levels section effectively explains the concepts using clear diagrams and precise explanations.


97-99: Fix grammar and punctuation in L1 reorg explanation.

-In this case, an L1 block is replaced, and the new block either contains the same blob with chain data that was contained in the old block, or it doesn't.
-If the new block contains the same blob, the change is meaningless from the L2 perspective.
-If the new block does not contain the same blob, then the sequencer on the chain will know it is missing and repost it.
+In this case, an L1 block is replaced, and the new block either contains the same blob with chain data that was contained in the old block, or it doesn't.
+If the new block contains the same blob, the change is meaningless from the L2 perspective.
+If the new block does not contain the same blob, then the sequencer on the chain will know it is missing and reposts it.

105-105: Fix subject-verb agreement.

-Sequencer inform the rest of the Superchain about a new block in two ways:
+Sequencers inform the rest of the Superchain about a new block in two ways:

178-182: LGTM!

The next steps section provides clear guidance with proper links.

Co-authored-by: Blessing Krofegha <bkrofegha@gmail.com>
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 (4)
pages/stack/interop/reorg.mdx (4)

2-2: Ensure title case consistency with H1 header.

The title in the frontmatter should match the H1 header's sentence case: "Interop reorg awareness".

-title: Interop reorg awareness
+title: Interop reorg awareness

37-38: Improve grammar and readability.

Add proper punctuation to enhance readability.

-In a normal asset transfer tokens are burned on the source chain first, then a message is sent to the destination chain.
+In a normal asset transfer, tokens are burned on the source chain first, then a message is sent to the destination chain.

97-99: Fix grammar and punctuation.

-In this case, an L1 block is replaced, and the new block either contains the same blob with chain data that was contained in the old block, or it doesn't.
-If the new block does not contain the same blob, then the sequencer on the chain will know it is missing and reposts it.
+In this case, an L1 block is replaced, and the new block either contains the same blob with chain data that was contained in the old block or it doesn't.
+If the new block does not contain the same blob, then the sequencer on the chain will know it is missing and repost it.

164-164: Fix punctuation.

Add a comma after the time duration for better readability.

-After a timeout of twelve hours all the verifiers will assume that the block that should have been posted is a deposit-only block.
+After a timeout of twelve hours, all the verifiers will assume that the block that should have been posted is a deposit-only block.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~164-~164: Possible missing comma found.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e8182eb and df30b6f.

📒 Files selected for processing (2)
  • pages/stack/interop/_meta.json (1 hunks)
  • pages/stack/interop/reorg.mdx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/stack/interop/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...

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

  • 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.
    "
  • pages/stack/interop/reorg.mdx
🪛 LanguageTool
pages/stack/interop/reorg.mdx

[uncategorized] ~154-~154: The preposition ‘to’ seems more likely in this position.
Context: ... block is invalid, even if it is posted on L1, the canonical chain replaces it wit...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~164-~164: Possible missing comma found.
Context: ...ver posted. After a timeout of twelve hours all the verifiers will assume that the ...

(AI_HYDRA_LEO_MISSING_COMMA)

🔇 Additional comments (3)
pages/stack/interop/reorg.mdx (3)

89-89: Clarify technical terms.

The terms "local-safe" and "cross-safe" are introduced without prior definition. Consider adding brief explanations or linking to documentation that defines these terms.


107-108: Add context about the gossip protocol.

Consider adding a link to documentation explaining the gossip protocol or briefly explaining how it works in the context of the Superchain.


178-182: LGTM!

The next steps section provides clear and relevant links for further learning.

@krofax krofax merged commit f84e1ad into ethereum-optimism:main Feb 14, 2025
4 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.

4 participants