Repository navigation
the four terminal benches go to production, two under honest slugs - #2852
Merged
Merged
Conversation
Benches 203, 206, 207 and 232 leave DEV_ONLY. They were gated on 2026-10-02 when the Dune trial ended; they were re-sourced this week to the public tehcscreener API via harnesses/terminal-activity, and the audit round is what #2843, #2844, #2846, #2848 and #2849 were. Un-gated after the audit rather than after a 24h window, and the distinction matters: these four declare no range selector. Every query is an instant read of a gauge, so there is no window to fill. The only thing a day would buy them is a complete chart, which is cosmetic, and 351 scrapes are already in. 206 and 207 are renamed on the way out: solana-avg-trade-size -> terminal-avg-trade-size solana-unique-traders -> terminal-swap-transactions Both gained an all-chains default view in #2846 while their slugs still promised Solana, which is the kind of thing an SEO audit flags and a reader trips over. Neither was ever served on production, so there is no signal to preserve and no redirect is owed; RENAMED_BENCH_SLUGS stays untouched. The second name also drops a claim the old one never earned: it counts transactions, not unique traders. Cache keys bumped in lockstep, bench-unfiltered v88 to v89, all-benchmarks v81 to v82 and bench-filters v32 to v33, because every cached bench set is stale on both counts: the membership changed and two slugs moved. bench-published.json keeps each bench's original publication date under its new key.
Flotapponnier
added a commit
that referenced
this pull request
Oct 7, 2026
…2854) #2846 gave 206 and 207 an all-chains default view and #2852 renamed them off the solana- prefix, but the renaming stopped at the title. The body did not move, so both pages shipped to production saying "leads Solana terminals", "routed Solana volume divided by that day's swap count", and, in every one of the eighteen provider formulas, "on Solana on the day". That is a page contradicting its own tab strip in front of readers, on the figure it exists to publish. Fixed across the seo_description, disclaimer, seo_intro, methodology, findings, FAQ and all eighteen formulas. 207's "Is this Solana only?" FAQ was the wrong question once the answer became no; it now answers how to read one chain at a time, which is what someone looking at eight tabs actually wants to know. Three mentions of Solana stay in each, and all three are true: the methodology line about BasedBot routing on Robinhood and almost nothing on Solana, and the tags on Trojan and Photon, which really are Solana-only products.
Flotapponnier
added a commit
that referenced
this pull request
Oct 7, 2026
…2854) (#2855) #2846 gave 206 and 207 an all-chains default view and #2852 renamed them off the solana- prefix, but the renaming stopped at the title. The body did not move, so both pages shipped to production saying "leads Solana terminals", "routed Solana volume divided by that day's swap count", and, in every one of the eighteen provider formulas, "on Solana on the day". That is a page contradicting its own tab strip in front of readers, on the figure it exists to publish. Fixed across the seo_description, disclaimer, seo_intro, methodology, findings, FAQ and all eighteen formulas. 207's "Is this Solana only?" FAQ was the wrong question once the answer became no; it now answers how to read one chain at a time, which is what someone looking at eight tabs actually wants to know. Three mentions of Solana stay in each, and all three are true: the methodology line about BasedBot routing on Robinhood and almost nothing on Solana, and the tags on Trojan and Photon, which really are Solana-only products. (cherry picked from commit df56c7d)
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.
1. Un-gated
Benches 203, 206, 207 and 232 leave
DEV_ONLY_BENCH_SLUGS(11 → 7).Un-gated after the audit round rather than after a 24h window, and the distinction matters: these four declare no range selector. Every query is an instant gauge read, so there is no window to fill. The only thing a day would buy them is a complete chart, which is cosmetic. 351 scrapes are already in and the last cycle was 2 minutes ago.
The audit round is what #2843, #2844, #2846, #2848 and #2849 were.
2. Renamed
Both gained an all-chains default view in #2846 while their slugs still promised Solana. Neither was ever served on production, so there is no signal to preserve and no redirect is owed;
RENAMED_BENCH_SLUGSstays untouched. The second name also drops a claim the old one never earned: it counts transactions, not unique traders.Cache keys bumped in lockstep (
bench-unfilteredv88→v89,all-benchmarksv81→v82,bench-filtersv32→v33) because membership changed and two slugs moved.bench-published.jsonkeeps each bench's original publication date under its new key.3. Bench 200 — not done, and I was wrong to propose it
I said
solana-launchpad-warsmisses a third of the volume it ranks and that the fix was the same as this week's. I had not compared the cohorts:Re-sourcing would lose 6 of 8 current rows to gain 5. That is not a fix, it is a different bench with worse coverage of the cohort bench 200 exists to rank.
The gap is real — ponsfamily.com ($7.2B/30d) and long.xyz ($1.89B/30d) on Robinhood Chain are untracked anywhere on the site — but the answer is a new cross-chain launchpad bench, not a re-source that guts this one.
Verification
pnpm validate237/237, typecheck clean, eslint clean, no stale slug outside the explanatory comment, all four resolve as production throughDEV_ONLY_BENCH_SLUGS.