Skip to content

bench 001: the title says price API, the bench measures onchain data - #3317

Closed
Flotapponnier wants to merge 1 commit into
devfrom
fix/head-lag-onchain-title
Closed

Flotapponnier wants to merge 1 commit into
devfrom
fix/head-lag-onchain-title

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

The board measures the wall clock between an onchain swap event and the moment each provider emits it. "Price API" narrows that to one use of the feed.

The name has moved twice: "Aggregator Head Lag", then "Fastest onchain data API provider", then "Fastest crypto price API" in #2297 on 2026-09-10. The measurement did not move with it, and the subtitle has said "from on-chain swap event to API emission" throughout.

title      Fastest crypto price API, live head lag across 6 data providers
       ->  Fastest onchain data API, live head lag across 6 providers        (58)

seo_title  Fastest crypto price API 2026: live head lag by chain
       ->  Fastest onchain data API 2026: live head lag by chain             (53)

Both stay inside the 35 to 65 character window. Nothing else in the repo carries the old string except video/lab/fixtures/, which fetch_fixtures.py regenerates from the live API, so it refreshes on its own rather than being hand edited.

A retitle resets that page's ranking history, so this is the moment to do it: the page is one of the oldest on the site and the current title has been live for seven weeks.

Gates: pnpm validate 257 specs valid, tsc --noEmit clean, bun test src/ 731 pass 0 fail.

To be cherry-picked onto main after this merges, so prod and staging carry the same title.

"Fastest crypto price API" arrived in #2297 on 2026-09-10, after the board
had been "Fastest onchain data API provider" and, before that, "Aggregator
Head Lag". The measurement never changed with the names: the harness
timestamps an onchain swap event and the moment each provider emits it, and
the subtitle has always said so.

"Price API" narrows that to one use of the feed and sets the wrong
expectation for what the number means. Back to onchain, in both the H1 and
the search title.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant