What is AeroNyx?
AeroNyx is the encrypted coordination layer for humans, apps, and autonomous agents: private routing, encrypted messaging, node-blind memory, decentralized privacy nodes, and Nodeboard operations.
What is AeroNyx?
AeroNyx is the encrypted coordination layer for autonomous agents.
AeroNyx lets humans, apps, and AI agents route traffic, exchange encrypted messages, preserve private memory, and coordinate work through a blind, open protocol. The protocol is designed around one simple idea: infrastructure should move and verify ciphertext without becoming the place that can read, profile, or control the user.
The product ecosystem is built on top of that protocol. The AeroNyx app gives users a daily privacy surface. Decentralized privacy nodes provide the network infrastructure. Nodeboard gives operators a serious control plane. MemChain gives users and agents private memory that storage nodes cannot read.
Protocol, products, and operators
| Layer | What it means |
|---|---|
| AeroNyx Protocol | The open ruleset for private routing, encrypted messaging, encrypted identity, node-blind memory, encrypted storage, and agent coordination. |
| AeroNyx App | The user-facing product for encrypted communication, privacy network access, identity backup, AI workflows, and daily privacy controls. |
| Decentralized privacy nodes | Independently operated infrastructure that forwards encrypted traffic, advertises signed capabilities, participates in peer discovery, and reports aggregate health. |
| Nodeboard | The operator product at app.aeronyx.network for registration, capacity, health, discovery, relay readiness, and operational workflows. |
| MemChain | The node-blind memory layer for encrypted records, private AI memory, local-first recall, and future agent state synchronization. |
This separation matters. A product can change its interface, pricing, or distribution. A protocol should define durable behavior: how nodes are discovered, how ciphertext is routed, which metadata is allowed, and which privacy boundaries cannot be crossed.
Why AeroNyx exists
The internet is moving from human-only applications to a world where people, applications, and autonomous agents all need to communicate, negotiate, store context, and access services. Most platforms centralize identity, retain 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 communication protect social context before relay transport
- multi-identity social keys separate chat identity from wallet identity
- encrypted
.ayxbackup helps users recover P2P identities without exposing plaintext seeds - encrypted storage keeps private records under user-controlled keys
- MemChain preserves encrypted state and AI memory without giving nodes plaintext access
- decentralized privacy nodes let independent operators help run the network
- Nodeboard turns node operation into an observable, auditable product workflow
- agent-to-agent encrypted services give autonomous systems a private coordination substrate
Core protocol surfaces
| Surface | Role |
|---|---|
| Private routing | Moves user and agent traffic through independent nodes while keeping payloads outside operator visibility. |
| Encrypted messaging | Delivers P2P, group, reaction, read-receipt, and media events as encrypted application payloads. |
| Node discovery | Lets nodes publish signed descriptors, peer summaries, capabilities, and freshness data. |
| Relay readiness | Uses candidate pools, reachability probes, and proof metadata to prepare multi-hop relay paths. |
| MemChain | Stores and synchronizes encrypted records, version vectors, and private memory checkpoints. |
| Operator observability | Exposes aggregate capacity, health, packet counts, traffic bytes, discovery state, and relay status without exposing user content. |
The Blind Infrastructure Invariant
AeroNyx privacy depends on one non-negotiable invariant: relay nodes, storage nodes, and MemChain coordinators must be blind.
A node may forward encrypted blobs, maintain a signed peer store, expose capacity, report aggregate health, and publish capability descriptors. It must not read message plaintext, packet payloads, DNS contents, browsing history, destinations, private files, MemChain plaintext, wallet-level traffic, or private identity seeds.
MemChain follows the same rule. A coordinator can order encrypted records, timestamp append-only events, and help clients synchronize versioned encrypted state. It should behave like ciphertext object storage plus version vectors, not a plaintext application database.
This is not a branding preference. It is the line between a privacy protocol and a centralized service with extra nodes attached.
Permissionless node participation
AeroNyx is designed so independent operators can run decentralized privacy nodes. A node can advertise capabilities such as privacy routing, chat relay readiness, onion-middle readiness, encrypted storage, or MemChain support through signed descriptors. Other nodes verify descriptors and maintain a peer store before selecting candidates for future relay paths.
Permissionless growth is powerful, but it also requires honest documentation. More nodes improve reach and resilience, while routing safety depends on reachability evidence, capability verification, operator diversity, anti-abuse controls, and future reputation or incentive mechanisms. AeroNyx documents these tradeoffs because privacy infrastructure must be understandable before it can be trusted.
What public statistics mean
Public AeroNyx dashboards may show aggregate operational information such as encrypted traffic bytes, encrypted packets, reporting nodes, node health, discovery freshness, relay proof counts, capacity, and service status. These metrics are useful because they show whether the protocol is alive and whether infrastructure is participating.
They are intentionally not user surveillance. Public stats and Nodeboard views 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, private memory plaintext, or social graph edges.
What AeroNyx is not
AeroNyx is not a promise that every external service involved in a user workflow is blind. If a user chooses an external AI model or third-party service, that provider may receive the data the user sends to it. AeroNyx's protocol boundary is about what AeroNyx nodes and coordinators can access: ciphertext and operational metadata, not user content.
AeroNyx is also not a closed application that only one company can operate. The long-term direction is an open protocol with open implementations, clear invariants, public documentation, and independently operated infrastructure.