AeroNyx FAQ and Community Guide

This FAQ provides concise, citation-ready answers about the AeroNyx open privacy protocol, official products, current deployment boundaries, decentralized privacy nodes, encrypted communication, MemChain, Nodeboard, and public trust policies. It describes what exists today and separates it from configurable or future protocol paths.

What is AeroNyx?

AeroNyx is an open privacy protocol and product ecosystem for private routing, encrypted messaging, client-sealed memory, encrypted storage, decentralized node operation, and coordination between people, apps, and autonomous agents. The protocol is the shared technical layer; an app, website, API, node, or operator console is one implementation or interface around it.

Is AeroNyx a protocol, a company, or an app?

AeroNyx has distinct trust domains: AeroNyx-operated websites, apps, APIs, relay/bootstrap services, Nodeboard, docs, and support; compatible nodes run by AeroNyx or independent operators; user-controlled keys and encrypted content; and external providers such as AI models, RPCs, payment processors, app stores, hosting providers, and destination services. The company operates official products, but compatible protocol software can be operated by others.

Is AeroNyx messaging fully decentralized today?

No. The official app currently uses an AeroNyx-operated relay by default because it provides predictable delivery and recovery. End-to-end encryption keeps supported message content unreadable to that relay. Compatible independent relay and multi-hop paths are optional, capability- and configuration-dependent, and still evolving. Users should not infer that every message already avoids all AeroNyx-operated coordination services.

Can anyone run an AeroNyx node?

Yes. A person or organization may run compatible AeroNyx privacy-node software, subject to applicable law, hosting terms, technical compatibility, security, and its own infrastructure responsibilities. Permissionless participation does not mean immediate routing eligibility: official discovery or app surfaces may require fresh health, reachable endpoints, compatible versions, abuse controls, capacity, signed descriptors, or quality evidence.

Are all nodes operated or approved by AeroNyx?

No. Compatible nodes may be operated by AeroNyx or independent parties. Running compatible software does not mean AeroNyx has certified, endorsed, supervised, or accepted responsibility for that node. Independent operators remain responsible for security, uptime, lawful operation, hosting, local disclosures, taxes, licenses, abuse handling, and any logging or retention obligations that apply to them.

What can AeroNyx see and decrypt?

AeroNyx-operated services may process limited operational data such as account identifiers, support messages, device diagnostics, node metadata, aggregate protocol statistics, command audit, payments, and abuse/security signals. For supported E2E and strict client-sealed paths, services are designed not to hold the content key or decrypt message, attachment, or MemChain plaintext. This promise does not cover plaintext deliberately sent to support or an external AI provider, readable legacy/cognitive modes, compromised devices, or metadata needed to operate a networked service.

Does AeroNyx guarantee anonymity or replace HTTPS?

No technology guarantees absolute anonymity, confidentiality, availability, censorship resistance, legality, or protection from every endpoint, device, metadata, traffic-analysis, operator, or third-party risk. AeroNyx reduces required trust and protects supported encrypted content, but it does not replace secure endpoint behavior. On the wider internet, use application encryption such as HTTPS; a routing layer alone does not make an insecure destination protocol confidential.

What is AeroNyx Privacy Network?

AeroNyx Privacy Network is the private-routing layer of the protocol. Compatible nodes can carry encrypted traffic and report aggregate health, capacity, bytes, packets, and route-readiness without reporting user plaintext. A node's configured capability is not the same as observed reachability or proven relay delivery. Public statistics are aggregate operational evidence, not a history of users, destinations, DNS, or browsing.

What is Nodeboard?

Nodeboard is the authenticated operations console for operators to register and manage their associated nodes. It presents fleet attention, capacity, policy, discovery, encrypted relay evidence, restart readiness, command lifecycle, recovery, and configuration-gated storage/commitment status. It is not a public traffic explorer and must not expose packet/message plaintext, routes, client public-IP activity, private memory, keys, voucher secrets, or wallet-level traffic.

What is MemChain?

MemChain is AeroNyx's local-first encrypted memory layer. The device keeps an encrypted store, performs hybrid recall, and may upload an owner-signed client-sealed copy to a configured node for sync/recovery. The strict node-blind promise applies to records encrypted before remember_sealed; standard cognitive or external-model paths may process readable text under separate consent and trust. Nodes can still see bounded metadata, so node-blind content does not mean metadata anonymity.

Is the signed commitment ledger a blockchain?

It is a specialized append-only evidence layer for opaque record commitments, follower recovery, signed anchors, checkpoint certificates, and pinned witnesses. It helps detect rollback, fork, divergence, or equivocation without putting message or memory plaintext on-chain. It is not a general-purpose public blockchain, smart-contract platform, token ledger, permissionless consensus system, or guarantee of global finality, and its advanced modes are configuration-controlled.

Why separate wallet and messaging identities?

Wallet identity supports assets, membership, subscription, node ownership, and account consent. Messaging or P2P identity supports contacts, encrypted chat, sharing, local namespaces, and protocol discovery. Separating them reduces unnecessary linkage between every social interaction and a wallet address. Losing user-held identity or decryption material may make encrypted data unrecoverable because AeroNyx does not keep a master recovery key.

Who is responsible for user content?

Users are responsible for content, messages, files, traffic, commands, prompts, memories, and other material they create, send, store, publish, route, or make available. The fact that AeroNyx cannot decrypt supported user-key-protected content is not permission to misuse the protocol or violate law, rights, hosting rules, or service terms. Node operators are separately responsible for their own infrastructure and jurisdictional duties.

How are legal requests and retention handled?

AeroNyx may provide records it actually holds from AeroNyx-operated services when required by valid applicable process and subject to retention rules. It cannot provide data it did not collect or control, recover user-held keys, or create plaintext from ciphertext it cannot decrypt. Retention varies by record type: aggregate statistics, diagnostics, support, command audit, payment, legal-request, security, and backup records can have different periods. Retention does not change the cryptographic no-decrypt boundary.

How should security, cookies, and advice be understood?

Report vulnerabilities through the Security and Vulnerability Disclosure Policy and avoid harming users, disrupting service, invading privacy, or testing independent systems without authorization. Official services may use cookies, local storage, analytics, preferences, and security signals for operation and improvement; these do not decrypt user-key-protected content. Docs, AI output, dashboards, statistics, and examples are informational, not legal, financial, investment, tax, medical, or other professional advice.

Where are official policies and support?

Start with the AeroNyx Trust Center, including the Privacy Policy, Terms of Service, Node Operator Policy, Data Retention Policy, Law Enforcement and Transparency Policy, Cookie Policy, and Security Disclosure Policy. Use only official sites, apps, docs, and announced community channels. Support will never ask for a seed phrase, private key, wallet secret, or user-held decryption key. General contact: hi@aeronyx.network.