Benchmark crypto infrastructure.
Open, reproducible performance data for the multichain stack — aggregators, bridges, RPCs, price feeds. Measured the same way every time. Every spec and every harness is public.
Benchmarks
3
Live
3
Providers tracked
6
Samples · 24h
241,053
Open data, freshly run.
Hover any card for the abstract and the field. Click to read the full report.
- № 001 · DataLive
Aggregator Head Lag — How Fresh Is the Data?
Time between an on-chain event and its appearance on each aggregator's WebSocket — measured against archive nodes tracking the canonical tip.
- Lead
- Mobula
- Best p50
- 0.5 s
Updated Apr 28, 2026, 8:12 PM UTCFrom the abstract
We measure the gap between a transaction settling on chain and the same transaction appearing on each aggregator's data feed. The harness watches reference pools across Base, BNB Chain and Solana from three regions (us-east, eu-west, sgp), records every new on-chain event with millisecond timestamps, and observes when each aggregator's WebSocket reflects the same event. Lower is better.
The field
- Mobula
- Codex
- GeckoTerminal
- № 002 · BridgesLive
Cross-Chain Bridge — Quote Latency
How fast each bridge API returns a usable cross-chain quote, measured under identical inputs.
- Lead
- Mobula
- Best p50
- 151 ms
Updated Apr 28, 2026, 8:12 PM UTCFrom the abstract
We benchmark how long the major bridge APIs take to return a usable cross-chain quote (route + fee + estimated settlement time). The harness cycles through 4 routes × 3 notional sizes × every supported bridge every five minutes, recording p50, p90 and p99 wall-clock latency along with the success rate. Quotes that error or return unsupported responses are excluded from latency aggregates and counted toward success rate.
The field
- Mobula
- Relay
- LiFi
- Debridge
- № 003 · BridgesLive
Cross-Chain Bridge — Fee
What a user actually pays — fees, slippage and destination gas combined, as a percentage of trade size.
- Lead
- Mobula
- Best p50
- 0.033%
Updated Apr 28, 2026, 8:12 PM UTCFrom the abstract
We measure the effective fee each bridge charges — the bottom-line cost a user pays, fees plus slippage plus destination gas — as a percentage of trade size. The harness uses Prometheus gauge `bridge_cost_percent` rather than the narrower `bridge_fees_percent` because providers structure pricing differently — some charge an explicit fee, others bake it into the spread. Comparing only the explicit fee field would let aggregators with implicit pricing show a misleading 0%. Sampled at $300 notional so small-amount fixed-fee blowups don't skew the percentile aggregates. Lower is better.
The field
- Mobula
- Relay
- LiFi
- Debridge
Spec it. Push metrics. The page renders itself.
01
One YAML per benchmark
Editorial metadata + Prometheus queries in a single file. Drop it in benchmarks/, open a PR. The format is a Zod schema; CI rejects malformed specs.
02
Run a harness anywhere
Whatever language fits — Bun, Node, Python, Go. Push the metrics named in your YAML. The site re-queries every minute via ISR.
03
Live leader, no gatekeeping
The leader on every page is computed at render time from the data. No spec marks a winner ahead of time. Pull requests for new providers welcome.