Install and Register an AeroNyx Rust Privacy Protocol Node

AeroNyx Rust nodes are the operator-run infrastructure layer for the AeroNyx privacy protocol. nodeboard is the operator console used to generate private registration codes, install nodes, inspect capacity, review health, and guide upgrades.

This page is the standard production onboarding flow. A normal operator should copy one command from nodeboard and let it perform the full path:

clone or pull main -> preview plan -> install/register -> status -> healthcheck

Production operator console: https://app.aeronyx.network

Open-source Rust repository: https://github.com/AeroNyxNetwork/AeroNyx

Product boundary

Do not describe nodeboard as a VPN panel. nodeboard is the operator console for running AeroNyx privacy protocol nodes.

The Rust node may carry private routing, encrypted packet forwarding, encrypted service telemetry, and future encrypted storage or Memory Chain capabilities. Public observability must stay aggregate: no packet payloads, DNS contents, destinations, domains, URLs, browsing history, voucher secrets, client public IPs, or wallet-level traffic.

The one command operators should use

In nodeboard, open Registration Codes, create a private registration code, and copy the generated quickstart command.

The command is intentionally shaped like this:

bash

git clone https://github.com/AeroNyxNetwork/AeroNyx.git /opt/aeronyx ||   git -C /opt/aeronyx pull --ff-only origin main

cd /opt/aeronyx
sudo ./deploy/node/aeronyx-node.sh quickstart   --registration-code "<nodeboard-private-registration-code>"   --api-base "https://api.aeronyx.network/api"   --repo-dir "$PWD"

nodeboard generates the exact command with the right registration code. Operators should not hand-type secrets.

What quickstart does

deploy/node/aeronyx-node.sh quickstart is the production entrypoint. It keeps the operator away from the older multi-script workflow.

The wrapper performs:

Repository readiness - validates that it is running inside the AeroNyx repository.
Preview plan - shows what will be installed, where the service files live, which API base will be used, and which registration code source is selected.
Explicit confirmation - requires the operator to type INSTALL before changing the machine.
Install/register - calls the underlying install and registration flow.
Status - checks the Rust node service and operator metadata.
Healthcheck - runs the privacy protocol healthcheck and prints JSON when requested.

Manual verification commands

After quickstart completes, the operator or AI assistant should verify:

bash

cd /opt/aeronyx
./deploy/node/aeronyx-node.sh status --repo-dir "$PWD"
./deploy/node/aeronyx-node.sh health --repo-dir "$PWD" --json
systemctl is-active aeronyx-server

In nodeboard, open the node detail page and confirm:

the node is online
heartbeat freshness is acceptable
AeroNyx privacy protocol health is ok
capacity decision allows new users or gives a clear blocker
IP pool capacity is visible
max connections and policy max sessions are visible
conntrack, file descriptor, packet drop, pps, and bps telemetry are reported when available
recent events show no open critical closure item

Upgrade path

Use the same entrypoint for upgrade-oriented operations:

bash

cd /opt/aeronyx
git pull --ff-only origin main
./deploy/node/aeronyx-node.sh plan --repo-dir "$PWD"
./deploy/node/aeronyx-node.sh status --repo-dir "$PWD"
./deploy/node/aeronyx-node.sh health --repo-dir "$PWD" --json

Remote restart and remote upgrade from nodeboard should only be enabled with explicit permission, confirmation steps, and audit records. Until that controlled workflow is fully enabled, node operators should run upgrades from their server shell.

AI assistant standard

If the operator uses Codex, OpenClaw, Claude Code, Hermes, or another terminal assistant, the assistant should:

open nodeboard at https://app.aeronyx.network
copy the generated command from Registration Codes
run only deploy/node/aeronyx-node.sh as the primary entrypoint
show the preview plan before installation
ask for operator confirmation before typing INSTALL
run status and healthcheck after changes
summarize nodeboard capacity and incident closure results

The assistant should not invent script names, search random shell files, or bypass the preview plan.