Skip to content
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

Port internal knowledge base info to doc #998

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

bradleycamacho
Copy link
Member

Ports internal knowledge base info to the Eth/OP differences doc. Adds info on bridging, chain finality, and useful tools.

@bradleycamacho bradleycamacho requested a review from a team as a code owner October 17, 2024 18:21
Copy link

netlify bot commented Oct 17, 2024

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit 7387303
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/671157f598c78a0008c13d53
😎 Deploy Preview https://deploy-preview-998--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.

Copy link
Contributor

coderabbitai bot commented Oct 17, 2024

Walkthrough

The pull request updates the document "Differences between Ethereum and OP Mainnet," adding new sections and content on bridging mechanisms, transaction fees, mempool rules, and chain finality specific to OP Mainnet. It introduces subsections on deposit and withdrawal transactions, expands on transaction fees, clarifies mempool rules, and explains concepts of chain finality. Additionally, a "What's Next" section with links to relevant tools and resources is included.

Changes

File Change Summary
pages/chain/differences.mdx Updated to include sections on Bridging (with subsections on Deposit and Withdrawal Transactions), expanded Transactions section (including Transaction Fees), clarified Mempool Rules, introduced Chain Finality, and added a "What's Next" section.

Possibly related PRs

Suggested labels

documentation

Suggested reviewers

  • cpengilly
  • zainbacchus

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 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: 1

🧹 Outside diff range and nitpick comments (2)
pages/chain/differences.mdx (2)

14-22: Approve changes with minor suggestion

The new Bridging section provides valuable information about deposit and withdrawal transactions, enhancing the document's completeness. The content is clear, concise, and relevant.

Consider adjusting the capitalization in the subheadings for consistency with the coding guidelines:

-### Bridging - Deposit Transactions
+### Bridging - deposit transactions

-### Bridging - Withdrawal Transactions and Fault Proofs
+### Bridging - withdrawal transactions and fault proofs

91-93: Approve Chain Finality section with minor suggestion

The new Chain Finality section provides crucial information about the different states of finality in OP-Stack chains. The content is informative and includes a helpful link to the glossary for more details.

Consider rephrasing the first sentence for clarity:

-Unlike L1s such as Ethereum OP-Stack chains have Unsafe, Safe, and Finalized Heads which indicate the state of finality for a given L2 block.
+Unlike L1s such as Ethereum, OP-Stack chains have Unsafe, Safe, and Finalized Heads, which indicate the state of finality for a given L2 block.
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between e08204f and 952964d.

📒 Files selected for processing (1)
  • pages/chain/differences.mdx (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/chain/differences.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 headers, 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).
  • Use sentence case for H1, H2, and H3 headers, capitalizing only the first word and any proper nouns.
  • For all headers (H1, H2, H3), do not change the capitalization of proper nouns; keep them as they are.
    "
🪛 LanguageTool
pages/chain/differences.mdx

