Enigma

Official $ENIGMA Token (Solana Mainnet):
Contract Address (CA): EknDj8VZUHL6FhV9pSk3m6xP2U2sDzwjRDVstKeQpump
Solscan Explorer • Pump.fun • Official Website • Official X (@Engimamemory)

Enigma Memory is a local-first AI Memory Passport. It gives you one canonical local memory vault, receipt-backed proof for Enigma-controlled events, and MCP connections into assistants such as Claude Desktop, Cursor, Kimi Code, and generic MCP clients.

Start with the Memory Drive loop below — one install, one connect, then health and status verification. You do not need to understand relay, gateway, mesh, browser, desktop, hosted infrastructure, or the proof network before trying Enigma locally.

Hosted cloud and BYOC operation are waitlist/operator-deploy only; they require real deployment credentials, domains, TLS, durable storage, KMS/secrets, monitoring, backups, and operator acceptance. The relay and gateway binaries included in the package are local bootstrap probes, not a live hosted service.

Enigma does not claim that a closed provider deleted internal data, that model weights forgot, or that provider-native memory disappeared. It proves facts about Enigma-controlled vault state, receipts, checkpoints, and declared boundary operations.

Install once, use everywhere

Prerequisites:

• Node.js >=24
• No database, package registry account, provider credential, cloud credential, hosted Enigma account, or external account for the local setup path
• Git only when you choose the advanced source-checkout path

Use Enigma as your private Memory Drive for AI: install once, connect the AI clients you already have, then inspect drive health and passport status before remembering, retrieving, packaging, and verifying context.

npm install -g enigma-memory
enigma setup --bundle "$HOME/.enigma/bundle.json" --client auto --connect-installed --overwrite
echo "Keep all Q3 planning notes in the project-context tag." > memory.txt
enigma remember --bundle "$HOME/.enigma/bundle.json" --text-file memory.txt
enigma search --bundle "$HOME/.enigma/bundle.json" --query "Q3 planning"
enigma context --bundle "$HOME/.enigma/bundle.json" --query "Q3 planning" --out "$HOME/.enigma/context-pack.json"
enigma verify --export "$HOME/.enigma/export.json"

Windows CMD:

npm install -g enigma-memory
enigma setup --bundle "%USERPROFILE%\.enigma\bundle.json" --client auto --connect-installed --overwrite
echo Keep all Q3 planning notes in the project-context tag.> memory.txt
enigma remember --bundle "%USERPROFILE%\.enigma\bundle.json" --text-file memory.txt
enigma search --bundle "%USERPROFILE%\.enigma\bundle.json" --query "Q3 planning"
enigma context --bundle "%USERPROFILE%\.enigma\bundle.json" --query "Q3 planning" --out "%USERPROFILE%\.enigma\context-pack.json"
enigma verify --export "%USERPROFILE%\.enigma\export.json"

enigma setup is the credential-free first run: it creates the local .enigma workspace, bundle, proof artifacts, and a demo memory, then connects every installed/config-present client it detects (Claude Desktop, Cursor, Kimi Code, VS Code/Cline, Roo, OpenCode, generic MCP). enigma start aliases the quickstart flow. Setup skips clients that are not installed and never creates configs from scratch; preview with --dry-run first if you want to see which clients will be written.

Keyring Security Modes & At-Rest Confidentiality

• Developer Default Mode (local_secret): Running enigma setup or enigma quickstart without credential parameters initializes an unencrypted developer keyring (unencrypted: true). This mode provides no at-rest confidentiality against local file access and is intended solely for zero-config local evaluation.
• Sovereign Encrypted Mode (local_secret_encrypted): Set ENIGMA_PASSPHRASE in your environment or pass --passphrase-file <path> to encrypt vault keys at rest using AES-256-GCM AEAD with scrypt key derivation and GCM AAD metadata authentication.

Encrypted + Solana-connected local flow:

