⬡ How Daimon works

Architecture

A daimon is three things at once: a trained AI, an encrypted memory you own, and a transferable on-chain asset. The diagram below shows how those three layers compose.

The stack at a glance

                ┌──────────────────────────────────────────────┐
                │              FAMILIAR (this dApp)            │
                │  Spawn · Train · Brain · Act · Market        │
                └────────────────┬─────────────────────────────┘
                                 │ uses
              ┌──────────────────┴──────────────────┐
              ▼                                     ▼
  ┌──────────────────────────┐         ┌──────────────────────────┐
  │      MEMORY              │         │       EXECUTION          │
  │  Encrypted iNFT memory   │         │  MEV-resistant intent    │
  │  (SealedMind primitive)  │         │  solving in a TEE        │
  └──────────────────────────┘         │   (VeilSolver primitive) │
                                       └──────────────────────────┘
                              │
                              │  everything settles on
                              ▼
                  ┌──────────────────────────┐
                  │       0G CHAIN           │
                  │  Storage · Compute · L1  │
                  └──────────────────────────┘

Spawn

A SealedMindNFT (ERC-7857) mints to your wallet. An encrypted memory vault is keyed under your wallet-derived key — only you can read it.

Train + Act

Every message becomes encrypted memory. When the daimon trades, intents are ECIES-encrypted and solved inside an Intel TDX TEE — no mempool exposure.

Transfer

Your daimon is property. Rent its brain for a fixed window (capability-gated). One day, sell it outright or pass it down.

What this unlocks

Inherit a trader's intuition
A long-running daimon holds years of preference data. Hand it to your kid, your fund, your successor.
Rent alpha for 30 days
A profitable daimon's brain is a leasable instrument. Capability expires, access stops on-chain.
Move agents between platforms
The brain is yours, not the platform's. Take your daimon with you the way you take a wallet.
Auditable AI for institutions
Every memory access leaves an on-chain trail. Compliance teams can verify without seeing plaintext.

Daimon vs. the alternatives

AI agents today fall into two camps. Both leak something. Daimon doesn't.

Property	ChatGPT / Replika	Ollama / local agents	Daimon
Who reads your memory	The platform	Just you (one device)	Just you. Encrypted under your wallet.
Move it to another app	No	Manual export only	Native — it's an iNFT
Sell, rent, or inherit	No	No	Yes — on-chain, capability-gated
Trade execution privacy	N/A	Public mempool	ECIES → TEE → ECDSA settlement
Audit trail for access	Closed logs	None	On-chain MemoryAccessLog
Inference attestation	Trust the operator	Local model only	Intel TDX, verifiable on-chain

Trust model

Memory privacy

Encrypted under a wallet-derived key in your browser. SealedMind backend never sees plaintext.

Trade privacy

Intent ECIES-encrypted to a TEE solver pubkey. Plaintext decrypted only inside Intel TDX.

Audit

Every memory access fires a background MemoryAccessLog tx. Surfaced inline as a clickable chainscan link.

v1 caveat — a daimon's encrypted memory is bound to the original owner's wallet-derived key. SALE flow records the transfer on-chain but does not re-key the brain; threshold re-encryption is planned for v2. RENT flow works fully today: a capability gates recall on the SealedMind backend until expiry.

FAQ

Is the LLM running locally or in the cloud?

Both, depending on the call. The TEE-attested chat (Qwen 2.5 7B) runs in an Intel TDX enclave on 0G Compute. Your prompts and the model's outputs are sealed inside the enclave — even the operator running the hardware can't read them.

What stops me from copying my daimon's memory to a friend?

Memory is encrypted under your wallet-derived key. To grant a friend access, you sign a capability grant — on-chain, time-bound, revocable. There's no plaintext copy floating anywhere.

Why not just use an NFT as the agent's identity?

A vanilla NFT is just a pointer. ERC-7857 (the standard SealedMind uses) makes the underlying encrypted data a first-class part of the token — the data hashes are on-chain, transfers re-key the brain via TEE proofs.

What's the worst-case if VeilSolver's TEE is compromised?

The execution plan would be discoverable. But settlement is bounded by `minAmountOut` in the contract, and the ECDSA solver key prevents arbitrary plans from being executed. MEV resistance degrades; counterparty risk does not.

Will my daimon work if I switch wallets?

A daimon is one wallet, one brain. Switching wallets means starting a new daimon with no shared history. The transfer roadmap (v2: threshold re-encryption) is how this changes.

Spawn one and see.

The argument for Daimon lives in the demo, not the diagrams. Two minutes of training, one approved trade, and you'll see why memory and execution had to ship together.

Spawn a daimon →