What is AeroNyx Protocol?

AeroNyx is an open privacy protocol and product ecosystem.

The protocol layer is the long-lived foundation: private routing, encrypted P2P and group communication, multi-identity social keys, encrypted identity backup, Memory Chain records, Rust privacy nodes, and agent-to-agent encrypted services. Products such as the AeroNyx app, nodeboard, and Rust node implementation are interfaces and tools built on top of that protocol.

This distinction matters. A product can change UI, pricing, or distribution. A protocol should define open rules, interoperable implementations, and a network that does not depend on one interface staying online.

Protocol vs products

Layer	What it means
AeroNyx Protocol	The open privacy ruleset and network layer for private routing, encrypted identity, encrypted messaging, encrypted backup, Memory Chain records, and node operation.
AeroNyx App	Cross-platform user product for encrypted chat, wallet, private routing, backup, AI, and daily privacy workflows.
Rust privacy node	Open node implementation that participates in the privacy network and reports aggregate health/capacity.
nodeboard	Operator product for registering nodes, monitoring services, managing access, and preparing commercial operation.

The AeroNyx story

The internet is moving from human-only applications to a world where people, applications, and agents all need to communicate, negotiate, store state, and access services. Traditional platforms centralize identity, store raw history, monetize metadata, and can remove access through a single control point.

AeroNyx takes a protocol-first route:

private routing gives users and agents a privacy-preserving network path
encrypted P2P and group chat protect social communication
multi-identity P2P keys separate social identity from wallet identity
encrypted .ayx backup helps users recover P2P identities without exposing plaintext seeds
encrypted storage keeps private records under user-controlled keys
Memory Chain creates a versioned record layer for encrypted state and conversation memory
Rust privacy nodes let independent operators participate in the network
nodeboard gives operators a commercial-grade control and observability surface
agent-to-agent encrypted protocol services help global agents connect without leaking private context

Core layers

Layer	Role
Privacy protocol	Defines the open network behavior, privacy boundaries, and service interfaces.
Private routing	Routes private network sessions through independent Rust privacy nodes.
Encrypted P2P chat	Protects 1:1 social communication with application-layer encryption.
Encrypted group chat	Extends the social layer to encrypted group conversations and group state.
Multi-identity social layer	Lets users switch social identities and isolate local message storage.
Encrypted backup	Exports/imports P2P identity material through password-protected `.ayx` files.
Encrypted storage	Stores private records as encrypted objects controlled by user keys.
Memory Chain	Preserves encrypted state history and versioned memory records for users, chats, nodes, and future agents.
Rust privacy nodes	Operate the network data plane and report aggregate health/capacity metrics.
nodeboard	Lets operators register nodes, monitor services, manage access, and prepare commercial operation.
Agent protocol services	Provide a natural encrypted connection layer for agent-to-agent workflows.

Transport model

AeroNyx encrypted chat is not only a network-tunnel feature. The app supports a standard encrypted RelayWS path and can use the privacy network relay path when available. In both cases, application-layer encryption protects message content before relay transport.

This distinction matters: the protocol includes private routing, but encrypted social identity and messaging are independent product layers on top of the same privacy foundation.

Open source direction

AeroNyx should be documented as an open protocol with open implementations and clear privacy boundaries. Public docs should explain which parts are protocol behavior, which parts are product UX, and which parts are operator tooling.

Privacy boundary

AeroNyx public statistics and operator dashboards should expose aggregate operational data only. They should not expose packet payloads, DNS contents, user destinations, domains, URLs, browsing history, voucher secrets, wallet-level traffic, raw client public IP activity, decryptable message history, encrypted backup plaintext, or private identity seeds.