npm install -g enigma-memory
printf "choose-a-long-local-passphrase\n" > ~/.enigma-passphrase
enigma quickstart --bundle "$HOME/.enigma/bundle.json" --passphrase-file ~/.enigma-passphrase --overwrite
enigma remember --bundle "$HOME/.enigma/bundle.json" --passphrase-file ~/.enigma-passphrase --text-file memory.txt
enigma-terminal --exec "solana status --cluster devnet"
enigma chain anchor-bundle --bundle "$HOME/.enigma/bundle.json" --cluster devnet --out "$HOME/.enigma/anchor-batch.json"
enigma chain submit-solana --file "$HOME/.enigma/anchor-batch.json" --cluster devnet
# Actual on-chain write, when you provide a funded Solana CLI keypair:
# enigma chain submit-solana --file "$HOME/.enigma/anchor-batch.json" --cluster devnet --execute --keypair ~/.config/solana/id.json

chain anchor-bundle anchors only public commitment roots (active_set_root, receipt_log_root) and public refs. It never places raw memory, plaintext prompts, vault keys, passphrases, private keys, or encrypted bundle bodies on-chain. chain submit-solana defaults to dry-run; --execute writes a compact SPL Memo proof reference to Solana using your explicitly supplied funded keypair.

The cypherpunk research basis is recorded in docs/research/sovereign-cypherpunk-memory.md: Shamir 1979 threshold sharing, Merkle 1979 accumulators, Rubberhose/TrueCrypt plausible-deniability storage patterns, OTR/Signal ratchets, and Unix/Windows memory-locking constraints. The document is explicitly exploratory; production Enigma only ships the reviewed local vault primitives and public-safe Solana commitment anchoring described above.

Run setup or quickstart before treating enigma doctor as a fully green install check. Doctor checks both the local package/runtime environment and existing connector configs; on a fresh install it can be red when an MCP client config already names an Enigma bundle that has not been initialized yet, or when clients still point somewhere else. That is expected first-run state, not evidence that the npm package failed to install. The no-friction path is enigma quickstart --bundle ./.enigma/bundle.json --overwrite or enigma setup --bundle ./.enigma/bundle.json --overwrite, then enigma doctor --bundle ./.enigma/bundle.json. If no clients are installed, setup still succeeds and the local CLI path works; use the copy-paste MCP snippets below to connect a client later.

For the no-global-install path, run npx --yes --package enigma-memory enigma quickstart --bundle ./.enigma/bundle.json --overwrite before npx --yes --package enigma-memory enigma doctor --bundle ./.enigma/bundle.json; running npx doctor first can surface the same expected red generic-MCP missing-bundle state.

Enigma Proof Network

Enigma Proof Network is the public proof layer for AI memory: local tools can package privacy-preserving roots, refs, counts, signatures, scoped capability grants, revocations, and benchmark attestations without exposing raw memory, prompts, transcripts, completions, embeddings, tenant names, private keys, provider responses, or provider credentials.

The enigma chain anchor|grant|revoke|attest|verify commands are local planning and verification commands. They emit public-safe JSON with transaction_submitted:false and raw_memory_on_chain:false; they do not submit Solana transactions, deploy hosted SaaS, create accounts, or call external providers.

Start with the category narrative in docs/market-category-narrative.md, then read the technical overview in docs/proof-network.md, use its Solana role section for the Solana-ready anchoring boundary, and read docs/proof-network-faq.md for claim boundaries.

ZK state layer (localnet-verified)

cortex-v3/ contains a working zero-knowledge state layer for AI agent memory on Solana: every shared-state transition is a client-generated Groth16 proof (circom 2.2.3, BN254, ~2s proving) verified on-chain by the enigma_nullifier Anchor program via alt_bn128 syscalls. Notes are E2EE-sealed (per-note XChaCha20-Poly1305 + HPKE/X25519 recipient envelopes) and bound into the proof as Poseidon commitments; revocations insert deterministic nullifiers into an Aztec-style indexed Merkle tree with strict non-membership proofs. Only {proof, 6 public inputs} ever leave the client.

• Program: E18KZR1Jq8fG3FFACpoHsE21ME3t1ftKPEwXL7cFWkoZ (localnet; not on mainnet)
• Circuit: 90,897 constraints, one fixed-shape VK, alias-safe (Num2Bits_strict, adversarially tested)
• Reproduce end-to-end (E2EE → prove → on-chain verify → replay rejection): docs/zk-state-layer.md

