Skip to content

the two release blockers the SEO audit found: a headline the page disowns, and a leader that is not on its board - #3023

Merged
Flotapponnier merged 1 commit into
devfrom
fix/ws-headline-and-perp-intro
Oct 17, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
fix/ws-headline-and-perp-intro

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

the two release blockers the SEO audit found: a headline the page disowns,
and a leader that is not on its board

The block-push pages quoted the number their own methodology calls an
artifact.
Every surface that cites these six pages said "GetBlock posts
the lowest push lag at 0.4 ms", while the spec two screens below says the
winner reads zero by construction and a coarse first bucket turns that into
an interpolation artifact. On hyperliquid-rpc-ws it was not merely weak but
false: "Chainstack pushes HyperEVM blocks first" with Chainstack at 60.6 ms,
a figure no provider that actually arrived first could post, since it would
sit inside the first histogram bucket. The board under the claim contradicts
it.

One string feeds the TL;DR, the StatisticalReport, /api/stat, /api/citable
and llms.txt, so one branch in citation.ts fixes five surfaces. It says what
the measurement supports: who has the lowest median lag, whether that lands
inside the first bucket, and how far the runner-up trails. The gap is the
figure a reader can act on, which is the same conclusion the hub reached
yesterday for the same reason.

The copy follows. Three sentences per spec told the reader to "read the win
rate": the table has p50, p90, p99 and Success, the harness emits only the
lag histogram, and no placeholder exists for a win share. Pointing at a
column that does not exist is worse than saying nothing, and FAQ 1 went
further and asserted the leader "wins most per-block races". Both now point
at the gap and at p99. A win share can be built from the bucket rates later,
and only then may the copy claim one.

The new descriptions are 136 to 149 characters for every chain and leader,
so the snippet cap never reaches them.

perp-capital-efficiency named a leader with no row. The intro read
"Gains supports over 40 active markets per $1M of trading TVL" and called a
"400x gap", while the TL;DR, the meta description and /api/stat all name
Ostium at 19.95 and Gains is absent from the twelve ranked venues. Two
hand-typed figures, neither checkable, contradicting the page above the
fold. It now reads the board through placeholders and keeps the
architectural point it was making. {{ranked_count}} is deliberately not
used: it is not a supported placeholder and would print raw.

Still open from the audit, deliberately not in this change: the six WS pages
are near-identical (Jaccard 0.98 on the first 300 words) and nothing links
to them from /rpc or the chain pages. That is differentiation work, not a
correctness fix, and it does not block the release.

Gates: 253 specs valid, tsc clean, 597 tests.

…owns,

and a leader that is not on its board

**The block-push pages quoted the number their own methodology calls an
artifact.** Every surface that cites these six pages said "GetBlock posts
the lowest push lag at 0.4 ms", while the spec two screens below says the
winner reads zero by construction and a coarse first bucket turns that into
an interpolation artifact. On hyperliquid-rpc-ws it was not merely weak but
false: "Chainstack pushes HyperEVM blocks first" with Chainstack at 60.6 ms,
a figure no provider that actually arrived first could post, since it would
sit inside the first histogram bucket. The board under the claim contradicts
it.

One string feeds the TL;DR, the StatisticalReport, /api/stat, /api/citable
and llms.txt, so one branch in citation.ts fixes five surfaces. It says what
the measurement supports: who has the lowest median lag, whether that lands
inside the first bucket, and how far the runner-up trails. The gap is the
figure a reader can act on, which is the same conclusion the hub reached
yesterday for the same reason.

The copy follows. Three sentences per spec told the reader to "read the win
rate": the table has p50, p90, p99 and Success, the harness emits only the
lag histogram, and no placeholder exists for a win share. Pointing at a
column that does not exist is worse than saying nothing, and FAQ 1 went
further and asserted the leader "wins most per-block races". Both now point
at the gap and at p99. A win share can be built from the bucket rates later,
and only then may the copy claim one.

The new descriptions are 136 to 149 characters for every chain and leader,
so the snippet cap never reaches them.

**perp-capital-efficiency named a leader with no row.** The intro read
"Gains supports over 40 active markets per $1M of trading TVL" and called a
"400x gap", while the TL;DR, the meta description and /api/stat all name
Ostium at 19.95 and Gains is absent from the twelve ranked venues. Two
hand-typed figures, neither checkable, contradicting the page above the
fold. It now reads the board through placeholders and keeps the
architectural point it was making. `{{ranked_count}}` is deliberately not
used: it is not a supported placeholder and would print raw.

Still open from the audit, deliberately not in this change: the six WS pages
are near-identical (Jaccard 0.98 on the first 300 words) and nothing links
to them from /rpc or the chain pages. That is differentiation work, not a
correctness fix, and it does not block the release.

Gates: 253 specs valid, tsc clean, 597 tests.
@Flotapponnier
Flotapponnier merged commit 915ce62 into dev Oct 17, 2026
2 checks passed
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