Dashboard

Last updated: 2026-06-28

The mining dashboard is an operator and network-control surface. It is not the same product as the customer Portal. Some dashboard actions read from or write to configured contracts, so the UI shows explicit environment labels and transaction warnings.

flowchart TB
  Dashboard["Mining dashboard"]
  Wallet["Operator wallet"]
  Contracts["Contracts"]
  Router["Router/session data"]
  Models["Model catalog"]
  Stats["Stats and heatmaps"]
  Admin["Admin/write actions"]

  Wallet --> Dashboard
  Dashboard --> Contracts
  Dashboard --> Router
  Dashboard --> Models
  Dashboard --> Stats
  Dashboard --> Admin
  Admin --> Contracts

Covered Areas

Area	What it shows or controls
Cognitive rounds	Request, create, prepare, precommit, and commit lifecycle visibility for network-assigned tasks.
Sessions	Session creation, queue state, private/dedicated session flows, payment/deposit state, and result inspection.
Stats	Uptime, heartbeat pings, task counters, failure ratios, validator feedback, quantitative stats, qualitative stats, and network metrics.
Network views	Node maps, heatmaps, reputation, model capacity, and performance views.
Model catalog	Model ID table, model-capacity counts, and session model selection.
Pricing	Pricing/payment configuration surfaces.
Admin	Contract/admin actions that require strong permission warnings.

See Model Catalog for the current dashboard/runtime model ID list.

Dashboard Modules

Module	Purpose
Cognitive tab	Mining explorer for cognitive rounds, precommit points, validator feedback, and cognitive-level scoring.
NodeStats tab	Node performance tracker for uptime, reliability, reputation, task completion, and validation feedback.
Session tab	User/developer interaction layer for creating, managing, and verifying inference sessions.
Smart Job Queue	Routes workloads using node specs, cognitive level, model capacity, and session state.
Quantitative stats	Compares network task outputs with numeric and embedding-distance style checks.
Qualitative stats	Adds usefulness/coherence-oriented validation signals for result quality.

Operator Requirements

Requirement	Why
Network selector	Prevents testnet/mainnet confusion.
Contract address table	Makes read/write targets explicit.
Write-action warnings	Protects operators from accidental transactions.
Screenshots	Shows how the dashboard differs from Portal.
Auth model	Clarifies who can use admin views.

Model Catalog Behavior

The dashboard reads node model metadata and counts supported model indexes when creating or inspecting sessions. The canonical model list lives in Model Catalog, with dashboard-specific behavior summarized here.

Behavior	Documentation note
Dedicated sessions	Can expose models differently from public/shared session creation.
Disabled IDs	Some model IDs are hidden outside dedicated mode.
Capacity-aware selection	Extended model IDs require active supporting node capacity.
Operator visibility	Dashboard views expose enough metadata for operators to understand session/model mismatch.