Claim boundaries: development trusted setup (production needs a multi-party ceremony); nullifiers prove protocol-level non-use, never physical deletion; privacy requires a populated shared tree — the mechanism is verified, operative anonymity requires real participants.

Advanced/source-only path

Use a source checkout only when you need source-only docs, Docker assets, browser-extension scaffolding, package development, or release scripts:

git clone https://github.com/Enigma-Memory/enigma-memory.git
cd enigma-memory
npm run install:local -- --execute --init-vault --bundle ./.enigma/bundle.json
enigma doctor --bundle ./.enigma/bundle.json
enigma-relay demo
enigma-gateway demo

install:local is dry-run unless --execute is present. The command above installs the checked-out package globally and creates a local vault bundle. It does not require Cloudflare, OpenAI, Anthropic, npm publish credentials, a database, or hosted infrastructure.

Manual alternative: inspect the lower-level local vault steps that enigma setup prepares for you. Use a tenant-approved smoke file; do not expand private memory into shell argv.

POSIX shell:

mkdir -p .enigma
ENIGMA_DEMO_MEMORY_FILE=/absolute/path/to/tenant-approved-smoke-memory.txt
test -f "$ENIGMA_DEMO_MEMORY_FILE"
enigma init --bundle ./.enigma/bundle.json --subject local-user --display-name "Local user"
enigma remember --bundle ./.enigma/bundle.json --text-file "$ENIGMA_DEMO_MEMORY_FILE" --purpose user_memory --tags local
enigma context --bundle ./.enigma/bundle.json --query "local context" --purpose local_answer --out ./.enigma/context-pack.json
enigma export --bundle ./.enigma/bundle.json --out ./.enigma/export.json
enigma verify --export ./.enigma/export.json

Windows PowerShell:

New-Item -ItemType Directory -Force .enigma | Out-Null
$env:ENIGMA_DEMO_MEMORY_FILE = "C:\path\to\tenant-approved-smoke-memory.txt"
if (-not (Test-Path -LiteralPath $env:ENIGMA_DEMO_MEMORY_FILE)) { throw "Missing ENIGMA_DEMO_MEMORY_FILE" }
enigma init --bundle .\.enigma\bundle.json --subject local-user --display-name "Local user"
enigma remember --bundle .\.enigma\bundle.json --text-file $env:ENIGMA_DEMO_MEMORY_FILE --purpose user_memory --tags local
enigma context --bundle .\.enigma\bundle.json --query "local context" --purpose local_answer --out .\.enigma\context-pack.json
enigma export --bundle .\.enigma\bundle.json --out .\.enigma\export.json
enigma verify --export .\.enigma\export.json

The bundle is local. Exported proof artifacts contain encrypted/committed vault state and receipt metadata; do not paste raw memory plaintext into relay records, witness checkpoints, SIEM events, public proof artifacts, or shell command lines.

MCP setup

Run the Enigma MCP server over stdio:

POSIX shell:

ENIGMA_BUNDLE="$HOME/.enigma/bundle.json" enigma-mcp

Windows PowerShell:

$env:ENIGMA_BUNDLE = "$HOME\.enigma\bundle.json"
enigma-mcp.cmd

Or through the CLI:

ENIGMA_BUNDLE="$HOME/.enigma/bundle.json" enigma mcp serve

Windows PowerShell CLI form:

$env:ENIGMA_BUNDLE = "$HOME\.enigma\bundle.json"
enigma.cmd mcp serve

Generic MCP client entry:

{
  "mcpServers": {
    "enigma": {
      "command": "enigma-mcp",
      "args": [],
      "env": {
        "ENIGMA_BUNDLE": "/absolute/path/to/.enigma/bundle.json"
      }
    }
  }
}

The MCP server exposes enigma_init, enigma_remember, enigma_search, enigma_context_pack, enigma_delete, and enigma_verify_receipts, plus an Enigma passport summary resource and a memory-use prompt. Provider-native memory should be treated as cache only; Enigma vault state remains canonical.

