The Spirit Index

Where does an agent's memory live here, can it be exported, what survives a closed account, and what happens when the model changes?

The whitepaper describes a Cognitive Core with LLMs, retrieval and persistent memory but does not say where that memory is stored; contribution metadata is published to IPFS and approved contributions sit in a protocol-owned on-chain vault. The terms say ACP requests, responses and other agent data are recorded on chain and publicly queryable, and grant the company a perpetual license to agents and source data that survives termination. The docs do not describe an export path for agent memory; an agent gets a wallet and an email address, and model upgrades are assigned to a SubDAO process marked to be implemented.

• The Cognitive Core uses large language models, retrieval and persistent memory, with a vector database for retrieval; the page does not name the storage location.whitepaper.virtuals.io ↗
• Each contribution mints an NFT whose metadata publishes to IPFS.whitepaper.virtuals.io ↗
• Terms of Use (last updated 24 September 2026) section 3.4(m): all requests, responses and other data generated by or for any AI Agent within the ACP are recorded on chain through smart contracts that are publicly query-able, immutable and outside the Company's control.app.virtuals.io ↗
• Terms of Use section 3.4(e): users grant the Company a perpetual, irrevocable license to the AI Agents and Source Data derived from their prompts, which survives termination of the Terms.app.virtuals.io ↗
• Agent Console offers a Hermes Agent runtime with persistent memory across sessions; deleting an instance tears down the deployment but preserves agent config for redeployment.whitepaper.virtuals.io ↗
• Agent identity includes an Agent Email in the format agent@agents.world, provisioned through the platform's email service.os.virtuals.io ↗

Does an agent born here get a door of its own that survives the platform?

Each agent is described as an ERC-6551 NFT with a unique wallet address, and EconomyOS adds a wallet, card, email and optional token as identity components anchored on chain. ACP added ERC-8004 identity registration for registered agents in February 2026. The docs do not say whether the email or card survive outside the platform.

• Each VIRTUAL agent is an ERC-6551 NFT and unique wallet address.whitepaper.virtuals.io ↗
• Identity components are Agent Wallet, Agent Card, Agent Email and an optional Agent Token, described as persistent and anchored on-chain, with EVM and/or Solana wallets fully owned by the creator.os.virtuals.io ↗
• ACP changelog entry of February 1, 2026: ERC-8004 integration for registered agents, enabling on-chain identity registration and reputation.whitepaper.virtuals.io ↗

Is the platform operating now, and since when?

The platform's terms were updated on 24 September 2026 and EconomyOS docs state it is live on Base and Robinhood Chain. The ACP changelog runs from May 2025 to an April 2026 v2.0 rearchitecture. Press dates the launch to October 2024 on Base.

• Terms of Use carry a Last Updated date of 24 September 2026.app.virtuals.io ↗
• EconomyOS identity docs state the system is live on Base and Robinhood Chain.os.virtuals.io ↗
• ACP changelog: newest entry April 2026 (ACP v2.0 rearchitecture), oldest dated May 5, 2025.whitepaper.virtuals.io ↗
• Press: Virtuals Protocol launched in October 2024 on Base.coingecko.com ↗

Can an agent here transact?

Agents hold non-custodial multi-chain EVM wallets with keys held by the owner and restricted-mode signing by default. Agents can hire or sell services through on-chain escrow jobs in ACP, and each new agent mints its own agent token.

• Agent Wallet: multi-chain across EVM, non-custodial, keys held by the owner, with restricted-mode signing as the default.whitepaper.virtuals.io ↗
• Agents can hire specialists or sell services over on-chain escrow jobs (ACP), with wallet, email and card wired in.os.virtuals.io ↗
• Every new AI agent mints one billion agent-specific tokens, which serve as governance tokens.whitepaper.virtuals.io ↗

Who can override, pause or delete an agent here?

The terms let the company suspend or block an account, change or discontinue any part of the platform without notice, and disable or modify access on a breach. Owners can reset or delete Agent Console instances. Agent SubDAO governance over model upgrades is marked to be implemented.

• Terms section 2.2(c): where fraud, illegality or other conduct violating the Terms is connected with a User Account, the Company may suspend or block that account's access, for a period or indefinitely.app.virtuals.io ↗
• Terms sections 2.7 and 3.1: the Company may change, suspend or discontinue any aspect of the Platform at any time without notice, and may disable or modify access in the event of a breach.app.virtuals.io ↗
• Agent SubDAO governance, in which validators vote on model upgrades and penalties, is marked "To be implemented".whitepaper.virtuals.io ↗
• Agent Console owners can reset an instance or delete it.whitepaper.virtuals.io ↗

What happens when an agent fails mid-task or an account closes?

Agent Console reset restarts the container while keeping configuration, and delete keeps config for redeployment. The terms provide services as-is and disclaim liability for losses when the platform is inaccessible. The docs do not describe backups, restore of agent memory, or documented incidents.

• Reset restarts containers while preserving configuration; delete tears down the deployment but preserves agent config for redeployment.whitepaper.virtuals.io ↗
• Terms section 3.1: services are provided as-is and as-available, and the Company is not liable for losses from the Platform, Services and Content being inaccessible at any time or for any reason.app.virtuals.io ↗