docs: add OpenChainBench RPC latency benchmark reference - #149
docs: add OpenChainBench RPC latency benchmark reference#149Flotapponnier wants to merge 3 commits into
Conversation
📝 WalkthroughWalkthroughThe documentation adds security audit details, replaces the roadmap structure with quarterly milestones, and updates RPC service documentation with a QuickNode asset and an OpenChainBench latency link. ChangesDocumentation refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1⚔️ Resolve merge conflicts 💡
🧪 Generate unit tests (beta)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/about-morph/4-morphs-architecture.md`:
- Around line 64-68: Update the “Open-Source Codebase” text near the “Morph
Contracts” link to make its scope explicit by describing the publicly available
content as the smart-contract codebase, or change the link target to the
repository root.
- Around line 81-83: Update the “Audit Scope” section to remove the claim that
the audits cover the entire codebase or bridge contract. Verify the separately
documented Trail of Bits scope and replace the sentence with wording that
accurately limits coverage to the specifically audited components and pinned
contract files.
In `@docs/about-morph/6-roadmap.md`:
- Around line 15-32: Update the roadmap sections for 2024 Q1, 2024 Q2, 2024 Q4,
and 2025 Q1 to clearly mark their milestones as completed historical items, or
replace them with current and future quarters that include milestone status; do
not present these past quarters as active roadmap work.
In
`@docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/2-rpc-services.md`:
- Line 14: Update the QuickNode Partnership link in the RPC services developer
resources documentation to use the current canonical benefits page, replacing
the broken URL while preserving the existing link text and surrounding content.
- Line 6: Correct the provider heading hierarchy in the documentation by
changing the QuickNode and OpenChainBench headings to the expected h2 level, and
update Tenderly to the same sibling level so all provider sections are
consistent.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 845b751c-cc9e-41c5-bf1c-00cbae9378da
⛔ Files ignored due to path filters (1)
assets/docs/about/roadmap/roadmap.pngis excluded by!**/*.png
📒 Files selected for processing (3)
docs/about-morph/4-morphs-architecture.mddocs/about-morph/6-roadmap.mddocs/build-on-morph/developer-resources/use-ecosystem-developer-tools/2-rpc-services.md
| ### Open-Source Codebase: | ||
|
|
||
| We’re proud to make our codebase publicly available, inviting scrutiny and contributions from the community. You can review it at the following links: | ||
|
|
||
| [Morph Contracts](https://github.com/morph-l2/morph/tree/main/contracts) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Make the open-source link scope explicit.
The text says the entire codebase is publicly available, but the link targets the contracts subdirectory. GitHub identifies that directory as the Morph smart-contract package and on-chain component. (github.com)
Change the text to smart-contract codebase, or link to the repository root.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/about-morph/4-morphs-architecture.md` around lines 64 - 68, Update the
“Open-Source Codebase” text near the “Morph Contracts” link to make its scope
explicit by describing the publicly available content as the smart-contract
codebase, or change the link target to the repository root.
| ### Audit Scope: | ||
|
|
||
| The above audit reports cover the entirety of our codebase, including the bridge contract, ensuring that all critical components have undergone rigorous security assessments. |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Narrow the audit-scope claim to the audited components.
The Sherlock scope covers specific contract files at a pinned commit and does not establish coverage of the full repository or the bridge contract. Check the separate Trail of Bits scope; if it is also narrower, replace the sentence with:
Proposed wording
- The above audit reports cover the entirety of our codebase, including the bridge contract, ensuring that all critical components have undergone rigorous security assessments.
+ The audit reports cover the components listed in their respective scopes. See each report for exact coverage, including any bridge contracts.📝 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.
| ### Audit Scope: | |
| The above audit reports cover the entirety of our codebase, including the bridge contract, ensuring that all critical components have undergone rigorous security assessments. | |
| ### Audit Scope: | |
| The audit reports cover the components listed in their respective scopes. See each report for exact coverage, including any bridge contracts. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/about-morph/4-morphs-architecture.md` around lines 81 - 83, Update the
“Audit Scope” section to remove the claim that the audits cover the entire
codebase or bridge contract. Verify the separately documented Trail of Bits
scope and replace the sentence with wording that accurately limits coverage to
the specifically audited components and pinned contract files.
| ## 2024 Q1 | ||
|
|
||
| - Optimistic zkEVM | ||
| - Decentralized Sequencers | ||
|
|
||
| Testnet Holesky (2024 Q2) | ||
| ## 2024 Q2 | ||
|
|
||
| - EIP-4844 Integration | ||
| - zkEVM Upgrade | ||
|
|
||
| ### Testnet Holesky | ||
|
|
||
| ## Phase 2: Mainnet Launch (2024 H2) | ||
| ## 2024 Q4 | ||
|
|
||
| ### Mainnet Beta 2024 Q3 | ||
| - Morph Staking | ||
| - Morph Zoo Season 1 | ||
|
|
||
| ### Mainnet Update Q4 | ||
| - Consumer Layer Launch | ||
| - zkVM Upgrade | ||
| - 1st Rollup with SP1 zkVM | ||
| - 1st Rollup with Decentralized Sequencers | ||
|
|
||
| ## 2025 Q1 | ||
| - Morph Pay | ||
| - Gasless Transaction No newline at end of file |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Do not present past quarters as an active roadmap.
As of August 4, 2026, all listed quarters—2024 Q1, 2024 Q2, 2024 Q4, and 2025 Q1—are in the past. Mark these as completed historical milestones, or replace them with current and future quarters and add milestone status.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/about-morph/6-roadmap.md` around lines 15 - 32, Update the roadmap
sections for 2024 Q1, 2024 Q2, 2024 Q4, and 2025 Q1 to clearly mark their
milestones as completed historical items, or replace them with current and
future quarters that include milestone status; do not present these past
quarters as active roadmap work.
| --- | ||
|
|
||
| ### Quicknode | ||
| ### QuickNode |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the provider heading hierarchy.
### QuickNode skips the expected h2 level. Apply the same correction to the new OpenChainBench heading. Keep all provider sections at the same sibling level, including Tenderly.
Proposed heading change
-### QuickNode
+## QuickNode
-### OpenChainBench
+## OpenChainBenchAlso applies to: 27-27
🧰 Tools
🪛 markdownlint-cli2 (0.23.1)
[warning] 6-6: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/2-rpc-services.md`
at line 6, Correct the provider heading hierarchy in the documentation by
changing the QuickNode and OpenChainBench headings to the expected h2 level, and
update Tenderly to the same sibling level so all provider sections are
consistent.
Source: Linters/SAST tools
| Read more about what you can get here: | ||
|
|
||
| [Quicknode Partnership](https://quicknode.notion.site/QuickNode-Benefits-for-Morph-Developers-4baf42f78dd64f389a2405e61350a0a6) | ||
| [QuickNode Partnership](https://quicknode.notion.site/QuickNode-Benefits-for-Morph-Developers-4baf42f78dd64f389a2405e61350a0a6) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Replace the broken QuickNode partnership link.
The linked page currently returns 404 Not Found. Replace it with the current canonical benefits page before merging. ()
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/2-rpc-services.md`
at line 14, Update the QuickNode Partnership link in the RPC services developer
resources documentation to use the current canonical benefits page, replacing
the broken URL while preserving the existing link text and surrounding content.
Source: MCP tools
2 participants
What is OpenChainBench?
OpenChainBench is an open, live benchmark that continuously measures latency across free public RPC endpoints for dozens of EVM chains. Results are updated in real time using actual JSON-RPC probe requests.
Why add this?
The RPC Services page lists QuickNode and Tenderly as RPC providers for Morph. This adds a reference to OpenChainBench where developers can compare latency across free public Morph endpoints before choosing a provider.
Change
Added an "OpenChainBench" section at the end of the RPC Services page.
Summary by CodeRabbit