Connect clients

Supported connector profiles are:

• claude-desktop
• cursor
• kimi-code
• vscode-cline
• roo
• opencode
• generic-mcp

The one-command path above (enigma setup --client auto --connect-installed --overwrite) already connects every installed/config-present client. To connect or preview a single client instead:

enigma connect claude-desktop --dry-run
enigma connect cursor --dry-run
enigma connect kimi-code --dry-run
enigma connect generic-mcp --dry-run

Remove --dry-run from enigma connect <client> only after you are ready for Enigma to merge the mcpServers.enigma entry into that specific client config. Bare enigma setup without --connect-installed or --write-connectors never writes third-party app configs.

Copy-paste MCP snippets:

Claude Desktop:

{
  "mcpServers": {
    "enigma": {
      "command": "enigma-mcp",
      "args": [],
      "env": {
        "ENIGMA_BUNDLE": "/absolute/path/to/.enigma/bundle.json"
      }
    }
  }
}

Cursor:

{
  "mcpServers": {
    "enigma": {
      "command": "enigma-mcp",
      "args": [],
      "env": {
        "ENIGMA_BUNDLE": "/absolute/path/to/.enigma/bundle.json"
      }
    }
  }
}

Kimi Code:

{
  "mcpServers": {
    "enigma": {
      "command": "enigma-mcp",
      "args": [],
      "env": {
        "ENIGMA_BUNDLE": "/absolute/path/to/.enigma/bundle.json"
      }
    }
  }
}

Generic MCP:

{
  "mcpServers": {
    "enigma": {
      "command": "enigma-mcp",
      "args": [],
      "env": {
        "ENIGMA_BUNDLE": "/absolute/path/to/.enigma/bundle.json"
      }
    }
  }
}

Use --mcp-command (alias --command) when a GUI app cannot find shell-installed binaries or needs a .cmd path on Windows.

Browser extension and native host

The browser extension is an unpacked Manifest V3 scaffold in:

apps/browser-extension

The local native messaging host install assets are in:

apps/native-host

Register host name com.enigma.native_host by generating a browser-specific manifest:

enigma native-host manifest --browser chrome --host-path "/absolute/path/to/enigma-native-host" --extension-id "REPLACE_WITH_EXTENSION_ID" --out ./com.enigma.native_host.json

Use --browser edge or --browser firefox for those browsers. Find unpacked Chrome IDs at chrome://extensions > Developer mode > Enigma > Details, Edge IDs at edge://extensions > Developer mode > Enigma > Details, and Firefox IDs at about:debugging#/runtime/this-firefox or from a stable browser_specific_settings.gecko.id/signed add-on ID. The host path must be absolute and point to enigma-native-host or a wrapper that sets ENIGMA_BUNDLE before launching it. Without --out, the generator prints manifest JSON to stdout; with --out, it writes the file and reports { ok, path }. Copy the resulting com.enigma.native_host.json into the browser/OS native-host location, or create the documented Windows registry key yourself. Manual templates remain in apps/native-host/manifests/. Exact copy and registry commands are in apps/native-host/README.md.

The native host is inside the local trust boundary: protect the manifest, wrapper, executable, and ENIGMA_BUNDLE path from local modification. The extension does not use browser sync storage (chrome.storage.sync) at all and requires an explicit user click before inserting Enigma context into ChatGPT, Claude, Kimi, Perplexity, or another supported provider page. Provider-native memory remains cache only; Enigma receipts do not prove provider deletion or model forgetting. See apps/browser-extension/README.md, apps/native-host/README.md, and docs/install-anywhere.md in the source checkout.

Desktop scaffold

The desktop surface is a static local scaffold in:

apps/desktop/src/index.html

Open it directly in a browser or package it inside a desktop shell. It models vault, MCP, clients, import/export, verifier, deletion, mesh, and enterprise screens. Desktop UI state is operational evidence only; cryptographic proof still comes from Enigma receipts and verifier output.

Relay, gateway, Docker, and enterprise modes

Local relay and gateway servers are Node HTTP modules:

