About OpenChainBench
Open, reproducible benchmarks for crypto infrastructure. measured in the open, published in the same format every time.
Why
Crypto infrastructure runs the world's open financial rails, and almost none of it is benchmarked in public. Every aggregator, bridge 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.
How
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 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.
What you can do
- ·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.
Contact
See a number you can't reproduce? File a data-quality issue or a provider correction. Material errors are corrected in place with a dated note on the affected report.