Website navigation
How the public website routes map to product areas and active account surfaces.
Sources
Top-level routes
The website presents public pages first, then routes account work through active Miner auth and protected dashboard pages.
| Route | Behavior |
|---|---|
| / | Landing page with concise positioning and entry points. |
| /challenges | Registry-style challenge index. |
| /metrics | Benchmark and telemetry overview. |
| /docs | This documentation system. |
| /auth | Active sign-in page for username/password login and rate-limited registration. |
| /dashboard | Username/password protected Miner dashboard overview. Anonymous visitors redirect to /auth?next=/dashboard. |
Account surfaces
Authentication is active for Miner accounts. The dashboard and settings routes are server-protected and only render after the username/password account gate and Miner authorization pass. The dashboard overview summarizes safe profile state, hotkey status, challenge participation, and platform-credit revenue events.
Active access
Docs should describe these routes as active. Keep dashboard claims scoped to username/password access, settings-based hotkey signature linking, challenge overview records, and platform-credit events.
| Route | Access model |
|---|---|
| /auth | Public page for username/password login and rate-limited registration. |
| /dashboard | Protected Miner overview with username/password account checks, safe user DTOs, challenge state, and platform-credit event summaries. |
| /dashboard/settings | Protected account settings for username account state, sessions, credential rows, and hotkey proof controls. |
| /dashboard/settings#hotkeys | Existing signed-message flow for nonce creation, hotkey signature verification, and active hotkey link creation. |
| /api/auth/** | Better Auth handlers running on the server. |
| /api/telegram/** | Removed verification endpoints that return 410 Gone for legacy callers. |
| /api/hotkeys/** | Signed nonce hotkey proof endpoints for protected Miner accounts. |