Skip to content

docs: add OpenChainBench RPC latency benchmark reference #149

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.

Sign up for GitHub

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

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

docs: add OpenChainBench RPC latency benchmark reference #149

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6bfd481
Update RoadMap
RedHorse823 Mar 7, 2025
30b90d5
Add Safety Information
RedHorse823 Mar 7, 2025
66a38e1
docs: add OpenChainBench RPC latency benchmark reference
Flotapponnier Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified assets/docs/about/roadmap/roadmap.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
26 changes: 26 additions & 0 deletions docs/about-morph/4-morphs-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,3 +57,29 @@ Morph’s architecture is further defined by five pivotal roles: Sequencers, Val

For a deeper understanding of Morph’s architecture, please visit our comprehensive [Developer Docs](../build-on-morph/0-developer-navigation-page.md).

## Safety and Security

We place the highest priority on security and are committed to providing users with a safe and trustworthy environment. To achieve this, we’ve implemented multiple measures, including making our codebase open-source, engaging leading third-party firms for audits, and continuously improving our systems to uphold the highest standards of transparency and security. Below are some specific efforts we’ve undertaken:

### 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)
Comment on lines +64 to +68

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 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.


### Sherlock Open-Source Audit Report:

We commissioned a comprehensive security audit from Sherlock, and the results are publicly available. You can view the detailed report here:

[Sherlock Open-Source Audit Report](https://audits.sherlock.xyz/dashboard/9b78b63a3eb0597e7ba60eec251b6888/confirm_issues)

### Trail of Bits Audit Report:

Additionally, we enlisted the renowned Trail of Bits team to conduct an in-depth audit of our codebase, including a review of implemented fixes. The [full report](https://github.com/morph-l2/audits/blob/main/tob/Morph%20-%20Comprehensive%20Report%20with%20Fix%20Review.pdf) is accessible.


### 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.
Comment on lines +81 to +83

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔒 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.

Suggested change
### 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.


We firmly believe that transparency and security are the cornerstones of trust. We will continue to collaborate with the community and professional organizations to elevate our security standards and provide users with peace of mind. If you have any questions or suggestions, feel free to reach out to us at any time!
23 changes: 8 additions & 15 deletions docs/about-morph/6-roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,28 +12,21 @@ description: Upgrade your blockchain experience with Morph - the secure decentra

![1](../../assets/docs/about/roadmap/roadmap.png)


## Phase 1: Testnet (2024 H1)

Testnet Sepolia (2024 Q1)
## 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
Comment on lines +15 to +32

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 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.

12 changes: 8 additions & 4 deletions ...ld-on-morph/developer-resources/use-ecosystem-developer-tools/2-rpc-services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,17 +3,17 @@ title: RPC Services
lang: en-US
---

### Quicknode
### QuickNode

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 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
+## OpenChainBench

Also 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


QuickNode is transforming blockchain infrastructure and tooling by simplifying web3 development and providing high-performance access to Morph.

Developers in the Morph ecosystem are now eligible for free QuickNode credits/discounts!

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)

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 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


![QuickNode](../../../../assets/docs/dev/resources/quicknode.png)
![QuickNode](../../../../assets/docs/dev/resources/quicknode2.jpg)

### Tenderly

Expand All @@ -22,4 +22,8 @@ Tenderly is a full-stack Web3 infrastructure – node RPC, dev environments & ex

Build & scale with ease. Get started [here](https://blog.tenderly.co/building-dapps-on-morph-with-tenderly/)

![tenderly](../../../../assets/docs/dev/resources/tenderly.png)
![tenderly](../../../../assets/docs/dev/resources/tenderly.png)

### OpenChainBench

For live latency comparisons across free public Morph RPC endpoints, see [OpenChainBench](https://openchainbench.com/benchmarks/morph-rpc) — an open benchmark that continuously measures response times across providers so you can pick the fastest endpoint for your use case.