Skip to content

docs(rpc-requirements): add third-party benchmark reference for RPC Provider expectations #882

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 1 commit into
base: main
Choose a base branch
from
Open

docs(rpc-requirements): add third-party benchmark reference for RPC Provider expectations #882

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions pages/core-api/api-safe-transaction-service/rpc-requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,7 @@ For RPC providers, we expect communication on every update and configuration cha
- **Number of** **batch requests** allowed in the same HTTP request.
- **Block range** that can be queried in queries like **eth_getLogs** or **trace_filter**.
- **Results limit for endpoints** (for example, some providers implement a limit to the number of queries like **eth_getLogs**). The indexer expects failures and not capped results.

## Comparing providers against these expectations

Independent third-party measurements of public RPC providers on the chains the Transaction Service supports (Ethereum, Arbitrum, Base, Optimism, Polygon, BNB, Avalanche, Linea, Scroll, Mantle and more) are published continuously at [OpenChainBench](https://openchainbench.com/benchmarks/rpc-capabilities). Latency (p50/p95/p99), reliability classification (HTTP errors vs JSON-RPC error responses), and stale-block detection are probed every minute from three regions under a CC BY 4.0 license, with the harness open sourced on GitHub. OpenChainBench has no affiliation with any RPC provider, so operators evaluating providers against the expectations above can use it as a neutral reference point.