[uncategorized] ~99-~99: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...rs.js for op-stack chains. We had an SDK but that is deprecated now. * [Specs](ht...

(COMMA_COMPOUND_SENTENCE_2)

🔇 Additional comments (2)
pages/chain/differences.mdx (2)

68-69: Approve addition of viem library information

The new information about using the viem library for estimating transaction gas costs is a valuable addition. It provides developers with a practical tool for working with OP Mainnet transactions.


90-90: Approve addition of Sequencer behavior information

The added information about the Sequencer executing transactions from the mempool in priority fee order is valuable. It clarifies an important aspect of transaction processing on OP Mainnet.

Comment on lines 95 to 101
## What's Next

There are various useful tools linked above. Here are a few more tools and links you may want to check out:

* [OP-viem](https://viem.sh/op-stack): JS framework that can handle many of these unique functions on OP-Chains. It is similar to Ethers.js for op-stack chains. We had an SDK but that is deprecated now.

* [Specs](https://specs.optimism.io/root.html): For more in-depth technical explanations and examples.
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Approve What's Next section with minor correction

The new What's Next section is a valuable addition, providing users with links to useful tools and resources for working with OP-Stack chains.

There's a minor grammatical issue in the sentence about the SDK. Please apply the following correction:

-*   [OP-viem](https://viem.sh/op-stack): JS framework that can handle many of these unique functions on OP-Chains. It is similar to Ethers.js for op-stack chains. We had an SDK but that is deprecated now.
+*   [OP-viem](https://viem.sh/op-stack): JS framework that can handle many of these unique functions on OP-Chains. It is similar to Ethers.js for op-stack chains. We had an SDK, but it is deprecated now.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## What's Next
There are various useful tools linked above. Here are a few more tools and links you may want to check out:
* [OP-viem](https://viem.sh/op-stack): JS framework that can handle many of these unique functions on OP-Chains. It is similar to Ethers.js for op-stack chains. We had an SDK but that is deprecated now.
* [Specs](https://specs.optimism.io/root.html): For more in-depth technical explanations and examples.
## What's Next
There are various useful tools linked above. Here are a few more tools and links you may want to check out:
* [OP-viem](https://viem.sh/op-stack): JS framework that can handle many of these unique functions on OP-Chains. It is similar to Ethers.js for op-stack chains. We had an SDK, but it is deprecated now.
* [Specs](https://specs.optimism.io/root.html): For more in-depth technical explanations and examples.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~99-~99: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...rs.js for op-stack chains. We had an SDK but that is deprecated now. * [Specs](ht...

(COMMA_COMPOUND_SENTENCE_2)

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

🧹 Outside diff range and nitpick comments (3)
pages/chain/differences.mdx (3)

68-69: Approve update with minor suggestion

The addition of information about using the viem library for estimating transaction gas costs is valuable. To enhance clarity, consider adding a brief explanation of what the L1 Data Fee is or linking to a relevant section that explains it.

Consider modifying the sentence as follows:

-You can use the [JS library viem](https://viem.sh/op-stack) to estimate the entire transaction gas costs, including the L1 Data Fee.
+You can use the [JS library viem](https://viem.sh/op-stack) to estimate the entire transaction gas costs, including the L1 Data Fee (additional cost for publishing transaction data on L1).

90-91: Approve update with minor grammatical correction

The updated Mempool Rules section provides valuable information about how the OP Mainnet Sequencer mempool differs from Ethereum's. To improve readability, a minor punctuation correction is suggested.

Please apply the following correction:

-The Sequencer executes transactions from the mempool in priority fee order (highest fee first).
+The Sequencer executes transactions from the mempool in priority fee order (highest fee first).

91-93: Approve new Chain Finality section with minor correction

The new Chain Finality section is a valuable addition, introducing important concepts specific to OP-Stack chains. The link to the glossary for more detailed explanations is particularly helpful. To improve clarity, a minor grammatical correction is suggested.

Please apply the following correction:

-Unlike L1s such as Ethereum OP-Stack chains have Unsafe, Safe, and Finalized Heads which indicate the state of finality for a given L2 block.
+Unlike L1s such as Ethereum, OP-Stack chains have Unsafe, Safe, and Finalized Heads, which indicate the state of finality for a given L2 block.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~93-~93: Possible missing comma found.
Context: ... ## Chain Finality Unlike L1s such as Ethereum OP-Stack chains have Unsafe, Safe, and ...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 952964d and 7387303.

📒 Files selected for processing (1)
  • pages/chain/differences.mdx (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/chain/differences.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 headers, 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).
  • Use sentence case for H1, H2, and H3 headers, capitalizing only the first word and any proper nouns.
  • For all headers (H1, H2, H3), do not change the capitalization of proper nouns; keep them as they are.
    "
🪛 LanguageTool
pages/chain/differences.mdx

[uncategorized] ~93-~93: Possible missing comma found.
Context: ... ## Chain Finality Unlike L1s such as Ethereum OP-Stack chains have Unsafe, Safe, and ...

(AI_HYDRA_LEO_MISSING_COMMA)

🔇 Additional comments (2)
pages/chain/differences.mdx (2)

14-22: Excellent addition of the Bridging section

The new Bridging section provides valuable information about deposit and withdrawal transactions, enhancing the document's comprehensiveness. The explanations are clear and concise, and the links to further resources are helpful.


95-101: Approve What's Next section

The new What's Next section is a valuable addition, providing users with links to useful tools and resources for working with OP-Stack chains. The information about OP-viem and the link to the specifications are particularly helpful.

Note: A previous review has already addressed the minor grammatical issue in the sentence about the SDK. Please refer to that comment for the suggested correction.

@sbvegan sbvegan self-assigned this Oct 17, 2024
Copy link
Collaborator

@sbvegan sbvegan left a comment

Choose a reason for hiding this comment

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

This is great, here's what I want to do:

  • Migrate these updates into https://docs.optimism.io/stack/differences
  • Delete this page
  • Add a redirect from this page to the Differences between Ethereum and OP Stack Chains page
  • add this to the MDX header thing at the top:
tags: ["eng-protocol"]

@sbvegan
Copy link
Collaborator

sbvegan commented Oct 17, 2024

This PR fixes: #1000
This PR fixes: #999

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