MemChain and Encrypted Storage
MemChain is AeroNyx's node-blind memory layer for private AI memory, encrypted records, local-first recall, encrypted sync, and future agent state coordination.
MemChain and Encrypted Storage
MemChain is AeroNyx's node-blind memory layer: AI memory the storage node cannot read.
It is built for a world where humans, applications, and autonomous agents need long-lived private context. The user may want an AI to remember preferences, projects, decisions, files, tasks, and relationship context. The infrastructure should help preserve and synchronize that memory, but it should not become the party that can read it.
MemChain connects AeroNyx privacy networking, encrypted messaging, encrypted identity backup, encrypted storage, decentralized privacy nodes, and future agent-to-agent protocol services into one private state model.
The product promise
MemChain is designed around four user-visible promises:
| Promise | Meaning |
|---|---|
| Node-blind memory | Storage nodes hold ciphertext, blind indexes, and operational metadata. They do not hold plaintext memories or decryption keys. |
| Local-first recall | The client keeps an encrypted local memory copy so useful recall can happen quickly and offline when local data is available. |
| Bring-your-own brain | Users can choose which AI model helps distill or answer over memory, including local models when available. |
| Encrypted sync | Cross-device recovery and synchronization use owner-controlled keys instead of plaintext server history. |
The important distinction is that MemChain is not a public blockchain and should not be marketed with blockchain imagery. The "chain" is the ordered relationship between encrypted memory records, version vectors, checkpoints, and append-only state.
Why MemChain matters
Private communication is not only about moving packets. Users, applications, and agents also need to preserve state:
- conversation context
- AI memory facts
- encrypted chat history
- encrypted identity backup metadata
- file and object checkpoints
- node service records
- agent workflow memory
- verifiable state transitions
If that state is stored in a centralized database as plaintext, the privacy model is incomplete. MemChain gives AeroNyx a path to store and sync encrypted records while keeping decryption under the owner-controlled key model.
Remember, store, recall
MemChain can be explained as a three-stage pipeline.
| Stage | What happens |
|---|---|
| Remember | The client observes eligible AI conversations, distills durable facts, classifies context, encrypts records locally, signs them, and prepares them for sync. |
| Store | The node stores encrypted bytes, blind indexes, content addresses, version vectors, and replication metadata. It cannot decrypt the memory. |
| Recall | The client searches local encrypted memory first, combines semantic, keyword, time, and structured signals, decrypts authorized hits locally, and injects relevant context into the AI workflow. |
This gives AeroNyx a practical path to private AI memory: memory can be useful without requiring a central service to hold readable user history.
What nodes can and cannot see
Allowed coordinator metadata:
- encrypted object bytes
- content hash or object address
- append sequence
- version vector
- timestamp or logical clock
- owner-controlled authorization proof
- coarse storage pressure
- replication and synchronization health
Forbidden coordinator data:
- decrypted memory records
- chat plaintext
- plaintext filenames
- semantic tags derived from plaintext
- raw user identity mappings
- private keys or recovery secrets
- wallet-level traffic analysis
- browsing history, DNS contents, or packet payloads
The mental model is private version control for ciphertext. Clients and owner-held keys interpret records; infrastructure only stores, orders, and synchronizes encrypted state.
Relationship to encrypted chat
Encrypted P2P and group chat protect message content before relay transport. MemChain can preserve encrypted conversation records as versioned history when the user enables that workflow. The storage layer should not know what the conversation says, who the user's broader social graph is, or which facts were extracted.
Search over message history should therefore be client-side. The relay and storage layers route and preserve ciphertext; they do not provide plaintext search endpoints.
Relationship to identity backup
AeroNyx P2P identities can be exported and imported through encrypted .ayx backup files. MemChain can later record encrypted backup checkpoints or verification state without exposing identity seeds, social graphs, or plaintext message history.
If a user loses the underlying identity or recovery secret, encrypted memory cannot be recovered by AeroNyx. That is a privacy property, not an accident: the node should not have a master key.
Relationship to privacy networking
The privacy network moves encrypted traffic through decentralized privacy nodes. MemChain protects long-lived state. Together they cover two different privacy surfaces:
- private transport for traffic in motion
- node-blind memory for state at rest
The same rule applies to both: infrastructure should expose health, capacity, and verification metadata, not user content.
Relationship to agents
Autonomous agents need a way to connect, exchange encrypted messages, preserve memory, and verify state transitions. MemChain gives agents a private memory substrate while AeroNyx private routing and encrypted relay services give them a communication substrate.
This is why MemChain is part of the AeroNyx protocol story, not a separate note-taking feature. It is the state layer for encrypted coordination.
Benchmark language
AeroNyx internal LongMemEval-S testing in July 2026 is used to evaluate the memory stack. Public claims should stay precise:
- retrieval hit rate can be described as 95-99% in internal LongMemEval-S tests when the evaluation setup is stated
- end-to-end answer quality depends on the selected AI model, because users can bring their own model
- node-side recall latency can be described as 2-5ms in internal tests
- local-first recall is designed for millisecond-level user experience and offline availability when the local encrypted copy has the needed memory
- retrieval itself does not require a new large-model inference call
Avoid stronger claims such as "industry-best accuracy", "zero-knowledge proof", or projected scores presented as achieved results. The stronger story is privacy, speed, cost, and user control.
Operator-safe Nodeboard fields
As decentralized privacy nodes add encrypted storage or MemChain capability, Nodeboard should show only operator-safe health fields:
- module enabled state
- encrypted object count
- storage pressure
- last checkpoint or sync height
- verification status
- replication health
- sync freshness
- error rates and capacity limits
Nodeboard should answer whether the system is healthy, synced, and within capacity limits. It should not become a plaintext data viewer.
Privacy boundary
MemChain's storage nodes are designed to be cryptographically unable to read memory contents because they hold device-encrypted ciphertext and irreversible blind indexes. Encryption, decryption, and meaningful search happen under user-controlled keys.
There is one important user-facing limitation: when a user chooses an external AI service to distill or answer over memory, the relevant plaintext may be sent to that provider by the client. With a local model, that workflow can remain local. AeroNyx should describe this clearly so users understand which part of the system is node-blind and which external services they choose to trust.
Read the introduction: What is AeroNyx?.