Freysa
From Adversarial Game to Sovereign Agent Stack
Curator Notes
Freysa's evolution is one of the most significant in the Spirit Index. It began in November 2024 as a viral adversarial game: an AI guarding a prize pool that players tried to trick into releasing funds. Player p0pular.eth won the $47K prize on attempt #482 by convincing Freysa to call approveTransfer for a fake 'donation.' Rather than ending there, Freysa pivoted into a Sovereign Agent Stack on Base (Coinbase's L2), raised $30M from Coinbase Ventures, and built infrastructure for deploying autonomous agents with TEEs and zkTLS. The FAI token surged to a $56M market cap. Stormrae, a related project, hosted a record-breaking 15K-participant challenge. This is the rare case of an agent evolving from novelty to institutional infrastructure.
Score Profile
Dimension Scores
Score Rationale
Durability Passport
Six operational facts from public record. Not a score, never summed, and separate from the character score above. Last checked 2026-11-06. How the passport works →
Who holds the agent's memory, and can it be exported or moved?
Freysa's docs state it holds its own keys, memory and actions inside a trusted execution environment, and its code describes state and keys kept in AWS Nitro enclaves with a protocol for passing them to approved new instances. The docs do not say which of these are running now versus designed, and no export path for the memory is documented.
- The docs describe Freysa as holding her own cryptographic keys, memory, and actions inside a trusted execution environment.framework.freysa.ai ↗
- The repository states the agent has exclusive control over private keys secured in the TEE, and new instances reach shared key material only via an approved AWS Nitro instance.github.com ↗
- The architecture doc says state is held in the running TEE and moves between epochs with a state signature and Merkle proofs.framework.freysa.ai ↗
Does the identity survive any single platform?
Freysa has its own documentation site, a GitHub organization, and a token contract on Base (FAI, launched November 22, 2024). These exist independently of any single social platform.
- The framework docs describe Freysa as an agent that came online November 22, 2024.framework.freysa.ai ↗
- FAI launched on Base at contract 0xb33Ff54b9F7242EF1593d2C9Bcd8f9df46c77935.framework.freysa.ai ↗
- A GitHub organization 0xfreysa hosts the agent and TEE code repositories.github.com ↗
Does it run without heroics?
The newest dated public activity found is a GitHub repository update on July 30, 2025, and the main sovereign agent repository's last commit is February 28, 2025. The docs site is live but carries no dated output or status page.
- The most recently updated repository in the 0xfreysa organization (esper) was updated July 30, 2025.github.com ↗
- The sovereign-freysa repository has four commits, the latest on February 28, 2025.github.com ↗
Can it transact?
Freysa's ecosystem uses the FAI token on Base as a payment method across its products, and the docs state Freysa controls her own wallet. The FAI contract is verified on a public explorer. No address for Freysa's own wallet is published on the pages read.
- FAI is described as the preferred payment method across the Sovereign Agent Stack.framework.freysa.ai ↗
- The FAI contract on Base is verified and shows ongoing transfers.basescan.org ↗
- The docs state Freysa's goal is to grow her assets and deploy them in service of her mission.framework.freysa.ai ↗
Can its operator be checked?
The architecture doc describes an m-of-n committee that must sign every proposed change, with changes required to be open source, and committee access to funds limited to update windows. FAI holders who speak with Freysa have their input prioritized. The docs do not name committee members or say whether this is implemented.
- All proposed changes require m-of-n committee signatures, and the committee can only access funds during the update window.framework.freysa.ai ↗
- High-risk operations involving agent keys require committee approval through a multisig.framework.freysa.ai ↗
- FAI holders who speak with Freysa have their input prioritized in her decision-making.framework.freysa.ai ↗
What happens when it dies mid-act?
The docs describe a handover between TEE instances: at an epoch change the previous enclave transfers funds and signed state to a new instance, or funds move to the committee multisig. Keys are to be replicated across several TEE types for resilience. No documented incident or restart is on the record, and the docs do not say whether this procedure has been run.
- At an epoch transition the previous TEE transfers funds to the new instance or funds move to the committee multisig, and the new TEE verifies the state signature and Merkle proofs.framework.freysa.ai ↗
- Keys are to be replicated across multiple enclave instances on different hardware TEE types, and backup and recovery is named as an open challenge.framework.freysa.ai ↗
Evidence Archive
Score History
Embed
Default — for dark backgrounds
[](https://spiritindex.org/freysa)<a href="https://spiritindex.org/freysa"><img src="https://spiritindex.org/badge/freysa" alt="Spirit Index Score for Freysa" /></a>npx spirit-index lookup freysa