Nodeboard Features Reference

This page is the compact product reference for Nodeboard. For operating procedures, use the Nodeboard Operator Console Guide.

Area	Purpose	First-level information
Dashboard	Fleet attention and overall readiness	Online/stale/offline nodes, open incidents, admission state, recent operator actions
Nodes	Search and compare individual nodes	Name, region, visibility, health, sessions, capacity decision, current action
Services	Compare operational domains	Privacy Network, Discovery & Relay, MemChain & Storage, Runtime
Registration Codes	Safely onboard a node	One-time code state, install progress, handoff to node detail
Events	Audit operational change	Source, severity, lifecycle, action, closure
Access	Manage restricted-node access	Code policy, status, expiry, revocation
Billing	Operator-facing commercial records	Aggregate plan or settlement status only; no user traffic history

Node detail modules

Module	Evidence
Overview	Identity, region, public/private role, heartbeat freshness, version
Capacity	IP pool, sessions, limits, bandwidth policy, conntrack, file descriptors, packet drops, pps/bps, disk, CPU, memory
Privacy Network	Tunnel readiness, aggregate encrypted bytes/packets, placement policy
Discovery	Signed peer view, cache source, routeable candidates, capability consistency, restart recovery
Encrypted Relay	ChatRelay/OnionMiddle readiness, probes, proof outcomes, terminal delivery, admission
MemChain & Storage	Mode, encrypted persistence, commitment checks, witness state, storage capacity
Maintenance	Restart/upgrade state, active-session guard, target version, health verification
Events	Node-scoped audit and incident closure

State vocabulary

Nodeboard uses explicit states instead of ambiguous colors:

healthy: fresh evidence and no active blocker
attention: service is running but an operator should review risk
degraded: capacity or protocol quality is reduced
blocked: a hard gate prevents admission or an action
stale: the last evidence is too old to trust
not_reported: the node or backend has never supplied the field
maintenance: intentionally unavailable for new work

Missing telemetry must never be displayed as zero or healthy.

Capacity decision contract

The backend and Rust runtime may provide a structured operator recommendation:

json

{
  "status": "accepting",
  "reason": "accepting",
  "active_sessions": 12,
  "max_sessions": 500,
  "maintenance_mode": false,
  "traffic_capacity_status": "within_limit"
}

Nodeboard turns this contract into a decision and keeps supporting counters on node detail. The recommendation does not replace raw evidence; it gives the operator a stable first action.

Discovery and relay contract

The UI distinguishes:

Evidence	Meaning
signed peer	Descriptor identity and signature verified
routeable peer	Endpoint passed a fresh reachability check
synthetic probe	Controlled opaque test envelope completed
accepted relay	Runtime accepted or forwarded an opaque envelope
verified client delivery	Terminal signed receipt authenticated for a real client delivery
restart continuity	Signed proof state restored after process restart

These signals must not be collapsed into a single “messages delivered” number.

Command lifecycle

Remote actions use the following durable states:

pending → sent → executing → completed | failed | timeout

Each command record contains the operator, target node, action, request time, lifecycle timestamps, result class, and post-action verification. Secrets and private user data are excluded.

Registration lifecycle

A registration entry may move through:

not_started → planning → running → completed | failed

The UI should expose the current phase, safe retry action, and linked node after successful registration. Consumed registration secrets are never returned.

Privacy contract

Nodeboard is an operational control plane. It may process aggregate health, capacity, policy, proof, and audit metadata. It must not become a traffic analytics product and must not expose packet payloads, DNS contents, destinations, browsing history, encrypted-message plaintext, private memory, client public IP activity, voucher secrets, private keys, or wallet-level traffic.