feat: frontend user badge display #202

Merged
eztvdpqx5 merged 8 commits from badges-1 into master 2026-03-23 21:39:50 +00:00
eztvdpqx5 commented 2026-03-22 03:21:37 +00:00 (Migrated from github.com)
  • Replace the "Last Submission" stat card with an "Achievements" section on the user dashboard
  • Display SVG medal badges (gold/silver/bronze) for each round a user has participated in, based on rank
  • Badges link to the corresponding block on mempool.space and show rank details on hover
image image
- Replace the "Last Submission" stat card with an "Achievements" section on the user dashboard - Display SVG medal badges (gold/silver/bronze) for each round a user has participated in, based on rank - Badges link to the corresponding block on mempool.space and show rank details on hover <img width="1593" height="344" alt="image" src="https://github.com/user-attachments/assets/b821a105-80e1-4f46-9a60-3273a9b00c49" /> <img width="1621" height="346" alt="image" src="https://github.com/user-attachments/assets/77b24a92-58ba-4042-873f-68e35e4d2402" />
eztvdpqx5 commented 2026-03-22 13:13:20 +00:00 (Migrated from github.com)

another color choice, debug setup to show all 3
image

another color choice, debug setup to show all 3 <img width="1586" height="455" alt="image" src="https://github.com/user-attachments/assets/30961fcd-fdd3-41f6-9073-497b4abf9e01" />
parabitdev (Migrated from github.com) approved these changes 2026-03-23 16:55:54 +00:00
parabitdev (Migrated from github.com) left a comment

LGTM

We still have last submitted on the individual workers so it is probably good to remove the account-wide one. I was concerned for a moment before I remembered as it is a VERY useful troubleshooting tool for users.

LGTM We still have `last submitted` on the individual workers so it is probably good to remove the account-wide one. I was concerned for a moment before I remembered as it is a VERY useful troubleshooting tool for users.
eztvdpqx5 commented 2026-03-23 21:10:19 +00:00 (Migrated from github.com)

are we worried at all in rounds-collector.ts about both the round participant fetch (line ~307/314) and block participant fetch (line ~355/362) write to the single error_message column on the rounds table? should we have separate columns or is the same okay?

are we worried at all in rounds-collector.ts about both the round participant fetch (line ~307/314) and block participant fetch (line ~355/362) write to the single error_message column on the rounds table? should we have separate columns or is the same okay?
eztvdpqx5 commented 2026-03-23 21:31:52 +00:00 (Migrated from github.com)

LGTM then

LGTM then
Sign in to join this conversation.
No description provided.