fix(243): scope every Robinhood Chain RPC claim to the Singapore probe - #2272
Merged
Conversation
The page and the report presented a single-origin measurement as a
chain-wide ranking ("fastest on Robinhood Chain", "the best of any
keyed provider on the chain") and justified the origin with an
unsourced claim about the chain's Asia-Pacific infrastructure.
Round-trip latency to a keyed RPC depends on where the probe sits
relative to the provider's serving node, so the ranking is
origin-dependent. Every title, headline, FAQ and report sentence now
says "from Singapore" and states that scope explicitly. The
Asia-Pacific justification is removed everywhere. The bench remains
pinned to the Singapore probe (aggregate_filters unchanged).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CpArutAtXuBb1BVNUDXoYA
Flotapponnier
force-pushed
the
hotfix/243-scope-singapore
branch
from
September 8, 2026 09:35
45d0b6e to
bfbbc80
Compare
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
1 participant
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.
Hotfix against
main(prod), text only.Why
The bench page and the August report presented a single-origin measurement as a chain-wide ranking ("Fastest Robinhood Chain RPC", "the best of any keyed provider on the chain"), justified by a claim about the chain's Asia-Pacific infrastructure that has no source in the spec or in Robinhood's docs. Round-trip latency to a keyed RPC depends on where the probe sits relative to the provider's serving node, so the ranking is origin-dependent by nature.
What changes
title,seo_title,seo_description,subtitle: "measured from Singapore" / "scoped to that origin". The templated headline sentence therefore reads "…posts the lowest rpc latency at 3 ms (p50, 24h) on Fastest Robinhood Chain RPC with API key, measured from Singapore: …".seo_intro,abstract, methodology cadence bullet, both FAQs: origin stated, scope stated, Asia-Pacific sentence removed.2026-08-fastest-robinhood-chain-rpc.mdx: title, hero finding, body claim and conclusion rescoped to "from our Singapore probe".What does not change
The bench stays pinned to the Singapore probe (
aggregate_filters: region: sgpuntouched). No additional region is surfaced in prod. Zero code, zero query changes.ALL SPECS VALID.🤖 Generated with Claude Code
https://claude.ai/code/session_01CpArutAtXuBb1BVNUDXoYA