Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion alternatives/birdeye.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@ intro: |
Birdeye is a Solana token analytics platform with a price + metadata API. If you need an alternative, one practical axis is metadata completeness. for a freshly-launched Solana token, how often does the API return a populated logo, description, twitter and website? Below is the live percentage for each provider on Solana, refreshed every minute against fresh-launch tokens detected from Mobula Pulse.

seo_title: "Birdeye alternatives: live benchmark"
seo_description: Compare Birdeye alternatives on token metadata coverage for Solana. Logo, description, twitter and website availability for freshly-launched tokens, measured live.
seo_description: "Birdeye alternatives on Solana token metadata coverage: logo, description, socials in seconds. Codex vs Mobula live."
2 changes: 1 addition & 1 deletion alternatives/chainlink.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ intro: |
Chainlink publishes on-chain price feeds via AggregatorV3 contracts deployed on Ethereum mainnet and most major EVM chains, with node operators posting new rounds on either a deviation trigger (typically 0.25 to 0.5 percent for blue chips) or a heartbeat interval. Every on-chain product that settles in fiat (perp DEXes, lending markets, derivatives, stablecoin issuers) picks one oracle and inherits its drift, which is why the practical question is how aligned the major feeds actually are at the moment a settlement happens. This benchmark polls four oracles every 30 seconds for ten USD-quoted blue chips, computes the pairwise deviation `|a-b|/avg * 100` across every source pair, and publishes the per-pair maximum as a Prometheus gauge in basis points. Sources include Chainlink AggregatorV3 (via `eth_call` against the canonical mainnet contracts), Pyth Network's Hermes REST feed, Binance and Coinbase REST tickers. Pairs are BTC, ETH, SOL, BNB, AVAX, LINK and POL on all four sources, plus XRP, ADA and DOGE on three sources because the Chainlink mainnet feeds for those USD pairs are deprecated. A stale-price guard skips samples older than 60 seconds so a dead poller cannot artificially flatten the deviation, and the companion gauge `ocb_oracle_last_round_age_seconds{source="chainlink"}` surfaces Chainlink's on-chain update gap separately so a wide deviation can be attributed to the right cause. The headline leaderboard ranks the ten pairs by p99 of the max deviation over 24 hours, lower meaning tighter cross-oracle alignment.

seo_title: "Chainlink alternatives: live benchmark"
seo_description: Compare Chainlink against Pyth, Binance and Coinbase on live oracle deviation. Max pairwise gap on 10 USD pairs, polled every 30 seconds, p99 over 24 hours.
seo_description: "Chainlink vs Pyth, Binance and Coinbase on live oracle deviation. Max pairwise gap on BTC, ETH, SOL."

status: live
2 changes: 1 addition & 1 deletion alternatives/drpc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ intro: |
dRPC is a decentralized RPC mesh that routes each JSON-RPC request across third-party node providers with consensus checks, exposing a no-key public tier on every major EVM network. Picking a default endpoint for a dapp comes down to a per-chain question: which free public RPC is actually fast and reliable on the chain my product runs on, right now, not according to a marketing page. This benchmark answers it directly. The harness sends an identical `eth_blockNumber` POST every 15 seconds against 15 audited no-key public RPC providers across 10 EVM chains (Ethereum, Arbitrum, Base, Optimism, Avalanche, BNB, Polygon, Linea, Scroll, Mantle), from three Railway regions (us-east, eu-west, sgp). p50, p90 and p99 are computed via Prometheus `quantile_over_time` over the last 24 hours, and a five-class result label (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) lets the success-rate column catch endpoints that return HTTP 200 with a JSON-RPC error body (the Cloudflare-eth trap). An archive-depth probe runs every 5 minutes against five depths so a fast endpoint that silently serves pruned state is not ranked as a viable archive source. The cohort competing with dRPC includes PublicNode, 1RPC, MeowRPC, Tenderly Gateway, Nodies, Lava, Merkle, Flashbots Protect and Cloudflare, plus the chain-official foundation endpoints on Base, BNB, Arbitrum, Optimism and Avalanche. The chain tab filters every query so the leader is reported per network rather than as a cross-chain aggregate that rewards whichever single-chain endpoint happens to be fastest on its one chain.

