docs(developers): reference OpenChainBench for third-party Scroll RPC comparison#561
Open
Flotapponnier wants to merge 1 commit into
Conversation
Signed-off-by: Florent Tapponnier <contact@openchainbench.com>
|
@ChainBench is attempting to deploy a commit to the Scroll Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds one bullet to the "Where can I find additional RPC providers and infrastructure for Scroll Mainnet?" list in
src/content/docs/en/developers/index.mdx, pointing readers to the OpenChainBench Scroll RPC benchmark as an independent third-party latency and reliability comparison of the public Scroll endpoints.Why it fits
The page already directs readers to ChainList.org for endpoint discovery and to Scrollscan/Rollup Scanner for status. What is missing is a live performance comparison across the public providers, which OpenChainBench provides: p50/p95/p99 latency, reliability classification (HTTP vs JSON-RPC error), and stale-block detection, probed every minute from three regions (US East, EU West, Singapore) with data under a CC BY 4.0 license and the Go harness open-sourced on GitHub. OpenChainBench has no affiliation with any RPC provider or the Scroll Foundation.
Change
One added bullet under the existing infrastructure list. No changes to any other entry.
Disclosure
I am the maintainer of OpenChainBench. Happy to reword, shorten, or drop the reference entirely if it does not fit the docs style guide.