feat(hl-frontends): logos + registry + YAML for 6 newly identified frontends - #772
Merged
Merged
Conversation
Following the on-chain referral code cross-reference that identified 6 of the 15 anonymous 0x… builder addresses on the HL frontends leaderboard, wire each into the editorial surface: - Logos: invo.png, bitget-wallet.png, marsgo.jpg, defi-saver.svg, unitywallet.png (from official brand sites). metamask-alt aliased to the existing metamask.svg in the manifest since it's the same brand split across two on-chain addresses. - provider-registry.ts: 5 new entries (description + url + twitter) for the standalone brands. metamask-alt intentionally omitted so /products/metamask-alt falls back to plain rendering (no separate product surface for a secondary address of an already-listed brand). - hyperliquid-frontends.yml: 6 providers entries with the same shape as the existing 60+ frontends (Prom queries pre-wired for p50/p90/p99/mean/success/sample/series). The builders.json on the HL node was already updated and the harness restarted in a prior step; this PR ships the editorial scaffolding the bench page reads when those builder labels surface.
Uh oh!
There was an error while loading. Please reload this page.
Flotapponnier pushed a commit
that referenced
this pull request
Jun 28, 2026
…ks-v20 Flushes stale snapshots that don't include the 6 newly identified HL frontends (invo, bitget-wallet, defi-saver, unitywallet, marsgo, metamask-alt) added in #772. Without this, /products/<slug> 404s for them even after the YAML + builders.json updates landed because the cached provider list still mirrors the pre-deploy snapshot. Same pattern as the v11→v15/v15→v19 historical bumps.
Flotapponnier added a commit
that referenced
this pull request
Jun 28, 2026
…ks-v20 (#773) Flushes stale snapshots that don't include the 6 newly identified HL frontends (invo, bitget-wallet, defi-saver, unitywallet, marsgo, metamask-alt) added in #772. Without this, /products/<slug> 404s for them even after the YAML + builders.json updates landed because the cached provider list still mirrors the pre-deploy snapshot. Same pattern as the v11→v15/v15→v19 historical bumps. Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier added a commit
that referenced
this pull request
Jun 28, 2026
…775) The 6 builders identified in #772 (invo, bitget-wallet, defi-saver, unitywallet, marsgo, metamask-alt) have their builders.json entry on the HL node, which means the harness now emits the friendly name as the Prom label (e.g. builder="invo") instead of the 8-char hex prefix (builder="0x557edb25"). The old hex-prefixed YAML providers were still querying the dead Prom labels, so they collapsed to null and the materialize worker dropped them. That's why /products/invo etc. 404'd after the deploy — the named entries existed in the YAML but the bench snapshot only carried the dead hex ranks beside them. Remove the 6 dead hex entries. The 9 still-anonymous hex addresses stay as-is since the harness still emits their hex prefix. Co-authored-by: Florent Tapponnier <contact@mobula.io>
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 freeto 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.
Summary
Following the on-chain HL referral code cross-reference that identified 6 of the 15 anonymous `0x…` builder addresses on `/benchmarks/hyperliquid-frontends`, wire each into the editorial surface so they get proper product pages instead of plain text rows.
What's wired
`/opt/hl-bench/builders.json` on the HL node was already updated in the prior fix step and the harness restarted; this PR ships the editorial scaffolding the bench page reads when those builder labels surface.
Test plan after deploy