• apps/relay/src/server.mjs stores opaque encrypted relay records, signs witness checkpoints, and handles pairing. It rejects plaintext-looking memory fields.
• apps/gateway/src/server.mjs evaluates enterprise policy, emits signed decisions, and exports plaintext-minimized SIEM events. It does not call model providers.

Direct bins are available after a source or package install. Add --state-file <path> when a local demo should survive a restart:

mkdir -p .enigma/state
enigma-relay demo
enigma-relay serve --host 127.0.0.1 --port 8787 --state-file ./.enigma/state/relay-state.json
enigma-gateway demo
enigma-gateway serve --host 127.0.0.1 --port 8797 --state-file ./.enigma/state/gateway-state.json

The same behavior is also available through the main CLI:

enigma relay demo
enigma relay serve --host 127.0.0.1 --port 8787 --state-file ./.enigma/state/relay-state.json
enigma gateway demo
enigma gateway serve --host 127.0.0.1 --port 8797 --state-file ./.enigma/state/gateway-state.json

--state-file is local demo durability, not a production database. Relay state files may contain relay node/trust metadata, local demo signing material, hash-only or opaque relay records, witness checkpoints, completed pairings, and authorization mode; they must not contain raw memory plaintext, prompts, transcripts, decrypted capsule contents, raw request bodies, or pending challenges. Gateway state business data is limited to active policy/minimized policy metadata, policy hash, and plaintext-minimized SIEM/decision evidence, but the snapshot may also include local demo identity and Ed25519 signing key material needed to verify decisions; it must not contain raw memory, prompts, completions, transcripts, provider responses, embeddings, tenant secrets, KMS material, or provider hidden-state claims. Unknown, malformed, or plaintext-looking state fails closed instead of silently resetting.

Keep state files outside source control with owner-only file permissions. Backups are useful for local demo restore only; hosted and BYOC deployments still need real durable storage, KMS/secrets, monitored backups, restore rehearsal, and an accepted operator packet.

For source-checkout Docker demos:

cd enigma
docker compose up --build relay gateway

See docs/install-anywhere.md and docs/deployment-runbook.md in the source checkout for concrete local server, Docker, hosted, and BYOC steps.

Enterprise modes:

• Hosted: Enigma operator runs relay/gateway for a tenant. Requires deployment credentials, TLS, production durable storage, KMS/secrets, monitoring, backups, incident response, and tenant policy.
• BYOC: customer runs relay/gateway in its own cloud or network. Customer controls KMS, network policy, logs, data residency, backups, and deployment credentials.

Both modes keep provider-native memory as cache only. Enigma can prove its own committed state and policy decisions; it cannot prove that a third-party provider erased hidden state or changed model weights.

Import and migration

Importer APIs normalize exported memory/context from ChatGPT, Claude, Mem0, Letta, LangGraph, Zep/Graphiti, and Enigma capsules into candidates with source references, limitations, confidence, and completeness flags. Imports preserve source caveats. A source export becomes canonical only after the candidate is written through an Enigma vault and receives Enigma receipts.

Migration CLI examples:

enigma import chatgpt --file ./chatgpt-export.json --out ./enigma-import-report.json
enigma capsule export --file ./enigma-import-report.json --out ./enigma-capsule.json
enigma capsule import --file ./enigma-capsule.json --bundle "$HOME/.enigma/bundle.json"

Verification commands

Repeatable package/demo audit:

npm run release:audit

This is the one-command local release evidence path; add -- --out <file> when another Enigma production command needs to consume the audit JSON. Docker runtime, hosted cloud, npm publication, and live website review remain external/operator-gated checks rather than prerequisites for release:audit.

Local provenance/SBOM checksum evidence:

npm run provenance:local -- --out ./.enigma/release-provenance.json

Use docs/release-provenance-and-sbom.md to interpret the generated JSON. Reviewers can compare recorded (path, sha256) entries with freshly computed SHA-256 values or with another provenance file. Run npm pack --dry-run separately when reviewing package tarball contents, and build the public site artifact before rerunning provenance when the optional public_site_manifest checksum is in scope. The provenance file is local unsigned checksum evidence only.

Hand-review packet:

