AI Memory Should Be
Controlled, Not Replayed.
ExergyNet is an AI Memory Control Plane for persistent, verifiable evidence and bounded execution.
xLMP separates durable memory from temporary model context. It gives persistent state a stable content identity and provides defined paths for provenance, policy, and authority controls without binding application memory to one model provider or accelerator.
The current benchmark program spans H200 memory efficiency, deterministic retrieval, VMN resilience, adaptive routing, and authority separation. Every public number is bounded to its tested envelope.
Persistent, root-addressed machine memory with bounded evidence delivery. VMN is the open-source local node.
Reasoning, orchestration, and execution coordination over bounded evidence and authority constraints.
Transport for persistent memory identity, provenance, integrity, and freshness. Memory portability does not grant execution authority.
Receipts for computation, authenticated external data, and physical-world observations.
Complementary rails for coordination, receipts, and economic finality.
A memory and execution fabric for autonomous systems.
ExergyNet is not another model wrapper. It is infrastructure for preserving state, delivering complete evidence, coordinating intelligence, and producing independently checkable operational records.
Persistent Machine Memory
Exergy Vault stores state as durable, integrity-rooted objects. xLMP retrieves the smallest complete set of authoritative evidence required for an operation.
Controlled Intelligence
Vanguard consumes bounded evidence from the memory control plane, coordinates reasoning and execution, and operates under explicit authority constraints.
Verifiable Operations
Computation, external data, hardware observations, and settlement produce distinct receipts with explicit trust boundaries.
xLMP separates three memory properties.
These properties are intentionally separate. A content hash is not provenance. Provenance is not authority. A model recommendation is not permission to act.
Integrity
A SHA-256 content root establishes the identity of committed content and makes later modification detectable.
Provenance
Where a signed provenance record is present, the source and creation event can be checked against the signer's public key.
Authority
Where the LNES-22 authority layer is enabled, policy and signed authorization determine whether retrieved state may result in a consequential action.
One architecture. Clear responsibilities.
Each component addresses a different part of the autonomous-system lifecycle. Together they form a persistent operating layer beneath models and applications.
Exergy Vault
Persistent, content-addressed storage for AI state, evidence, provenance, and long-lived operational memory.
SEI-Vanguard
The native control plane for evidence selection, model execution, policy enforcement, and state transition.
Vanguard Memory Node
Open-source local node for xLMP — the AI Memory Control Plane. Deterministic, content-addressed memory via MCP. No cloud required. Deploy in 60 seconds.
Omega Carrier
A transport architecture for moving persistent memory between nodes while preserving identity, provenance, integrity, and freshness.
AERIS
Authenticated external-data ingestion for systems that must use web and enterprise data without abandoning provenance.
Edge Witness
Hardware-backed capture and signing for device observations, physical presence, and field-operational evidence.
Proof and Settlement
Computation receipts, proof aggregation, and multi-chain anchoring connect completed work to durable records and economic finality.
Persistent knowledge. Bounded context. Verifiable action.
The objective is not to send the largest possible prompt. It is to preserve complete state outside active context and deliver only the authoritative evidence required for the current operation.
Preserve state
Source material is normalized into durable objects with provenance and integrity commitments.
Locate evidence
xLMP resolves the complete object or record set required for the current question or task.
Execute with control
Vanguard selects the model, tool, policy, and execution path without binding the system to one provider.
Issue a receipt
The operation returns evidence, integrity metadata, and the appropriate computational or hardware-backed receipt.
Update durable state
The result is written back into persistent memory and, where required, anchored or settled across supported rails.
Different claims require different proofs.
ExergyNet does not collapse computation, hardware identity, physical observation, and settlement into one vague idea of truth. Each layer exposes a specific guarantee and a specific boundary.
| Layer | What it establishes | What it does not establish |
|---|---|---|
| xLMP root | The identity, integrity, and provenance of the addressed memory object. | That a model will interpret the object correctly. |
| ZK receipt | That a defined computation executed according to the committed program and inputs. | That external inputs were semantically correct. |
| Hardware signature | That an authorized device or enclave signed the observation or execution record. | That every sensor or external environment was truthful. |
| Ledger anchor | Ordering, timestamping, and durable settlement finality. | The semantic correctness of off-chain claims. |
| Vanguard audit | The evidence, policy, and execution path used for an operation. | Absolute model infallibility. |
Architectural response to the x402 vulnerability matrix.
Security research accepted for USENIX Security 2026 identifies facilitator-mediated failure modes in x402 deployments. ExergyNet’s architectural answer: capital locked before compute, proof verified before settlement, asset authority constrained by contract.
Architecture supported by benchmark evidence.
The public benchmark program focuses on measured behavior, explicit limitations, and reproducible results. The numbers below apply to the tested workloads and conditions.
Infrastructure for systems that cannot afford to forget what happened.
Build persistent agents
Connect memory, models, external data, tools, and receipts through APIs, SDKs, and MCP-compatible interfaces.
Operate with provenance
Preserve authoritative state, control evidence access, and produce audit-ready records for high-value workflows.
Run sovereign infrastructure
Contribute execution, storage, transport, or witness capacity to the network under explicit protocol roles.
Built to be discovered and used by software.
ExergyNet exposes public integration surfaces without exposing the implementation mechanisms that create the system's advantage.
MCP
Agent Tooling
Connect compatible agents to ExergyNet memory, execution, and verification capabilities. For local stdio MCP memory, deploy VMN.
SDK
Application Integration
Use documented APIs and SDKs to create jobs, resolve memory, monitor execution, and verify receipts.
Discovery
Machine-Readable Manifests
Protocol coordinates, capabilities, and integration surfaces are available through canonical discovery files.
Clear interfaces. Stable identifiers.
The public site exposes the identifiers and interfaces needed to evaluate and integrate with the network. Internal topology, credentials, and security-sensitive implementation details are not published.
Network Details
- Solana Program
7BCPpUMBxQMPomsgTaJsQdLEfycNwPWqkQD1Cea4CcCL - EVM Contract
LNES04Membrane.sol (Base Mainnet) - Settlement RailsSolana / Base L2
- MCP Gateway
https://exergynet.org/mcp - npm Package
@elizaos/plugin-exergynet
Build systems that remember what matters.
Explore the architecture, evaluate the interfaces, or begin integrating ExergyNet into an autonomous workflow.