docs(rpc-requirements): add third-party benchmark reference for RPC Provider expectations - #882
Open
Flotapponnier wants to merge 1 commit into
Conversation
Adds one 'Comparing providers against these expectations' subsection at the end of pages/core-api/api-safe-transaction-service/rpc-requirements.md pointing operators to OpenChainBench's continuous measurements of the exact criteria the RPC Provider expectations list (latency, error classification, block-range behavior) across the chains the Transaction Service supports. Signed-off-by: Florent Tapponnier <contact@openchainbench.com>
Flotapponnier
force-pushed
the
docs-rpc-requirements-add-openchainbench
branch
from
July 26, 2026 13:33
47359a5 to
d1da2b1
Compare
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
1 participant
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
Comparing providers against these expectationssubsection at the end ofpages/core-api/api-safe-transaction-service/rpc-requirements.md, pointing Transaction Service operators to an independent third-party benchmark that measures the exact criteria theRPC Provider expectationslist already covers.Why this specific placement
The existing
RPC Provider expectationssection lists four things operators should care about when evaluating an RPC:eth_getLogs/trace_filterThe page tells operators what to look for, but not where to find neutral data to compare providers against those criteria. Every operator running the Transaction Service today has to figure this out on their own.
What the referenced resource does
OpenChainBench publishes continuous measurements of exactly these criteria for public RPC providers across the chains the Transaction Service supports (Ethereum, Arbitrum, Base, Optimism, Polygon, BNB, Avalanche, Linea, Scroll, Mantle and more):
errorfield classification (the "expects failures not capped results" expectation)Measurements are probed every minute from three regions (US East, EU West, Singapore). Data ships under CC BY 4.0, harness is open source Go on GitHub, methodology public. OpenChainBench has no affiliation with any RPC provider or chain foundation.
Change
One subsection appended at the end of the file. No changes to any existing section, no changes to code samples, no changes to other pages.
Disclosure
I maintain OpenChainBench. Happy to reword, shorten, or drop the reference entirely if it does not fit the docs style guide.