About OpenChainBench

Crypto infrastructure runs the world's open financial rails, and almost none of it is benchmarked in public. Every aggregator, bridge, RPC and market-data feed quotes its own numbers, on its own terms, with its own regions and its own definitions of “fast”. OpenChainBench picks one definition at a time, runs the experiment in the open, and publishes the script alongside the result.

The goal is to make performance an observable property of crypto infrastructure. like uptime in SaaS, or p99 in databases. so builders can choose providers on data and users can hold them to it.

• ·Aggregators & data APIs. head-lag (on-chain event → feed), metadata coverage, network coverage, wallet-label coverage. Mobula, Codex, GeckoTerminal, Jupiter, Moralis, Helius and 6 wallet-label providers compared live.
• ·Bridges. quote latency and effective fee on $300 USDC corridors. Mobula, Relay, LiFi, Debridge.
• ·Blockchains. L1 finality time across 11 chains. L2 sequencer block time across 9 L2s.
• ·Trading venues. all-in opening cost on perp DEXes (Hyperliquid, Lighter, dYdX, GMX, gains). Stablecoin peg deviation on USDC, USDT, DAI + USDT-anchored swap-cost on FDUSD, USDe.
• ·RPCs. fastest free no-key public RPC across 10 EVM chains × 15 providers (PublicNode, dRPC, 1RPC, Tenderly, Nodies, Lava, Merkle, MeowRPC, Flashbots, Cloudflare, foundation endpoints). Plus gas-oracle prediction error (Blocknative, Owlracle, Etherscan, PublicNode feeHistory) on Ethereum, Polygon, Avalanche.

13 live benchmarks. ~150 (provider × chain) probe pairs. Every metric is queryable on the public Prometheus and reproducible from the harness source.

Numbers on the site can be reproduced from public data and public code. Three structural safeguards keep the project verifiable:

• ·Open Prometheus data. Every number on the site is a literal quantile_over_time query. Anyone can hit our /api/citable or /api/stat/<slug> endpoint and re-derive the leaderboard with their own aggregation. The raw data is the source of truth.
• ·Open harness source. Every harness is on GitHub under harnesses/. Clone, run docker compose up, your /metrics endpoint emits the same numbers ours does within 30 seconds.
• ·Public methodology review. We invite external review and ship the fixes publicly. In June 2026 four issues were flagged on the stablecoin peg and oracle deviation benches; three were shipped in pull requests #349, #352 and #353 within twenty-four hours; the fourth was answered with citations to CME, Chainlink and CoinGecko convention.

No paid tier. No sold ranking slots. No provider sponsorship in exchange for inclusion. No token. If you spot any deviation from this policy, file a private security advisory and we will treat it as the integrity incident it would be.

Every benchmark is a YAML spec plus a harness. The spec describes what to measure, which providers, which Prometheus queries hold the numbers; the harness runs continuously on Railway and exposes those metrics. A single shared Prometheus scrapes every harness; the site queries Prometheus directly and re-renders every minute. Every provider is rendered with equal visual weight. readers do their own ranking.

Anyone can submit a benchmark. The contribution guide walks through the steps. New providers, new metrics, new chains. all welcome via pull request.

• ·Read the live benchmarks .
• ·Reproduce any number. the methodology page tells you how.
• ·Contribute a harness via GitHub. Pull requests for new providers and new benchmarks are reviewed openly.
• ·Discuss ideas in GitHub Discussions or follow @OpenChainBench.

See a number you can't reproduce? File a data-quality issue or a provider correction. For press, partnerships or anything else, reach us at openchainbench@gmail.com. Material errors are corrected in place with a dated note on the affected report.