Skip to content

fix(ledger): only render #1 chips on the leaderboard row#192

Merged
Flotapponnier merged 1 commit into
devfrom
fix/leaderboard-chips-leaders-only
May 29, 2026
Merged

fix(ledger): only render #1 chips on the leaderboard row#192
Flotapponnier merged 1 commit into
devfrom
fix/leaderboard-chips-leaders-only

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Reported visually on wallet-labels-coverage (11 chain dimensions): every row was rendering all 11 chips, most as neutral 'not leading' tags → ~44 chips across 4 rows, completely overwhelming.

Default ChainCoverageChip to leaders-only mode on the bench leaderboard. Non-leader chips hard-skipped. The chain tabs on the bench already provide precise per-chain rankings; this chip is a quick scan aid for 'where does this provider top the field today' — that signal vanishes when buried under 9 neutral chips per row.

leadersOnly=false escape hatch kept so /products/[slug] or future consumers can opt back into the full coverage view.

Reported visually: on wallet-labels-coverage (11 chain dimensions), every row was showing all 11 chain chips (Ethereum, Solana, BNB Chain, Base, Arbitrum, Polygon, Optimism, TON, Stellar, XRP, Bitcoin) — most rendered as neutral 'not leading on this chain' chips. Total noise: ~44 chips across 4 rows.

Default ChainCoverageChip to leaders-only mode. Non-leader chips are hard-skipped. The bench page chain tabs already provide precise per-chain rankings; this chip is a quick scan aid for 'where does this provider currently top the field' — that signal disappears when buried under 9 neutral chips per row.

leadersOnly=false escape hatch kept so /products/[slug] (or any future consumer) can opt back into the full coverage view.
@Flotapponnier
Flotapponnier merged commit a5e2efb into dev May 29, 2026
@Flotapponnier
Flotapponnier deleted the fix/leaderboard-chips-leaders-only branch June 9, 2026 21:42
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