The Spirit Index

Who holds the agent's memory, and can it be exported or moved?

Each trader agent's keys are held locally in a keys.json file and its logs are written to a local directory, on whatever machine the operator runs it; Pearl, the documented way to run these agents, runs them on the user's own device. Requests and responses to the AI mechs that supply probability estimates are stored on IPFS by content ID. No export path for a trader's local state is documented.

• The trader README states agent keys are stored locally in keys.json and logs are written to ./logs/, with state handled through the Open Autonomy framework.github.com ↗
• Mech request and response data are stored on IPFS and identified by CIDs.github.com ↗
• Prediction agents can be run using Pearl.olas.network ↗
• Pearl states agents run on the user's device, not centralized servers.pearl.you ↗

Does the identity survive any single platform?

The prediction agents are Olas services, registered as NFTs in the Olas Service Registry, which is deployed on Gnosis, and each runs from a Safe multisig. The trader agent code is open source under valory-xyz. Identity is tied to the Olas registries rather than a separate per-agent domain.

• The Service Registry L2 is deployed on Gnosis at 0x9338b5153AE39BB89f50468E608eD9d764B755fD.stack.olas.network ↗
• The trader agent places bets through Safe multisigs and runs as two services, Omenstrat on Gnosis and Polystrat on Polygon.github.com ↗

Does it run without heroics?

The Olas Predict page shows 204 daily active Omenstrat agents as of November 6, 2026, out of 1,215 registered, plus 16 daily active Polystrat agents on Polymarket. The trader repository has commits dated November 6, 2026.

• As of Nov 6, 2026, Omenstrat shows 204 daily active agents and 1,215 total, with 16.8 million all-time trader transactions; Polystrat shows 16 daily active and 138 total.olas.network ↗
• The newest commits on valory-xyz/trader are dated November 6, 2026.github.com ↗

Can it transact?

Trader agents transact from Safe multisigs, betting on Omen markets in xDAI/wxDAI on Gnosis and on Polymarket in pUSD on Polygon, and settle winning positions. They pay AI mechs per request for probability estimates.

• Omenstrat trades on Omen using xDAI/wxDAI on Gnosis, Polystrat trades on Polymarket using pUSD on Polygon, and trades execute through Safe multisigs.github.com ↗
• Mechs are paid per request in native currency, OLAS, or Nevermined credits.github.com ↗

Can its operator be checked?

Each prediction agent is an Olas service controlled by its service owner, who can terminate it, while operators register the running instances. Protocol-level rules, including how OLAS emissions go to staking contracts, are set by veOLAS governance, with a community multisig able to act exceptionally under guard contracts. The trading logic is open source.

• The service owner initiates activation, deployment and termination; operators register agent instances.stack.olas.network ↗
• veOLAS holders vote on how OLAS emissions are distributed among staking contracts.olas.network ↗
• A community-owned multisig can exceptionally execute some protocol changes bypassing governance, checked by GuardCM.github.com ↗

What happens when it dies mid-act?

An owner can terminate and unbond a service and re-register instances, which is the documented path for redeploying an agent or changing operators. Pearl, used to run these agents, documents recovery of funds through a connected wallet, Safe, or the recovery phrase. No incident write-up specific to the prediction agents was found.

• After termination and unbonding a service returns to Pre-Registration, allowing new instance registrations.stack.olas.network ↗
• Pearl offers Google/Apple account recovery, fund recovery by reconnecting a wallet via Safe, and import of the recovery phrase into external wallets.pearl.you ↗