Skip to content

Rebuild the miner details page into a decision-support dashboard #1324

Description

@Dexterity104

Summary

The miner details page currently presents earnings, score, contribution history, and standing as a set of loosely connected cards. Reading it top to bottom does not make it clear how a miner ranks against the rest of the network, what is gating their earnings, or which single action would raise their score next.

This rebuilds the page into one decision-support dashboard that answers three questions at a glance: where the miner stands, what is locked, and what to do next.

Motivation

The existing layout spreads related signals across separate sections (credibility chart, insights card, score levers, open-PR risk, repo standings). The raw figures carry little meaning on their own: a score of 12.5 or 41 merged PRs says nothing without a peer baseline, and the actions a miner could take to improve are scattered across three different cards.

A consolidated dashboard would:

  • Show headline performance (earnings, score, activity, collateral) with peer percentiles, so absolute numbers gain context ("top 8%" rather than a bare figure).
  • Fold the old earning levers, insights, and open-PR-risk prompts into one severity-ranked "what to do next" list, with each step linking to the page section where it can be acted on.
  • Surface per-repository standing and unlock progress, driven by the live eligibility gates rather than the retired Bronze/Silver/Gold tier ladder.
  • Keep contribution detail (pull requests, open issues, activity) filterable by a 1D/7D/30D range that matches the subnet scoring window.

The result reads as a single coherent view instead of a stack of unrelated widgets, and points a miner straight at the highest-impact next action.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfeatureNet-new functionality

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions