nodeboard Features Reference
Reference for nodeboard dashboard, nodes, services, sessions, events, Memory Chain readiness, encrypted storage, codes, billing, and settings.
nodeboard Features Reference
nodeboard is the operator-facing console for AeroNyx Rust privacy nodes and related privacy network services.
Dashboard
The dashboard should summarize:
- total registered nodes
- online nodes
- aggregate active sessions
- encrypted traffic
- encrypted packet forwarding
- capacity warnings
- recent events
- Memory Chain or encrypted storage module status when enabled
Nodes
The Nodes area should support:
- node registration
- node status
- region and capability metadata
- heartbeat freshness
- capacity fields
- service configuration
- safe maintenance visibility
Services
Services should be layered. The first screen should show only high-signal operational state. Deep technical metrics should be available through detail panels.
First-level:
- service health
- capacity
- encrypted traffic
- encrypted packet forwarding
- packet drops
- commercial readiness
Details:
- IP pool capacity
- used IPs
- remaining IPs
max_connections- policy
max_sessions - conntrack
- file descriptors
- pps
- bps
- DNS status
- transport metadata
- Memory Chain readiness
- encrypted storage readiness
Sessions
Sessions should show aggregate privacy network usage, not private user activity. The UI should avoid revealing destinations, domains, URLs, DNS contents, or packet payloads.
Events
Events should help operators diagnose service state:
- registration events
- heartbeat changes
- service warnings
- capacity risk
- access code changes
- billing state changes
- Memory Chain sync warnings
- encrypted storage pressure warnings
Private access codes
Private access codes are operator credentials for controlled access flows. They should be handled like secrets and not shared in public support channels.
Billing
Billing should connect commercial operation with transparent aggregate usage. It should not expose user-level browsing or message content.
Memory Chain and encrypted storage
When enabled, nodeboard should show capability and health:
- module status
- encrypted object count
- storage pressure
- last checkpoint
- sync state
- verification status
The UI must not show plaintext memory records, decrypted chat logs, user storage contents, or keys.