Repository navigation
the RPC speed test and the latency map go live - #2746
Merged
Merged
Conversation
Both were held off production since 2026-09-21 because the map had 2 cells and 32 samples. That reasoning inverted on itself: the speed test is the only thing that produces contributions, so keeping it off production guaranteed the map would never fill. It is still at zero today, nine days later, across all three chains. The map is safe to publish because its empty state already says which kind of nothing it is, rather than drawing a blank map under a latency legend and letting the reader infer an answer: "No community samples for this chain yet. The map fills up as people run the speed test: every completed test adds one anonymous point to its city", and "Run a test from here to add the first point". Nothing needed cherry-picking. Both routes have been on main all along; only the DEV_ONLY_ROUTES entries kept them from being served. Removing them also puts the two pages back into the sitemap, the footer, llms.txt and the /rpc hub, which all read the same gate.
This was referenced Sep 30, 2026
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.
What
Removes
/speedtest-rpcand/rpc-mapfromDEV_ONLY_ROUTES.Nothing was cherry-picked: both routes have been on
mainsince they were written. Only the two gate entries kept them from being served, and removing them also restores them to the sitemap, the footer,llms.txtand the/rpchub, which all read the same gate.Why now
They were held from 2026-09-21 with the reason "2 cells, 32 samples: not ready for an audience". That reasoning inverted on itself — the speed test is the only thing that produces contributions, so gating it off production guaranteed the map would never fill.
Verified today:
stm:totalis 0 and every chain returns 0 cells on staging. Nine days of being gated produced nothing, which is what being gated does.Why the empty map is safe to publish
The map's empty state already names the absence instead of implying an answer:
and, on the nearest-areas panel:
src/components/speedtest/rpc-map-client.tsx:622-646.Verified
tsc --noEmitcleanpnpm validate: 241 specs validpnpm test: 368 pass, 0 failVERCEL_ENV=production next build: both routes emitted static with 1h revalidate, and the four/api/speedtest/*handlers build/api/speedtest/whereamianswers correctly on stagingNote
/data-apiis live on production and linked from the product pages but is absent from the sitemap, with no comment explaining it, unlike every other hub. That looks like an omission rather than a decision. Left out of this PR to keep it targeted; worth its own change.