AeroNyx nodeboard Operator Console Guide
Guide to nodeboard at app.aeronyx.network for Rust privacy node quick install, registration, services, sessions, events, Memory Chain readiness, encrypted storage, codes, and billing.
AeroNyx nodeboard Operator Console Guide
nodeboard is the AeroNyx operator console for managing Rust privacy nodes. The production URL is https://app.aeronyx.network.
nodeboard is the operational control surface for AeroNyx Protocol products: Rust privacy node onboarding, service health, capacity, encrypted packet counters, access policy, events, billing, Memory Chain readiness, encrypted storage capability, and commercial operation.
What nodeboard is
nodeboard helps node owners and infrastructure teams operate AeroNyx services safely. It connects wallet-based operator identity, node registration, node health, service visibility, aggregate sessions, events, access codes, billing views, and policy controls into one dashboard.
The Rust node still runs on the operator server. nodeboard is the control and observability surface that helps operators understand whether that node is ready for real users and future agent workloads.
Core workflows
| Workflow | Purpose |
|---|---|
| Wallet sign-in | Operator identity and session access. |
| Add node | Generate a short-lived registration code plus preview/install commands. |
| Preview install | Copy a read-only command that runs install.sh --quick --print-plan before host changes. |
| Quick install | Copy the one-command Linux/systemd install command using install.sh --quick. |
| Node list | See registered nodes, online status, region, health, and basic capacity. |
| Node detail | Review service health, sessions, metrics, policy, and operational state. |
| Services | Inspect capacity, DNS, transport metadata, encrypted counters, and commercial placement readiness. |
| Memory Chain readiness | Display encrypted record capability, sync state, and module health when enabled. |
| Encrypted storage readiness | Display encrypted object capability and storage pressure without exposing plaintext. |
| Sessions | Review aggregate privacy network sessions without exposing private browsing or chat data. |
| Events | Track operational events and control-plane activity. |
| Codes | Manage private access codes and registration-related operator flows. |
| Billing | Review commercial service accounting and billing state. |
| Settings | Manage operator-facing preferences and account settings. |
Adding a Rust privacy node
- Open https://app.aeronyx.network.
- Sign in with the supported wallet flow.
- Open Add Node.
- Generate a registration code.
- Copy and run the Preview command on the Linux server:
curl -fsSL https://raw.githubusercontent.com/AeroNyxNetwork/AeroNyx/main/deploy/node/install.sh -o /tmp/aeronyx-node-install.sh && chmod +x /tmp/aeronyx-node-install.sh && AERONYX_REGISTRATION_CODE='<NODEBOARD_CODE>' /tmp/aeronyx-node-install.sh --quick --print-plan
- If the plan looks correct, copy and run the Install command:
curl -fsSL https://raw.githubusercontent.com/AeroNyxNetwork/AeroNyx/main/deploy/node/install.sh -o /tmp/aeronyx-node-install.sh && chmod +x /tmp/aeronyx-node-install.sh && sudo AERONYX_REGISTRATION_CODE='<NODEBOARD_CODE>' /tmp/aeronyx-node-install.sh --quick
- Wait for the Rust node to register and send heartbeats.
- Confirm the node appears online in nodeboard.
Services page
The Services page should make the first screen readable while allowing deeper inspection through expandable modules or detail panels.
First-level modules should focus on:
- node online and heartbeat state
- capacity summary
- aggregate active sessions
- encrypted traffic
- encrypted packet forwarding
- packet drops and health warnings
- commercial placement readiness
Detail panels can hold:
- IP pool capacity, used IPs, and remaining IPs
max_connections- policy
max_sessions - conntrack and file descriptor pressure
- pps and bps
- DNS resolver ownership and status
- transport capability metadata
- Memory Chain capability and sync state
- encrypted storage capability and storage pressure
Memory Chain and encrypted storage
Memory Chain is the encrypted record layer direction for AeroNyx. It gives the protocol a way to preserve versioned private state, such as conversation memory, node service records, encrypted storage checkpoints, and future agent workflow state.
nodeboard should present this as operational capability, not plaintext content. Operators need to know whether the module is enabled, synced, healthy, and within storage limits. They should not see user messages, decrypted memory, private keys, or raw personal data.
Agent-to-agent protocol services
AeroNyx is designed for a future where autonomous agents need private network access, encrypted communication, and verifiable state exchange. nodeboard should eventually show whether a node can serve agent workloads, including:
- private routing capability
- encrypted protocol capability
- Memory Chain readiness
- encrypted storage readiness
- payment or settlement readiness
- capacity available for agent traffic
Operational safety
nodeboard should expose aggregate service and node metadata only. It should not expose:
- packet payloads
- DNS contents
- user destinations
- domains or URLs
- browsing history
- voucher secrets
- wallet-level traffic
- raw client public IP activity
- decryptable chat history
- encrypted storage plaintext
- Memory Chain plaintext
- registration code history after expiration
Recommended operator routine
Daily:
- check node online status
- review Services capacity warnings
- review Events for repeated failures
- confirm latest heartbeat freshness
Before maintenance:
- check aggregate active sessions
- avoid forced restart during high usage
- run Rust healthcheck
- use staged upgrades before planned restart windows
After maintenance:
- confirm
aeronyx-serveris active - confirm nodeboard sees fresh heartbeat
- confirm transport metadata is active
- review packet drops and capacity warnings
- confirm Memory Chain or encrypted storage modules remain healthy when enabled