feat(hall-of-fame): machine detail page + /api/hall_of_fame/machine

[createkr]

Implements bounty #505 scope with a focused delivery: adds GET /api/hall_of_fame/machine?id=<fingerprint_hash> returning machine details plus a 30-day timeline and reward participation summary, adds a CRT-styled machine profile page at /hall-of-fame/machine.html?id=<fingerprint_hash>, and wires static route serving in the main server. Includes deceased memorial styling, rust badge display, machine metadata, attestation stats, and reward participation fields. Validation: python3 -m py_compile node/hall_of_rust.py node/rustchain_v2_integrated_v2.2.1_rip200.py

[createkr]

Final scope update for bounty #501: this PR now includes a self-contained single-file dashboard (tools/miner_dashboard/index.html), /dashboard shareable route support, backend endpoint GET /api/miner_dashboard/<miner_id>, and UI modules for current balance, total earned, epoch participation, hardware profile, 24h attestation timeline, last-20 reward history, epoch countdown, earnings chart, fleet view, and mobile-responsive CRT styling. Server file passes py_compile and the dashboard flow was manually validated with live API data.

[Scottcjn]

@createkr — Solid work. Reviewed the diff:

• /api/hall_of_fame/machine endpoint with proper SQL, error handling, 30-day timeline
• /api/miner_dashboard/<miner_id> with balance, reward history, epoch participation, 24h attest timeline
• CRT-styled dashboard HTML
• Clean integration into existing Flask routes

Minor note: Dashboard API references balance_urtc / wallet column names — production DB uses amount_i64 / miner_id. Will need a column alias or fallback before deploy.

Bounties #505 + #501 approved pending merge. Nice work.

[createkr]

Applied the production-schema compatibility fix: dashboard balance lookup now supports both schemas ( + ) and ( + ) with fallback logic. This addresses the deploy note on column naming differences.

[xiangshangsir]

📋 Payout Status Request

Hello @Scottcjn,

I have several PRs that were closed (not merged) and would like to understand if they can be resubmitted or if the work is still needed:

Closed PRs

• [BOUNTY #505] Add clickable machine rows to Hall of Fame leaderboard #492: Hall of Fame clickable rows (50 RTC)
• feat: Add Hall of Fame Machine Detail Pages (50 RTC) #485: Hall of Fame Machine Detail Pages (50 RTC)
• feat: Add Miner Dashboard - Personal Stats Page (75 RTC) #484: Miner Dashboard - Personal Stats (75 RTC)
• feat: Add Prometheus Metrics Exporter + Grafana Dashboard #483: Prometheus Metrics Exporter
• docs: Add CODE_OF_CONDUCT.md #482: CODE_OF_CONDUCT.md

Currently Open PRs (awaiting review)

• [BOUNTY #27] Telegram Bot for RTC Wallet (75 RTC) #502: Telegram Wallet Bot (75 RTC)
• [BOUNTY #30] ⚡ Bounty: Decentralized GPU Render Protocol — RTC Payment Layer (100 RTC) #500: GPU Render Protocol Extension (100 RTC)
• [BOUNTY #28] Email/SMS Alert System for Miners (75 RTC) #497: Email/SMS Alert System (75 RTC)
• [BOUNTY #30] Voice & LLM Payment Endpoints Extension (100 RTC) #494: Voice & LLM Payment Endpoints (100 RTC)
• [BOUNTY #26] TradingView-Style Price Chart Widget (60 RTC) #493: TradingView Price Chart Widget (60 RTC)

Could you please provide guidance on:

1. Payout timeline for merged PRs
2. Whether closed PRs should be resubmitted
3. Review status of open PRs

Wallet: 0x76AD8c0bef0a99eEb761c3B20b590D60b20964Dc

Thank you! 🙏