AeroNyx App and Protocol Architecture

AeroNyx has two layers: the open privacy protocol and the products built on top of it.

The protocol layer is the durable foundation for private routing, encrypted identity, encrypted P2P and group communication, encrypted backup, Memory Chain records, Rust privacy nodes, and agent-to-agent encrypted services. The product layer includes the AeroNyx cross-platform app, nodeboard, Rust node implementation, and operator/user interfaces.

Protocol and product separation

Layer	Examples	Purpose
Protocol	privacy routing rules, encrypted messaging behavior, identity model, Memory Chain direction, node service interfaces	Defines how the network works and how independent implementations can interoperate.
User products	AeroNyx app on iOS, Android, macOS, Windows, Linux	Gives people encrypted chat, wallet, private routing, backup, AI, and daily privacy workflows.
Operator products	nodeboard, Rust privacy node installer, node monitoring	Helps node operators run infrastructure safely and commercially.
Future agent products	agent-to-agent encrypted services, private state exchange, settlement integrations	Lets autonomous agents communicate and use services through the privacy protocol.

Product layers

Layer	Role
Privacy network	Private routing through Rust privacy nodes and commercial node capacity.
Encrypted P2P chat	1:1 end-to-end encrypted messaging using P2P social identities.
Encrypted group chat	Group communication with encrypted group keys and signed membership operations.
Multi-identity social layer	Users can maintain multiple P2P identities, switch between them, and isolate local message storage.
Wallet layer	multi-chain wallet functions with high-trust consent surfaces.
Encrypted backup	P2P identity export/import through encrypted `.ayx` backup files.
Memory Chain direction	Encrypted, versioned private state for conversation memory, storage checkpoints, nodes, and future agents.
Agent protocol services	Private connectivity, encrypted messaging, and verifiable state exchange for autonomous agents.

Wallet identity vs P2P identity

AeroNyx separates financial identity from social identity.

Identity	Purpose
Wallet identity	Financial root for wallet assets, membership, subscription, node ownership, and account-level entitlements.
P2P identity	Social mask layer for encrypted contacts, chat identity, QR/deep-link contact sharing, local message namespace, and future discovery.

This separation is intentional. Deleting a wallet should not automatically delete encrypted chat identities. A user's financial root and social root have different privacy expectations and recovery flows.

P2P encrypted chat

AeroNyx P2P chat uses application-layer end-to-end encryption. Public docs should describe the model at a product level:

P2P identity keys represent the chat identity.
Messages are encrypted before relay transport.
Relay infrastructure should not see plaintext message content.
Contact identity should be verified by public-key fingerprint, QR code, or deep link.
Local message storage is namespaced by active P2P identity.

Current app architecture supports two transport paths:

Transport	Role
RelayWS	Standard encrypted relay path over TLS WebSocket, with HTTP fallback when needed.
Privacy network relay	Optional/fallback path through the private network when available.

P2P chat should not be described as requiring a privacy network connection. The privacy network can strengthen or route traffic, but encrypted P2P messaging must remain understandable as its own product layer.

Encrypted identity backup

P2P identity backup uses an .ayx encrypted export file. The backup design is:

random salt
password-derived key
AES-256-GCM encrypted seed payload
no plaintext identity seed in the backup file
user-controlled import/export flow

This makes backup a high-trust recovery surface. Docs and UI should avoid raw cryptography exceptions and explain recovery in stable product language.

Group chat and calls

AeroNyx group chat extends the encrypted social layer beyond 1:1 conversations. Group surfaces should emphasize encrypted membership state, group keys, safe leave/dissolve operations, and localized trust copy.

Voice and video calls are part of the same social runtime direction. They should remain consistent with the encrypted identity model and avoid exposing low-level transport errors to users.

Agent protocol direction

Autonomous agents need private connectivity, encrypted messaging, and verifiable state exchange. AeroNyx can provide:

private network access
encrypted agent-to-agent communication
encrypted storage for private state
Memory Chain records for versioned memory
wallet-aware consent and payment flows
independently operated service infrastructure

This is why AeroNyx should be described as an open privacy protocol and product ecosystem, not only as a network tunnel or a single app feature.