python scripts/build_public_site.py
npm run review:packet -- --out ./.enigma-review-packet --public-site ./_public_site

Use docs/reviewer-packet.md to inspect REVIEW_PACKET_MANIFEST.json, evidence/release-audit.json, evidence/local-provenance.json, package/npm-pack-dry-run.json, copied docs/, optional site/, and the recorded SHA-256 values. Pass --public-site only for an already-built generated public-site artifact such as ./_public_site; the packet copies local evidence for review and does not prove npm publication, live Cloudflare deployment, Docker image/runtime behavior, hosted/BYOC readiness, legal approval, signed provenance, or compliance status.

Local smoke path:

ENIGMA_DEMO_MEMORY_FILE=/absolute/path/to/tenant-approved-smoke-memory.txt
test -f "$ENIGMA_DEMO_MEMORY_FILE"
enigma init --bundle ./.enigma/bundle.json
enigma remember --bundle ./.enigma/bundle.json --text-file "$ENIGMA_DEMO_MEMORY_FILE" --purpose local_test
enigma export --bundle ./.enigma/bundle.json --out ./.enigma/export.json
enigma verify --export ./.enigma/export.json
enigma boundary run --scenario committed_crossing

MCP JSON-RPC handshake:

printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"manual","version":"0"}}}\n{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}\n' | ENIGMA_BUNDLE="$PWD/.enigma/bundle.json" enigma-mcp

Connector demo:

node --input-type=module -e "import { runConnectorDemo } from './packages/connectors/src/index.js'; console.log(JSON.stringify(runConnectorDemo({ clientId: 'generic-mcp' }), null, 2));"

Importer demo:

node --input-type=module -e "import { runImporterDemo } from './packages/importers/src/index.js'; console.log(JSON.stringify(runImporterDemo(), null, 2));"

Relay and gateway demos:

enigma-relay demo
enigma-gateway demo

Relay and gateway servers:

enigma-relay serve --host 127.0.0.1 --port 8787
enigma-gateway serve --host 127.0.0.1 --port 8797

Claim boundary

Enigma can honestly claim:

• A local Enigma vault contains or no longer serves a committed memory address.
• A memory create, retrieval, context-pack, update, or tombstone event produced a receipt that verifies offline.
• A boundary harness classified an observed boundary event as committed, blocked, out-of-scope, or failed.
• A relay stored an opaque encrypted record or signed a witness checkpoint without raw memory plaintext.
• A gateway decision followed a specific Enigma enterprise policy at a specific policy hash.

Enigma cannot honestly claim:

• A closed provider physically deleted all internal copies.
• A model forgot training, fine-tuning, cache, telemetry, or hidden personalization state.
• Enigma caused semantic forgetting across model outputs, hidden personalization, embeddings, summaries, caches, or third-party systems outside Enigma state.
• Imported provider memories are complete unless the source export explicitly proves completeness.
• A signed memory statement is true in the real world; receipts prove custody and lifecycle, not factual correctness.
• Token ROI, profit, equity, revenue share, investment return, or token price expectation.
• Tamper-proof hardware or raw compute superiority.
• Benchmark leadership without measured repository evidence.
• Hosted cloud or customer BYOC deployment is live without the required credentials, domain/TLS, production durable storage, KMS/secrets, monitoring, backups, incident ownership, and SIEM/log routing; local --state-file demo state is not hosted/BYOC readiness.
• That a local review packet or local provenance/SBOM output is signed provenance, registry attestation, git/source-control evidence, SLSA level, compliance certification, Docker image digest/runtime evidence, npm publication, hosted/BYOC readiness, or hosted/cloud deployment proof.

Read next:

• docs/overnight-build-master-plan.md
• docs/release-evidence-2026-06-23.md
• docs/release-provenance-and-sbom.md
• docs/reviewer-packet.md
• SECURITY.md
• docs/security-threat-model.md
• docs/operator-acceptance-packet.md
• docs/cloudflare-token-and-domain-runbook.md
• docs/public-api-reference.md
• docs/install-anywhere.md
• docs/client-connectors.md
• docs/deployment-runbook.md
• docs/production-release-checklist.md