AeroNyx Privacy Coordination Protocol
AeroNyx does not publish what users do. It lets independent nodes verify signed infrastructure state, recover public evidence, and prove encrypted relay work without exposing identities, messages, memory, or complete routes.
Three-plane architecture
Separating encrypted data from coordination evidence gives independent operators enough information to participate and audit protocol behavior without turning users into public records.
Carries encrypted traffic, messages, media, and memory payloads through blind protocol services.
Distributes signed node descriptors, capabilities, sequence state, and bounded route candidates.
Orders signed commitments and mirrors checkpoint, witness, recovery, and aggregate relay evidence.
Public evidence boundary
AeroNyx Verifiable Coordination Ledger is a producer-scoped, append-only evidence system. It exists to make protocol state recoverable and independently checkable, not to create a public history of user behavior.
Optional encrypted payload storage is a separate client-controlled service. Payload blobs are not coordination-ledger records and remain unreadable to storage nodes.
Private relay evidence
Each participant receives only the minimum information needed for its role. Evidence is bounded so no single node receives the complete story.
The sender encrypts and signs the payload before it enters the network.
The network receives an opaque envelope, not message meaning.
Fresh signed descriptors and reachability evidence form a bounded candidate set.
A relay learns its next action, not the complete route.
Middle nodes forward ciphertext and produce replay-resistant, route-bounded relay evidence.
Proof covers protocol work, never plaintext content.
Checkpoint witnesses and mirrors preserve public evidence if a producer becomes unavailable.
Independent recovery does not require publishing user activity.
A different kind of ledger
The word ledger describes tamper-evident ordering and recovery. It does not imply a token, smart-contract platform, global transaction mempool, or universal finality.
Protocol delivery
The public surface separates verified runtime capabilities from active research so operators and developers can reason about the network without roadmap theater.
Available now
Nodes publish signed, sequence-protected descriptors and discover eligible peers without a central approval list.
Available now
Independent nodes can verify, mirror, and recover producer-scoped public commitments.
Available now
Blind relay paths can produce accepted or rejected evidence and observable delivery counters without exposing payloads.
Building next
More operators, network diversity, client-selected decentralized delivery, and stronger anti-correlation policy remain the next trust boundary.
Straight answers
Claim boundaries are part of the architecture. They should remain as visible as the features.
No. AeroNyx uses signed, hash-linked, append-only coordination evidence for privacy infrastructure. It is not presented as a token ledger, smart-contract platform, or public transaction network.
No. Message and memory contents are excluded from the evidence ledger. Optional encrypted payload storage is separate, client-controlled, and unreadable to storage nodes.
No. The current model provides producer-scoped signed ordering, independent witnesses, mirrors, and recovery evidence. Global consensus and universal transaction finality are not current claims.
Protocol payloads are end-to-end encrypted before relay or storage. Nodes process bounded metadata required for delivery, but cannot decrypt the payload. Traffic-correlation risk remains part of the threat model and requires continued route and operator diversity work.
Open protocol, bounded knowledge
Anyone can run compatible nodes and verify public protocol evidence. The durable product promise is not that operators are trusted; it is that the protocol limits what any operator can know.