FOMO.fund
FOMO.fund (FOMO) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).
FOMO.fund — an AI/Agents / Community project: the website uses the “Agentic Horizon / Agentic future” positioning, while the extracted Tier‑1 contain no technical description of what exactly the AI does and how the product is structured. The FOMO token is listed as an SPL token on Solana (mint in the explorer link).
Disclaimer
Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.
TL;DR (for readers who are not into AI)
- What it is: a website/project that announces an “agentic” product (details not disclosed in the extracted sources).
- Who it’s for: community members/potential users of the future product.
- Why onchain/token: the token exists onchain; the token utility is not confirmed in the extracted Tier‑1.
How it works (very briefly)
- The user does: visits the website and “Initialize Access” (a claim on the website), subscribes to the channels.
- The system does: publishes the “Relaunch imminent” status and messages (website).
- The user gets: access to communications and the wait for the release (per the website).
- Where the blockchain is: the FOMO SPL token on the Solana network is listed (mint address from the explorer link).
- Token role (if any): no confirmed utility was found in the extracted Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | FOMO.fund |
| Also known as (aliases) | FOMO |
| Logo (logo) | — |
| Token symbol (ticker) | FOMO |
| Category | AI/Agents | Community |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | — |
| Project status (status) | in development |
| Token (standard) | SPL |
| Token contract | ZxBon4vcf3DVcrt63fJU52ywYm9BKZC6YuXDhb3fomo |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | "agentic" product |
| Use‑case (use_case) | agentic future |
| DecAI Fit — AI thesis fit | 2/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 1 / 0 / 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://fomo.fund |
| Docs | https://docs.fomo.fund/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://solscan.io/token/ZxBon4vcf3DVcrt63fJU52ywYm9BKZC6YuXDhb3fomo |
| X | https://twitter.com/Fomodotfund |
| Discord | — |
| Telegram | https://t.me/fomodotfundAnn |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/fomo-3 |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/fomo-fund/ |
General project overview
FOMO.fund in Tier‑1 (website) shows a minimal landing page with the messages “The Agentic Horizon”, “Relaunch imminent” and the “Initialize Access” button. The documentation at docs.fomo.fund is unavailable for extraction (unavailable per the available sources), so it was not possible to describe the product mechanics and the token utility per Tier‑1.
Features/modules
- Landing page/release announcement: system status and “Initialize Access” (website).
- Token: the FOMO SPL token on Solana (link to the explorer).
Typical scenarios
- Scenario 1: a user visits the website → sees the relaunch status and subscribes to the channels.
- Scenario 2: a user checks the token in the explorer → sees the onchain identifier (mint).
Getting started (wallet/network)
- What you need: a Solana wallet for working with the SPL token (for example, Phantom).
- Network/chain: Solana mainnet.
- Fees: Solana network fees in SOL for onchain transactions.
Architecture/tech (non‑AI)
- Components: website + SPL token on Solana.
- Participant roles: community members/token holders.
- Where logic runs: onchain — the token; the product logic is not described in the extracted Tier‑1.
- Dependencies: Solana.
Token/economics (expanded, no forecasts)
- Token utility: — (not confirmed in the extracted Tier‑1).
- Protocol necessity drivers: —.
- Who pays fees: users pay Solana fees for transactions.
- Where fees go: to Solana validators (network fees).
- Issuance/burn: — (supply metadata not established per Tier‑1).
- Security/incentive mechanisms: —.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: high uncertainty due to the absence of a Tier-1 description of the product, AI mechanics and token utility; a separate check of marketing claims is also required given the limited availability of supporting materials.
Project status and timeline
- Current status: the landing page indicates “Relaunch Imminent”; the token exists on Solana.
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? in the extracted Tier‑1 there is only “agentic” positioning without a description of functions/models.
- What is truly onchain? the FOMO SPL token (mint address) is listed, with a link to the explorer.
- Why is a token needed? the token utility is not confirmed in the extracted Tier‑1 (docs/whitepaper/a technical description are needed).
- Red flags (based on the information found): AI‑washing (the word “agentic” without specifics); no available Tier‑1 docs; the token utility and the product’s onchain architecture are unknown.
DecAI Fit component summary
- DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 present | 1 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): the website positions the project as “Agentic Horizon / agentic future”.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there is a Tier‑1 statement of intent about the “agentic” direction, but without evidence for AI_1..AI_4.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): no specific description of AI/agent functions was found in the extracted Tier‑1.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there is no description of “what the AI does”.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): no demo of an AI product was found in the extracted Tier‑1.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there is only a landing page announcement without a demo.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there are no metrics.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): no technical description/architecture of the AI was found in the extracted Tier‑1.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): no documentation/artifacts.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: FOMO token mint: ZxBon4vcf3DVcrt63fJU52ywYm9BKZC6YuXDhb3fomo
- Evidence: Tier‑1 — https://solscan.io/token/ZxBon4vcf3DVcrt63fJU52ywYm9BKZC6YuXDhb3fomo
- Why sufficient / why not (one line): there is an onchain token identifier and a link to the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: the extracted Tier‑1 contain no addresses/contracts of protocol logic (other than the token).
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): without onchain artifacts we consider “onchain = token”.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: if the blockchain were replaced with a server/DB, the landing page/communications would remain; only the onchain token layer would disappear.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): onchain criticality is not shown.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, FOMO.
- Evidence: Tier‑1 — https://solscan.io/token/ZxBon4vcf3DVcrt63fJU52ywYm9BKZC6YuXDhb3fomo
- Why sufficient / why not (one line): the token exists onchain.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): the “payment in the token” utility is not confirmed in the extracted Tier‑1.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there is no description of paying for the service with the token.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentives/collateral/penalties via FOMO are not confirmed in the extracted Tier‑1.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there is no description of the mechanics.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the governance utility of the token is not confirmed in the extracted Tier‑1.
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): there is no description of governance.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): in the absence of confirmed token utility (TK_1..TK_3), the token does not look necessary for the product to work (in its current description).
- Evidence: Tier‑1 — https://fomo.fund
- Why sufficient / why not (one line): the utility is not confirmed → the token looks replaceable.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://fomo.fund | Tier‑1 “agentic” positioning and the relaunch status (without technical details) |
| Tier‑1 | https://solscan.io/token/ZxBon4vcf3DVcrt63fJU52ywYm9BKZC6YuXDhb3fomo | onchain token identifier (mint) |
| Tier‑1 | — | No Tier‑1 source on the description of the product/AI mechanics/token utility was found / not confirmed by Tier‑1 (docs unavailable: timeout). |
No comments to display
No comments to display