cryptosnif
EN ↗
EnglishFrançais · Translation pendingPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-FAI-001

Freysa (FAI)

Base · Token contract · Documentation reviewed

Documentary contract0xb33ff54b9f7242ef1593d2c9bcd8f9df46c77935

The verdict

Unrated · 0% Evidence coverage

Operational strength remains unproven; unrated with 0% scoring coverage.

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Inspect the evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

The Promise

This dossier examines the documented purpose and mechanisms of Freysa (FAI) on the Base network, identified by the contract address 0xb33ff54b9f7242ef1593d2c9bcd8f9df46c77935. The stated aim is to evaluate an evolving AI stack and agent, specifically described as the world's first adversarial agent game. This review focuses strictly on the provided documentary records and does not verify current network operation, deployed bytecode, or active control by any party.

Established Facts

The pinned Trust Wallet registry entry for FAI on Base lists the asset with eighteen decimal places, a standard for amount representation that does not measure supply or value. The registry labels this entry as active within the community-maintained directory. This directory serves as a documentary context for token information but does not validate live network performance, consensus behavior, or current deployment status. The ERC-20 specification defines a standard interface for fungible tokens, including functions for reading balances, transferring assets, and managing allowances where a spender is authorized to use a specific amount. A wallet label based on this standard establishes no independently checked compliance, actual controller permissions, or security guarantees. No token transaction was performed during this review.

Unknowns

Independent verification of beneficial ownership, current program behavior, and complete incident history remains absent. The registry description contains project claims regarding partnerships and economic niche, but these are attributed statements from the community-maintained source, not independently established issuer statements. The scope of the registry explicitly excludes brand-new tokens from submissions, meaning it cannot provide an exhaustive inventory of recent launches. Consequently, the operational strength, liquidity, and adoption metrics for this specific asset remain unproven and unclassified.

Consequences

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of independent dated network observations means that the active status in the registry is merely a metadata label without live-network validation. Users relying solely on this documentation cannot assess the safety, reserve integrity, or security audit status of the deployed implementation. The gap between the registry claim and verified operational reality leaves critical risk factors unaddressed.

Verdict

Operational strength remains unproven. The asset is unrated with zero percent scoring coverage across all dimensions including technology, usage, economics, governance, resilience, and liquidity. Essential criteria such as identity, supply, and control are missing from the evidence base. The dossier confirms only the existence of a documentary record; it does not confirm the functionality, safety, or legitimacy of the underlying project.

What Would Change It

A revised assessment would require reproduced identity checks, independent dated network observations, and criterion-specific evidence covering the missing essential dimensions. Calibration and editorial review would follow the submission of this verified data. Until such independent operational verification is provided, the unrated status and lack of coverage remain definitive.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured Base record for FAI

The pinned Trust Wallet Base integration record names FAI with symbol FAI, documentary address 0xb33ff54b9f7242ef1593d2c9bcd8f9df46c77935 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BASE and active. Its community-maintained description states: "Freysa is an evolving AI stack and agent, starting as the world's first adversarial agent game." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: f11be81196d74c4e61813545bc5005fa30beccbb7091eaf24dfdf2412b662f0f

Trust Wallet: pinned Base directory context

The pinned Trust Wallet base network-context record identifies the community registry directory for Base. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: a197d8ac29d06d8a50f717312eecf4b62aa6e60465836d79c89106c081d9ab40

Trust Wallet Assets: README.md (bbe582d25a22)

The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

Ethereum ERC-20: pinned token interface specification

The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation