split network-coverage into asset-registry + dex-network benches - #1390
Merged
Conversation
…erage Apple-to-apple ranking: CoinPaprika's 300+ chains via /v1/contracts is asset-registry coverage (token metadata lookups), not comparable to GeckoTerminal 265 chains via /networks which is DEX pool indexing. - asset-registry-coverage bench (005): CoinGecko, CoinPaprika, CoinStats, Mobula - dex-network-coverage bench (090): GeckoTerminal, Codex, DefiLlama, DexPaprika, Sim by Dune - add fetchers coingecko, defillama, dexpaprika to harness (same binary) - 301 redirect /benchmarks/network-coverage to /benchmarks/asset-registry-coverage via RENAMED_BENCH_SLUGS map (preserves external backlinks) - retarget answer YAML to asset-registry-coverage with split framing
4 tasks
Flotapponnier
added a commit
that referenced
this pull request
Jul 24, 2026
Legacy bench 005 network-coverage removed, 2 new slugs added (asset-registry-coverage, dex-network-coverage). Bench SET changed so the 3 unstable_cache keys need lockstep bumps (see comments): - bench-unfiltered v45 -> v46 - all-benchmarks v48 -> v49 - bench-filters v20 -> v21 Without this, the new bench URLs 404 on prod (getBenchmark reads a stale cached bench-set that predates the split), which just tripped the sitemap smoke on #1390. Co-authored-by: Florent Tapponnier <contact@mobula.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
network-coverageinto 2 apple-to-apple benchesasset-registry-coverage(005): CoinGecko 461, CoinPaprika 307, CoinStats 149, Mobula 79dex-network-coverage(090): GeckoTerminal 265, Codex 120, DefiLlama 479, DexPaprika 36, Sim by Dune 64/benchmarks/network-coverage->/benchmarks/asset-registry-coverageviaRENAMED_BENCH_SLUGS(preserves CoinPaprika Twitter backlink + PageRank)Why
Twitter user @sooneggg flagged CoinPaprika #1 with 307 chains via
/v1/contracts(asset registry) is not comparable to GeckoTerminal 265 chains via/networks(DEX pool indexing). Different products, different question, splitting into 2 leaderboards makes each ranking meaningful.Test plan
pnpm validate-> 87 specs OKpnpm typecheck-> OKgo build ./cmd/script/-> OKcurl https://openchainbench.com/api/stat/asset-registry-coveragereturns 4 providerscurl https://openchainbench.com/api/stat/dex-network-coveragereturns 5 providerscurl -I https://openchainbench.com/benchmarks/network-coveragereturns 301 to asset-registry-coverage