Install and Register a Rust Privacy Node

This guide explains how an operator installs and registers a Rust privacy node for AeroNyx Protocol.

The Rust node is the operator-run infrastructure process. nodeboard is the operator console. The backend coordinates registration, heartbeats, aggregate metrics, access policy, and public network statistics.

Recommended path: nodeboard quick install

Open nodeboard at https://app.aeronyx.network, sign in, and choose Add Node.

nodeboard generates a short-lived registration code and shows two copyable commands:

Command	Purpose
Preview command	Runs `install.sh --quick --print-plan` without root access, package installation, host changes, registration, or service start. Use it to verify the resolved install plan first.
Install command	Runs `sudo ... install.sh --quick` with the registration code and starts the production install flow.

The registration code expires quickly. If it expires before the node is installed, generate a new code in nodeboard.

Before you start

You need:

a Linux server with systemd
root or sudo access
a public IPv4 address
outbound access to AeroNyx backend APIs
UDP service reachability for the current privacy network data plane
curl available on the server

Preview the install plan

Copy the Preview command from nodeboard. It follows this shape:

bash

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

The preview command is read-only. It should not require root and should not mutate the host. It prints whether a registration code is present without revealing the code value.

Run the quick install

After the preview looks correct, copy the Install command from nodeboard. It follows this shape:

bash

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

--quick is the production first-install path. It should still run safeguards instead of bypassing them:

detect the Linux/systemd environment
run host preflight checks
print capacity-plan warnings
install required packages when needed
prepare or update the AeroNyx repository
write safe default configuration without overwriting node identity files
configure forwarding/NAT when enabled
build or install the Rust server binary
verify and install the systemd service
register the node with the backend
start aeronyx-server
begin heartbeat and aggregate metric reporting

Validate

Check service status:

bash

systemctl status aeronyx-server --no-pager

Check recent logs:

bash

journalctl -u aeronyx-server -n 100 --no-pager

Then open https://app.aeronyx.network and confirm:

the node is registered
heartbeat is fresh
service health is visible
capacity information is present
aggregate traffic and encrypted packet counters are updating when sessions are active

Existing checkout path

Advanced operators with an existing checkout can still run the installer from the repository:

bash

sudo AERONYX_REGISTRATION_CODE='<NODEBOARD_CODE>' ./deploy/node/install.sh --quick

For a custom checkout path without build or network changes:

bash

sudo ./deploy/node/install.sh --repo-dir /root/open/AeroNyx --no-build --no-network

What the node reports

The Rust privacy node should report operational metadata needed for commercial reliability:

heartbeat freshness
region and service capability metadata
IP pool capacity, used IPs, and remaining IPs
max_connections
policy max_sessions
conntrack and file descriptor pressure
packet drops
pps and bps
aggregate encrypted traffic counters
aggregate encrypted packet forwarding counters
Memory Chain or encrypted storage capability status when those modules are enabled

The node should not report packet payloads, browsing history, DNS contents, user destinations, domains, URLs, decryptable chat history, encrypted backup plaintext, identity seeds, or private storage plaintext.

Current maturity

The quick-install flow is suitable for technical operators and early commercial node onboarding. The next maturity step is installer progress reporting back to nodeboard so operators can see previewed, install started, preflight failed, registered, and service started states directly in the dashboard.