Metrics and access

Metrics pages present challenge telemetry rather than account-private data: registry status, active challenge counts, runtime readiness, benchmark summaries, and weight aggregation indicators.

• Use metrics to understand public network health.
• Use challenge pages to inspect specific miner or architecture results.
• Use dashboard routes for protected Miner account state after the username/password account gate passes.

Auth, dashboard, and dashboard settings are active for the implemented Miner account scope. Anonymous dashboard requests redirect to auth, and session-bearing requests still pass through server DAL checks before private UI renders.

The implemented scope covers username/password account sign-in, username registration limited to 10 attempts per IP per hour, protected dashboard access, and signed hotkey proof. Other account-provider, contact, admin, billing, organization, analytics, two-factor, validator, creator, builder, and owner-chain features are outside the active website scope.

The miner dashboard overview is username/password gated and scoped to the signed-in Miner account. It shows safe account state, current hotkey summary, challenge participation state, and empty states when no dashboard records exist.

Hotkey linking stays in the existing settings flow: open /dashboard/settings#hotkeys, request a nonce, sign the exact message with the hotkey, and submit the signature for verification. The dashboard provides a shortcut and summary, not a separate proof system.

Challenge rows describe list and overview semantics such as available, active, submitted, and completed participation. Revenue rows describe platform-credit events only.