Skip to content

adding block time research #1034

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 8 commits into from
Oct 28, 2024
Merged

adding block time research #1034

merged 8 commits into from
Oct 28, 2024

Conversation

sbvegan
Copy link
Collaborator

@sbvegan sbvegan commented Oct 28, 2024

Description

Adding Sunnyside's block time research into the docs site: https://docs.google.com/document/d/13dc1x9Vwc4BOq2M1Z-VNKb7w1xFHEEeeKyZ2nX8YnF4/edit?usp=sharing

@sbvegan sbvegan requested a review from a team as a code owner October 28, 2024 19:45
Copy link

netlify bot commented Oct 28, 2024

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit 3ee02e9
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/67200ab96f2e520008942a0c
😎 Deploy Preview https://deploy-preview-1034--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 28, 2024

Walkthrough

The pull request includes several changes primarily focused on documentation and metadata updates. Notably, a comment in next-env.d.ts has been modified to update a TypeScript configuration URL. Additionally, new metadata keys have been added to JSON files in the pages/stack directory, and a new research document on block time has been introduced. Several existing .mdx files related to the OP Stack have been deleted, streamlining the content available in the documentation.

Changes

File Path Change Summary
next-env.d.ts Updated URL reference in a comment for TypeScript configuration documentation.
pages/stack/_meta.json Added key "research": "Research" to expand metadata for the OP Stack.
pages/stack/research/_meta.json Added key "block-time-research": "Block time research" to enhance research metadata.
pages/stack/operators.mdx File removed: contained information on operators and related topics.
pages/stack/operators/features.mdx File removed: provided information about features in the Optimism ecosystem.
pages/stack/protocol.mdx File removed: overview of various protocol topics.
pages/stack/protocol/fault-proofs.mdx File removed: guide on fault proofs within the Optimism ecosystem.
pages/stack/protocol/features.mdx File removed: overview of features within the Optimism ecosystem.
pages/stack/protocol/interop.mdx File removed: guide on interoperability within the Optimism ecosystem.
pages/stack/protocol/rollup.mdx File removed: guide on the rollup protocol within the Optimism ecosystem.
pages/stack/research/block-time-research.mdx New file added: details research on reducing block time for OP Chains to one second.
words.txt Added new entries: Crosschain, replayor, Sunnyside; removed entry: Proxyd.

Possibly related PRs

  • 3 new node pages #679: This PR involves updating hyperlinks related to node configuration documentation, which is similar to the change in the main PR that updates a URL reference in a TypeScript configuration file.
  • supersim explainer #978: This PR also updates a URL reference in the next-env.d.ts file, aligning with the main PR's focus on modifying a comment within the same file.
  • adding address details for opcm #1028: This PR adds details about the OP Contracts Manager, which may relate to the overall documentation improvements that include URL updates, similar to the changes made in the main PR.

Suggested labels

documentation, flag:merge-pending-release


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
Member

@bradleycamacho bradleycamacho left a comment

Choose a reason for hiding this comment

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

The images made this really hard to read, so I recommended a fix for them. The rest of the content looks fine for the audience who'd read this. GJ! Happy to approve one I take a look at the new preview

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

🧹 Outside diff range and nitpick comments (1)
pages/stack/research/block-time-research.mdx (1)

25-25: Standardize figure caption formatting.

Ensure consistent formatting across all figure captions.

Apply this formatting to all captions:

-**Figure 4:** op-geth / archive node / block 13686867 \~ 15074141
+**Figure 4**: op-geth / archive node / block 13686867 \~ 15074141

Also applies to: 29-29, 35-35, 41-41, 45-45, 51-51

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between be3ff1c and 3bdd0b9.

