answers: rewrite two head-to-head YAMLs whose tokens pulled from the wrong axis - #1130
Merged
Merged
Conversation
…wrong axis
Both YAMLs were shipping short_answer / seo_description / faq copy that
referenced {{best_name}} and {{best_p50}}. renderTemplate resolved those
tokens against the underlying bench's global leader, but the questions
frame a head-to-head that the bench does not answer on the same axis:
* polymarket-vs-kalshi-resolution-speed referenced polymarket-resolution-delay,
whose dimensions are market categories (Crypto / Sports / Politics),
not venues. {{best_name}} returned the fastest category and the page
rendered 'Crypto currently resolves faster at 11.3 min' - grammatically
fine, factually wrong for a Polymarket vs Kalshi question. Kalshi is
also not measured in the bench today.
Fix: rewrite the copy to describe what the bench actually measures
(Polymarket resolution delay per category, live onchain from UMA
events on Polygon), state explicitly that Kalshi ingestion is pending,
and point at the bench page for the numbers. No {{}} tokens.
* helius-vs-triton-vs-quicknode-solana referenced solana-tx-landing,
which includes Jito bundle submission as a separate priority-lane
comparator. {{best_name}} could name Jito, mismatching the three
RPC providers in the question and reading as broken output.
Fix: rewrite the copy to describe the harness methodology, name the
three providers explicitly, and flag Jito's presence on the same
leaderboard so a reader who lands here from Google or a LLM answer
understands why the aggregate leader can be Jito rather than one of
the three RPCs. No {{}} tokens.
Both YAMLs still list status: live and short_answer is above the schema
40-char floor. Related answers unchanged. No changes to any other YAML.
Verified:
grep for {{}} tokens in both YAMLs: 0 hits
bun test src/lib: 64 pass 0 fail
pre-existing typecheck error on provider-registry.ts:1247 is unrelated
(present on dev before this branch, confirmed via git stash test)
Flotapponnier
added a commit
that referenced
this pull request
Jul 12, 2026
…wrong axis (#1130) Both YAMLs were shipping short_answer / seo_description / faq copy that referenced {{best_name}} and {{best_p50}}. renderTemplate resolved those tokens against the underlying bench's global leader, but the questions frame a head-to-head that the bench does not answer on the same axis: * polymarket-vs-kalshi-resolution-speed referenced polymarket-resolution-delay, whose dimensions are market categories (Crypto / Sports / Politics), not venues. {{best_name}} returned the fastest category and the page rendered 'Crypto currently resolves faster at 11.3 min' - grammatically fine, factually wrong for a Polymarket vs Kalshi question. Kalshi is also not measured in the bench today. Fix: rewrite the copy to describe what the bench actually measures (Polymarket resolution delay per category, live onchain from UMA events on Polygon), state explicitly that Kalshi ingestion is pending, and point at the bench page for the numbers. No {{}} tokens. * helius-vs-triton-vs-quicknode-solana referenced solana-tx-landing, which includes Jito bundle submission as a separate priority-lane comparator. {{best_name}} could name Jito, mismatching the three RPC providers in the question and reading as broken output. Fix: rewrite the copy to describe the harness methodology, name the three providers explicitly, and flag Jito's presence on the same leaderboard so a reader who lands here from Google or a LLM answer understands why the aggregate leader can be Jito rather than one of the three RPCs. No {{}} tokens. Both YAMLs still list status: live and short_answer is above the schema 40-char floor. Related answers unchanged. No changes to any other YAML. Verified: grep for {{}} tokens in both YAMLs: 0 hits bun test src/lib: 64 pass 0 fail pre-existing typecheck error on provider-registry.ts:1247 is unrelated (present on dev before this branch, confirmed via git stash test) Co-authored-by: Florent Tapponnier <contact@mobula.io>
6 tasks
Flotapponnier
pushed a commit
that referenced
this pull request
Jul 12, 2026
Answer YAMLs: rewrite six pages whose {{best_name}} / {{best_p50}} tokens could
resolve outside the question's named cohort (oracle-deviation is per pair not
per provider; rpc-capabilities includes 14 chain gateways; keyed RPC bench
includes Chainstack/Ankr/Helius; bridge-fee cohort was Stargate/Squid/Socket
not in bench; perp-fees added Paradex/Extended/Polymarket). Same pattern as
PR #1130.
Bench YAMLs: fix |predicted, realized| -> |predicted - realized| (3 spots in
gas-estimation), lag_seconds = a, b -> subtract in l1-finality, drop
contradictory 1RPC provider block from rpc-capabilities (methodology already
says delisted 2026-07-09), sweep stale "Merkle" references and provider
counts on base/bnb/megaeth cluster.
Compare page: FAQ template rendered "a s value" / "a count value" because
${unit} was interpolated bare. Fix by including the fmtUnit(p50, unit) for
both providers. Also add Dataset.identifier to satisfy Google's rich-result
requirement.
Answer + chain page JSON-LD: add Article.image (bench OG) on answers, add
TechArticle.datePublished on chain sub-pages.
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.
Both YAMLs were shipping copy that referenced {{best_name}} and {{best_p50}}. renderTemplate resolved those tokens against the underlying bench's global leader, but the questions frame a head-to-head that the bench does not answer on the same axis. The audit called this out today.
polymarket-vs-kalshi-resolution-speed
Referenced
polymarket-resolution-delay, whose dimensions are market categories (Crypto / Sports / Politics), not venues.{{best_name}}returned the fastest category and the page rendered Crypto currently resolves faster at 11.3 min — grammatically fine, factually wrong for a Polymarket vs Kalshi question. Kalshi is also not currently measured in the bench.Fix: rewrite the copy to describe what the bench actually measures (Polymarket resolution delay per category, live onchain from UMA events on Polygon), state explicitly that Kalshi ingestion is pending, and point at the bench page for the numbers. Zero
{{}}tokens.helius-vs-triton-vs-quicknode-solana
Referenced
solana-tx-landing, which includes Jito bundle submission as a separate priority-lane comparator.{{best_name}}could name Jito, mismatching the three RPC providers in the question and reading as broken output.Fix: rewrite the copy to describe the harness methodology, name the three providers explicitly, and flag Jito's presence on the same leaderboard so a reader who lands here from Google or a LLM answer understands why the aggregate leader can be Jito rather than one of the three RPCs. Zero
{{}}tokens.Verified
{{}}tokens in both YAMLs: 0 hitsbun test src/lib: 64 pass, 0 fail