seo_title: "dRPC alternatives: live benchmark"
seo_description: Compare dRPC alternatives on eth_blockNumber p50 latency. PublicNode, 1RPC, Tenderly, Nodies, Lava and chain-official endpoints measured every 15 seconds from 3 regions.
seo_description: "dRPC alternatives on eth_blockNumber p50 latency. PublicNode, 1RPC, Tenderly, Nodies, Lava ranked live."

status: live
2 changes: 1 addition & 1 deletion alternatives/dune.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,4 @@ intro: |
Dune lets analysts query indexed blockchain data with SQL, often via labelled wallet datasets contributed by the community. When sizing alternatives, one practical axis is wallet labelling depth. how many addresses does each provider have a label for, and how confident are those labels? Below is the live coverage from each major labelling provider, refreshed continuously against a shared sample of recently active wallets.

seo_title: "Dune alternatives: live benchmark"
seo_description: Compare Dune alternatives on wallet labelling depth. Coverage of recently active addresses across major providers, measured continuously and published openly.
seo_description: "Dune alternatives on wallet labelling depth. Recently active address coverage across major EVM chains."
2 changes: 1 addition & 1 deletion alternatives/kalshi.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ intro: |
Kalshi runs a CFTC-regulated event contracts exchange with the only documented token bucket in its cohort (around 20 requests per second on the basic read tier at the time of writing). Its order book and single-market endpoints go to origin on every request, but the market list is served from CloudFront with `max-age=15`, so list latency measures the edge rather than the API origin. The WebSocket requires authentication, which excludes Kalshi from the public WS panel. Builders sizing against this kind of API need two numbers: the real latency of the hot endpoints at a polite request rate, and what happens as the rate climbs. This benchmark probes book (`/markets/{ticker}/orderbook`), price (`/markets/{ticker}`) and list (`/markets`) endpoints continuously from three Railway regions (us-east, eu-west, sgp), every 5 to 7 seconds over warm keep-alive connections, with a separate cold-connect probe once per minute. Once per day per venue it runs a 60-second-per-tier ramp at rising request rates, recording added latency against the same-hour warm baseline and any 429 onset. Kalshi's ramp uses tiers 25/50/100 requests per 10 seconds and stops at the first 429 out of respect for the documented contract. The harness flags CDN cache hits via `cf-cache-status`, `x-cache` and `age` headers and excludes them from latency aggregates so no venue ranks on its CDN. Every request carries an identifying User-Agent with a contact address. The cohort competing with Kalshi includes Polymarket (Cloudflare-queued CLOB), Limitless (undocumented limits, errors CDN cached for 4 hours), Manifold (500 req/min per IP, whole API behind a 5-second cache) and Myriad (single-region Heroku origin, no order book).

seo_title: "Kalshi alternatives: live benchmark"
seo_description: Compare Kalshi against Polymarket, Limitless, Manifold and Myriad on warm book latency and daily ramp throttle behaviour, measured from us-east, eu-west and sgp.
seo_description: "Kalshi vs Polymarket, Limitless, Manifold, Myriad on warm book latency and ramp throttle (us-east, eu-west, sgp)."

status: live
2 changes: 1 addition & 1 deletion alternatives/publicnode.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ intro: |
PublicNode is the no-key public RPC service operated by Allnodes, covering 70+ chains with endpoints anchored close to a large EU-resident validator footprint. It is the de-facto default fallback for many dapps because it shows up on most EVM networks at once and serves archive-depth state on most of them. Comparing it against the other candidates a developer might paste into a wallet config or a backend service is per chain and per region, not per marketing page. This benchmark probes `eth_blockNumber` every 15 seconds against 15 audited no-key RPC providers across 10 EVM chains (Ethereum, Arbitrum, Base, Optimism, Avalanche, BNB, Polygon, Linea, Scroll, Mantle) from three Railway regions (us-east, eu-west, sgp). Latency is recorded with millisecond precision and exposed as both a gauge and a histogram so p50, p90 and p99 are computed via Prometheus `quantile_over_time` over the last 24 hours. A five-class result label catches endpoints that answer HTTP 200 with a JSON-RPC error body or serve a stale head more than 20 blocks behind the cross-provider tip, and a separate archive-depth probe runs every 5 minutes across five depths (300 to 5,000,000 blocks). The cohort competing with PublicNode includes dRPC, 1RPC, MeowRPC, Tenderly Gateway, Nodies, Lava, Merkle, Flashbots Protect and Cloudflare, plus the chain-official foundation endpoints on Base, BNB, Arbitrum, Optimism and Avalanche. The chain tab filters every query so the leader is reported per network, not as a cross-chain aggregate.

seo_title: "PublicNode alternatives: live benchmark"
seo_description: Compare PublicNode alternatives on eth_blockNumber p50 latency. dRPC, 1RPC, Tenderly, Nodies, Lava, Merkle and chain-official endpoints probed every 15 seconds from 3 regions.
seo_description: "PublicNode alternatives on eth_blockNumber p50 latency. dRPC, 1RPC, Tenderly, Nodies, Lava ranked live."

status: live
2 changes: 1 addition & 1 deletion alternatives/pump-portal.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,4 @@ intro: |
Pump Portal is a single-purpose WebSocket on Solana, scoped to pump.fun and the bonding-curve launchpad ecosystem around it (new token creations, migration to Raydium, per-mint trade events). The surface is intentionally narrow: no support for other chains, no general DEX coverage outside the pump.fun graduates and no historical query layer beyond the live stream. The free tier exists, but high-volume readers route through a paid trading endpoint that adds a per-trade priority fee on top. The provider sits close to the launchpad it tracks rather than near a canonical Solana archive, so the bottleneck is usually the upstream indexer rather than the WebSocket itself. Teams that outgrow the pump.fun-only scope (cross-DEX routing, non-Solana chains, OHLCV history) tend to drop it the moment a second venue or chain enters the product.

seo_title: "PumpPortal alternatives: live benchmark"
seo_description: Looking for an alternative to Pump Portal? Compare Codex, GeckoTerminal and Mobula on real-time blockchain data latency, measured continuously and published openly.
seo_description: "Pump Portal alternatives: Codex, GeckoTerminal, Mobula on real-time block ingestion + Solana mint feed."
2 changes: 1 addition & 1 deletion alternatives/pyth.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ intro: |
Pyth Network is a pull-based price oracle with publisher-signed feeds delivered through the Hermes REST endpoint and on-chain via wormhole-attested updates. Unlike Chainlink's push model with a deviation trigger, Pyth refreshes continuously off-chain, which means the off-chain quote available to a protocol team is usually fresher but the on-chain inscription of that quote still depends on when an integrator submits the update. The question every protocol designer picking an oracle asks is how aligned the major feeds actually are at the moment a settlement happens, not what each vendor's whitepaper claims. This benchmark polls four oracles every 30 seconds for ten USD-quoted blue chips, computes the pairwise deviation `|a-b|/avg * 100` across every source pair, and publishes the per-pair maximum as a Prometheus gauge in basis points. Sources are Chainlink AggregatorV3 (via `eth_call`), Pyth Hermes (batched `latest_price_feeds`), Binance REST ticker (USDT quoted, treated as approximately USD) and Coinbase REST ticker. Pairs are BTC, ETH, SOL, BNB, AVAX, LINK and POL on all four sources, plus XRP, ADA and DOGE on three sources because the Chainlink mainnet feeds for those USD pairs are deprecated. A 60-second stale-price guard excludes any source whose last sample is older than two poll intervals, so a dead poller cannot register a false zero deviation against itself. The leaderboard ranks the ten pairs by p99 of the max deviation over 24 hours; lower means tighter cross-oracle alignment.

seo_title: "Pyth alternatives: live benchmark"
seo_description: Compare Pyth against Chainlink, Binance and Coinbase on live oracle deviation. Max pairwise gap on 10 USD pairs, polled every 30 seconds, p99 over 24 hours.
seo_description: "Pyth vs Chainlink, Binance and Coinbase on live oracle deviation. Max pairwise gap on BTC, ETH, SOL."

status: live
2 changes: 1 addition & 1 deletion alternatives/tenderly.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ intro: |
Tenderly runs a multi-chain public RPC gateway at `gateway.tenderly.co/public/<slug>` alongside its simulation and observability stack. The free, no-key tier covers nine EVM networks and gets pulled into the same dapps that pick PublicNode or dRPC as their default fallback endpoint. The question every developer faces before pasting a URL into a wallet config or a backend service is whether that endpoint is actually fast and reliable on the chain their product runs on, not whether the vendor's homepage says it is. This benchmark probes `eth_blockNumber` every 15 seconds against 15 audited no-key public RPC providers across 10 EVM chains (Ethereum, Arbitrum, Base, Optimism, Avalanche, BNB, Polygon, Linea, Scroll, Mantle), from three Railway regions (us-east, eu-west, sgp). Each provider gets the same identical JSON-RPC POST every cycle, so the recorded p50/p90/p99 reflects sustained round-trip latency rather than a marketing burst. The harness also classifies every response as `ok`, `http_err`, `jsonrpc_err`, `stale` or `timeout` and exposes archive-depth support for five historical depths (300 to 5,000,000 blocks). The cohort competing with Tenderly's gateway includes PublicNode, dRPC, 1RPC, MeowRPC, Nodies, Lava, Merkle, Flashbots Protect and Cloudflare, plus the chain-official foundation endpoints on Base, BNB, Arbitrum, Optimism and Avalanche. The leaderboard re-sorts every 15 seconds against fresh Prometheus samples, and the chain tab at the top of the page filters every query so the comparison stays per chain rather than smeared across an aggregate that mechanically favours single-chain endpoints.

seo_title: "Tenderly alternatives: live benchmark"
seo_description: Compare Tenderly Gateway alternatives on eth_blockNumber p50 latency. PublicNode, dRPC, 1RPC, Nodies, Lava and chain-official endpoints probed every 15 seconds from 3 regions.
seo_description: "Tenderly Gateway alternatives on eth_blockNumber p50 latency. PublicNode, dRPC, 1RPC, Nodies ranked live."