⛔ Files ignored due to path filters (7)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • public/img/op-stack/protocol/block-time-research-figure-1.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-2.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-3.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-4.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-5.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-6.png is excluded by !**/*.png
📒 Files selected for processing (12)
  • next-env.d.ts (1 hunks)
  • pages/stack/_meta.json (1 hunks)
  • pages/stack/operators.mdx (0 hunks)
  • pages/stack/operators/features.mdx (0 hunks)
  • pages/stack/protocol.mdx (0 hunks)
  • pages/stack/protocol/fault-proofs.mdx (0 hunks)
  • pages/stack/protocol/features.mdx (0 hunks)
  • pages/stack/protocol/interop.mdx (0 hunks)
  • pages/stack/protocol/rollup.mdx (0 hunks)
  • pages/stack/research/_meta.json (1 hunks)
  • pages/stack/research/block-time-research.mdx (1 hunks)
  • words.txt (9 hunks)
💤 Files with no reviewable changes (7)
  • pages/stack/operators.mdx
  • pages/stack/operators/features.mdx
  • pages/stack/protocol.mdx
  • pages/stack/protocol/fault-proofs.mdx
  • pages/stack/protocol/features.mdx
  • pages/stack/protocol/interop.mdx
  • pages/stack/protocol/rollup.mdx
✅ Files skipped from review due to trivial changes (2)
  • next-env.d.ts
  • pages/stack/research/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/research/block-time-research.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/stack/research/block-time-research.mdx

[uncategorized] ~55-~55: The preposition ‘of’ seems more likely in this position.
Context: ... took less than one second in the block on time and include outliers in the next b...

(AI_HYDRA_LEO_REPLACE_ON_OF)

words.txt

[uncategorized] ~356-~356: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...nents subgame subheaders SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's Superchains Superscan Supersim supers...

(DE_PHRASE_REPETITION)

🔇 Additional comments (4)
pages/stack/research/block-time-research.mdx (4)

1-6: LGTM: Metadata section is well-structured.

The metadata section follows proper formatting with appropriate title case, tags, and description.


14-19: LGTM: Method and raw data section is well-referenced.

The section provides clear links to the research methodology and raw data.


59-69: LGTM: Impact analysis is comprehensive.

The section clearly outlines the expected impacts on both verifiers and sequencers.


70-80: LGTM: Limitations and references are well-documented.

The section provides a thorough analysis of limitations and includes relevant references.

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 (4)
words.txt (4)

69-69: Ensure consistent capitalization format.

Consider adding both capitalized and lowercase variants of "Crosschain" to match the pattern used for other terms in the file (e.g., like "Superchain"/"superchain").

 Crosschain
+crosschain

200-200: Add plural form for completeness.

Consider adding the plural form "mitigations" to maintain consistency with other terms that have both singular and plural forms.

 Mitigations
+mitigations

294-295: Consider adding lowercase variant.

For consistency with other entries, consider adding the lowercase variant of "Pyth".

 Pyth
 Pyth's
+pyth

356-356: Consider adding variants for completeness.

Consider adding possessive and lowercase variants of "Sunnyside" for consistency, especially since it's a key term related to the block time research being added.

 Sunnyside
+Sunnyside's
+sunnyside
🧰 Tools
🪛 LanguageTool

[uncategorized] ~356-~356: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...nents subgame subheaders SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's Superchains Superscan Supersim supers...

(DE_PHRASE_REPETITION)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between be3ff1c and b3b8df2.

⛔ Files ignored due to path filters (7)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • public/img/op-stack/protocol/block-time-research-figure-1.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-2.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-3.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-4.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-5.png is excluded by !**/*.png
  • public/img/op-stack/protocol/block-time-research-figure-6.png is excluded by !**/*.png
📒 Files selected for processing (12)
  • next-env.d.ts (1 hunks)
  • pages/stack/_meta.json (1 hunks)
  • pages/stack/operators.mdx (0 hunks)
  • pages/stack/operators/features.mdx (0 hunks)
  • pages/stack/protocol.mdx (0 hunks)
  • pages/stack/protocol/fault-proofs.mdx (0 hunks)
  • pages/stack/protocol/features.mdx (0 hunks)
  • pages/stack/protocol/interop.mdx (0 hunks)
  • pages/stack/protocol/rollup.mdx (0 hunks)
  • pages/stack/research/_meta.json (1 hunks)
  • pages/stack/research/block-time-research.mdx (1 hunks)
  • words.txt (9 hunks)
💤 Files with no reviewable changes (7)
  • pages/stack/operators.mdx
  • pages/stack/operators/features.mdx
  • pages/stack/protocol.mdx
  • pages/stack/protocol/fault-proofs.mdx
  • pages/stack/protocol/features.mdx
  • pages/stack/protocol/interop.mdx
  • pages/stack/protocol/rollup.mdx
✅ Files skipped from review due to trivial changes (2)
  • next-env.d.ts
  • pages/stack/research/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/research/block-time-research.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.
    "
🪛 GitHub Check: lint
pages/stack/research/block-time-research.mdx

[warning] 22-22:
Missing final pipe in table fence


[warning] 24-24:
Misaligned table fence


[warning] 26-26:
Cell should be padded with 1 space, not 2


[warning] 26-26:
Missing final pipe in table fence


[warning] 28-28:
Misaligned table fence


[warning] 32-32:
Cell should be padded with 1 space, not 2


[warning] 32-32:
Missing final pipe in table fence


[warning] 34-34:
Misaligned table fence


[warning] 38-38:
Cell should be padded with 1 space, not 2


[warning] 38-38:
Missing final pipe in table fence

🪛 LanguageTool
words.txt

[uncategorized] ~356-~356: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...nents subgame subheaders SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's Superchains Superscan Supersim supers...

(DE_PHRASE_REPETITION)

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

19-20: LGTM! The metadata structure is well-organized.

The addition of the "research" section follows the established conventions and provides a logical location for the block time research documentation.

words.txt (2)

328-330: LGTM! Complete entry set.

The Sepolia entries are well-structured with all necessary variants (uppercase, title case, and lowercase).


Line range hint 1-403: Verify removal of 'Proxyd' term.

The removal of 'Proxyd' should be verified as it might still be referenced in the documentation.

🧰 Tools
🪛 LanguageTool

[style] ~291-~291: Möchten Sie die modernere Schreibweise „proxid“ verwenden?
Context: ...uctionize productionized Protip Proxied proxyd pseudorandomly Pyth Pyth's QRNG Quickno...

(I_ANSTATT_Y)


[duplication] ~293-~293: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ed Protip Proxied proxyd pseudorandomly Pyth Pyth's QRNG Quicknode quicknode quickstarts ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~296-~296: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... proxyd pseudorandomly Pyth Pyth's QRNG Quicknode quicknode quickstarts RANDAO Regenesis regenesis ...

(GERMAN_WORD_REPEAT_RULE)

pages/stack/research/block-time-research.mdx (5)

1-6: LGTM! Frontmatter metadata is well-structured.

The metadata provides appropriate tags and a clear description.


14-19: LGTM! Method section is clear and well-referenced.

The section provides appropriate links to the test methods and data.


58-68: LGTM! Impact analysis is comprehensive and well-structured.

The section clearly outlines the effects on verifiers and sequencers.


69-79: LGTM! Limitations and references are well-documented.

The section provides clear analysis of potential challenges and includes relevant references.


22-50: ⚠️ Potential issue

Standardize table formatting for figure captions.

The table formatting for figure captions needs to be consistent with Markdown standards.

Following the established format from previous reviews, apply consistent formatting to all figure captions. Ensure:

  • One space padding in cells
  • Proper table fence alignment
  • Final pipe in table fence
🧰 Tools
🪛 GitHub Check: lint

[warning] 22-22:
Missing final pipe in table fence


[warning] 24-24:
Misaligned table fence


[warning] 26-26:
Cell should be padded with 1 space, not 2


[warning] 26-26:
Missing final pipe in table fence


[warning] 28-28:
Misaligned table fence


[warning] 32-32:
Cell should be padded with 1 space, not 2


[warning] 32-32:
Missing final pipe in table fence


[warning] 34-34:
Misaligned table fence


[warning] 38-38:
Cell should be padded with 1 space, not 2


[warning] 38-38:
Missing final pipe in table fence

Copy link
Member

@bradleycamacho bradleycamacho left a comment

Choose a reason for hiding this comment

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

Just applied the linting fixes; looks good to me!

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

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b3b8df2 and 66c9dac.

📒 Files selected for processing (2)
  • pages/stack/research/block-time-research.mdx (1 hunks)
  • words.txt (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/research/block-time-research.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/stack/research/block-time-research.mdx

[uncategorized] ~54-~54: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...he block after the block time, it stops to include the transactions and yields the current...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[uncategorized] ~54-~54: The preposition ‘of’ seems more likely in this position.
Context: ... took less than one second in the block on time and include outliers in the next b...

(AI_HYDRA_LEO_REPLACE_ON_OF)

words.txt

[uncategorized] ~348-~348: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...nents subgame subheaders SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's Superchains Superscan Supersim supers...

(DE_PHRASE_REPETITION)

🔇 Additional comments (5)
words.txt (2)

68-68: LGTM! New terms are valid and correctly placed.

The additions of "Crosschain", "Sunnyside", and "xlarge" are appropriate and properly alphabetized in the word list.

Also applies to: 348-348, 392-392


303-303: Verify spelling: "replayor"

This appears to be a misspelling of "replayer". Please verify if this is intentional or if it should be corrected.

pages/stack/research/block-time-research.mdx (3)

1-6: LGTM: Metadata is well-structured and complete.

The metadata section follows documentation guidelines with appropriate tags and description.


10-12: Skip duplicate comment about personal pronouns.

A previous review has already addressed the use of personal pronouns in this section.


58-68: LGTM: Impact analysis is clear and technically accurate.

The section effectively outlines the implications for both verifiers and sequencers.

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 (1)
words.txt (1)

356-356: Remove duplicate dictionary entries.

There are multiple variations of "Superchain" that appear redundant:

  • "SUPERCHAIN"
  • "Superchain"
  • "superchain"

Consider keeping only the necessary variations to maintain a cleaner dictionary.

Also applies to: 357-359

🧰 Tools
🪛 LanguageTool

[uncategorized] ~356-~356: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...nents subgame subheaders SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's Superchains Superscan Supersim supers...

(DE_PHRASE_REPETITION)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 66c9dac and 3ee02e9.

📒 Files selected for processing (1)
  • words.txt (9 hunks)
🧰 Additional context used
🪛 LanguageTool
words.txt

[uncategorized] ~356-~356: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...nents subgame subheaders SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's Superchains Superscan Supersim supers...

(DE_PHRASE_REPETITION)

🔇 Additional comments (1)
words.txt (1)

14-14: LGTM on new dictionary entries.

The following new entries are valid and relevant to the blockchain/documentation context:

  • Ankr (infrastructure provider)
  • Crosschain (cross-blockchain concept)
  • Immunefi (security platform)
  • Mitigations (technical term)
  • Pyth (oracle network)
  • SEPOLIA (Ethereum testnet)
  • Sunnyside (research contributor)
  • voxel (graphics term)

Also applies to: 69-69, 151-151, 200-200, 294-294, 328-328, 356-356, 398-398

@sbvegan sbvegan merged commit 1351f9f into main Oct 28, 2024
7 of 8 checks passed
@sbvegan sbvegan deleted the block-time-research branch October 28, 2024 22:15
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