status: live
2 changes: 1 addition & 1 deletion benchmarks/bridge-fee.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: bridge-fee
number: "003"
title: Cheapest cross-chain bridge for USDC at $300 notional
seo_title: "Cheapest cross-chain bridge 2026"
seo_description: "Cheapest cross-chain bridge for USDC at $300 notional. Total cost (fees, slippage, dest gas) across Solana, Base, Arbitrum. deBridge, LI.FI, Mobula, Relay, Near Intents."
seo_description: "Cheapest cross-chain bridge for USDC at $300. Total cost (fees, slippage, gas) across deBridge, LI.FI, Mobula, Relay."
subtitle: Total cost as a percent of notional, fees plus slippage plus destination gas combined, sampled at $300 USDC across Solana, Base and Arbitrum corridors.
category: Bridges
status: live
Expand Down
2 changes: 1 addition & 1 deletion benchmarks/bridge-quote-latency.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: bridge-quote-latency
number: "002"
title: Fastest cross-chain bridge quote API, live ms ranking
seo_title: "Fastest bridge quote API 2026"
seo_description: "{{best_name}} leads fastest bridge quote API at {{best_p50}} (p50, 24h). Mobula, deBridge, Relay, LI.FI, Near Intents on identical USDC routes, refreshed every 5 minutes."
seo_description: "Live p50 latency for cross-chain bridge quote APIs. Mobula, deBridge, Relay, LI.FI, Near Intents ranked."
subtitle: Time to receive a usable cross-chain quote, in milliseconds. Identical route and identical notional, measured every five minutes across Mobula, deBridge, Relay, LI.FI and Near Intents.
category: Bridges
status: live
Expand Down
2 changes: 1 addition & 1 deletion benchmarks/bridge-revenue.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: bridge-revenue
number: "028"
title: Cross-chain bridge implied protocol revenue
seo_title: "Cross-chain bridge revenue tracker 2026"
seo_description: "Live cross-chain bridge implied protocol revenue. (USD in − USD out − gas − app fees) summed over swaps in 24h / 7d / 30d. Upper bound on what each bridge + solvers keep. Relay tracked today; Across / Socket / deBridge to follow. Methodology pre-registered, harness OSS."
seo_description: "Live cross-chain bridge implied protocol revenue. (USD in − out − gas − fees) summed daily, ranked in USD."
subtitle: Implied margin in USD that each cross-chain bridge plus its solver network collectively retain per swap, summed over rolling 24h / 7d / 30d windows. Upper bound, not exact. Read methodology before citing.
category: Bridges
status: live
Expand Down
2 changes: 1 addition & 1 deletion benchmarks/buyback-audit.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: buyback-audit
number: "018"
title: DeFi token buyback tracker, live executed vs promised ratio
seo_title: "DeFi buyback tracker 2026"
seo_description: "DeFi token buyback tracker ranked live by executed over promised ratio. Hyperliquid Assistance Fund (HYPE) and Sky Smart Burn Engine (SKY). 7d and 30d windows."
seo_description: "DeFi token buyback tracker: ratio of executed vs promised, live. Hyperliquid HYPE, Sky SKY ranked."
subtitle: Executed USD over promised USD for live on-chain buyback programs, computed against destination-wallet inflows over rolling 7-day and 30-day windows.
category: Trading
status: live
Expand Down
2 changes: 1 addition & 1 deletion benchmarks/evm-quote-latency.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: evm-quote-latency
number: "033"
title: Fastest EVM swap quote API
seo_title: "Fastest EVM swap quote API 2026"
seo_description: "Live p50/p90/p99 round trip latency for the major EVM swap quoting APIs measured every minute on a rotating basket of top markets across Ethereum, Base, Arbitrum and BSC, with a 3 region geographic split."
seo_description: "Live p50/p90/p99 latency for major EVM swap quote APIs measured every minute on a rotating token basket."
subtitle: Wall clock p50 latency of GET /quote per provider, measured every minute on a 5 pair basket across 4 chains.

per_chain_explainer:
Expand Down
2 changes: 1 addition & 1 deletion benchmarks/gas-estimation.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: gas-estimation
number: "013"
title: Most accurate gas oracle, live gap vs realized priority fee
seo_title: "Most accurate gas oracle 2026"
seo_description: "Most accurate gas oracle ranked live on Ethereum and Polygon. Gwei gap between predicted and realized priority fee in the next mined block. Ranked on the p99 gap over 24h."
seo_description: "Most accurate gas oracle live on Ethereum and Polygon: gwei gap between predicted and realized effective_gas_price."
subtitle: Absolute gap in gwei between each oracle's predicted priority-fee tier and the realized percentile in the next mined block, measured per chain. Ranked on the p99 gap, the worst 1% of blocks, because that is where gas spikes hurt integrations.

per_chain_explainer:
Expand Down
2 changes: 1 addition & 1 deletion benchmarks/hyperliquid-frontends.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ slug: hyperliquid-frontends
number: "030"
title: Hyperliquid frontends builder revenue leaderboard
seo_title: "Hyperliquid frontends: builder fees 2026"
seo_description: "Live USD revenue collected by every Hyperliquid frontend via the on chain builder code field. Phantom Perps, MetaMask, Rabby, Insilico, based.app, OneKey, Axiom, pvp.trade and 95+ others ranked by 24h, 7d and 30d builder fees. Data source is a local hl node tailing the Hyperliquid mainnet fill stream."
seo_description: "Live USD revenue collected by every Hyperliquid frontend via the on-chain builder code. Ranked by 24h fees."
subtitle: How much USD builder fee revenue each Hyperliquid frontend collected over the rolling 24h, 7 day and 30 day windows. Data from a local hl node tailing every fill on mainnet.
category: Trading
status: live
Expand Down
Loading
Loading