flowerAI
flowerAI (FLOWER) — 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).
flowerAI — an AI/Analytics | DeFi project on the Solana network, token (symbol: FLOWER).
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: an AI agent and a platform for “on-chain markets” analytics (per the project documentation).
- Who it’s for: users who need quick insights/analysis on tokens and the onchain activity of wallets.
- Why onchain/token: the FLOWER SPL token on Solana is confirmed; the necessity of the token for the operation of the service is not established per Tier‑1.
How it works (very briefly)
- The user does: submits a query/views analytics on tokens/wallets.
- The system does: AI analysis based on onchain data and the sources described in the docs (FloweyQuant, RAG).
- The user gets: conclusions/summaries on market movement/wallet activity (per the project’s claim).
- Where the blockchain is: the onchain part is confirmed by the FLOWER token on Solana and by the fact that the product analyzes onchain activity.
- Token role: per Tier‑1, it is not established that the token is mandatory for the operation of the service.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | flowerAI |
| Also known as (aliases) | FloweyQuant |
| Logo (logo) | ../assets/599_flowerai_logo.png |
| Token symbol (ticker) | FLOWER |
| Category | AI/Analytics | DeFi |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | SPL |
| Token contract | AVyjco9j8vv7ZPkhCpEoPJ3bLEuw7G1wrrNt8DrApump |
| 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) | FloweyQuant agent + RAG |
| Use‑case (use_case) | analytics for on-chain markets + wallets |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://flowerai.app/ |
| Docs | https://flowerai.gitbook.io/flowerai |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://flowerai.gitbook.io/flowerai |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://solscan.io/token/AVyjco9j8vv7ZPkhCpEoPJ3bLEuw7G1wrrNt8DrApump |
| X | https://twitter.com/flowerAI_sol |
| Discord | — |
| Telegram | https://t.me/FlowerAI_Sol |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/flowerai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/flowerai/ |
General project overview
In the Tier‑1 documentation, flowerAI describes the FloweyQuant AI agent, which analyzes onchain data and provides “instant analysis” on tokens/market movements/wallets. An interactive platform for visualizing the token holders of the FLOWER ecosystem is also mentioned.
As for the onchain part, the card confirms the FLOWER SPL token on Solana (the address is given in the Tier‑1 documentation).
Features/modules
- FloweyQuant (claimed): an AI agent for analyzing onchain activity and “market movements”.
- Token holder visualization platform (claimed): a tool for analyzing onchain behavior.
Typical scenarios
- Scenario 1: the user views analytics → gets a summary of token movement/wallets.
- Scenario 2: the user tracks wallet activity → gets “real-time” insights (per the documentation’s claims).
Getting started (wallet/network)
- What you need: access to the project’s documentation/website.
- Network/chain: Solana (in terms of the token).
- Fees: Solana fees for operations with the token (if performed).
Architecture/tech (non‑AI)
- Components: documentation; website; an SPL token on Solana.
- Participant roles: users of the analytics/agent.
- Where logic runs: AI analysis — offchain; the data/objects of analysis — onchain (Solana and other sources mentioned in the documentation).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 (other than the fact that the token is used as an “ecosystem token”).
Governance
- Governance: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
Project status and timeline
- Current status: active (based on the presence of documentation).
- Roadmap: —.
Ecosystem/integrations
- Integrations: — (we do not record them without Tier‑1 confirmations).
AI component of the project
- What is real AI here? the Tier‑1 documentation describes the FloweyQuant AI agent (RAG) for analyzing onchain data.
- What is truly onchain? the FLOWER SPL token on Solana (the address is given in Tier‑1).
- Why is a token needed? the role of the token as a mandatory mechanism of the product is not established per Tier‑1.
- Red flags (based on the information found): absence of quality metrics/benchmarks (AI_3=0); unclear onchain logic of the product (other than the token); claims about “instant analysis” require verifiable examples/demos.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium 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 | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described as a current component of the product (the FloweyQuant AI agent), not only intent.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): We do not use AI_0 when there is a description of the product function (AI_1=1).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The FloweyQuant AI agent analyzes token performance, market movements and wallet activity (per the Tier‑1 documentation).
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): The documentation explicitly describes the purpose of the AI agent and the types of data analyzed.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): A public demo/app of the agent’s operation is not established per Tier‑1.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): AI_2=1 requires an explicit “touch surface” of a demo/interface; there is a link to the website, but a reproducible demo/app is not confirmed per Tier‑1.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): No quantitative quality metrics/benchmarks were found in the Tier‑1 documentation.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture/versions of the AI component at a level sufficient for 1 are not established per Tier‑1.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): RAG and integrations are mentioned, but there is no formalized tech description/versioning.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: AVyjco9j8vv7ZPkhCpEoPJ3bLEuw7G1wrrNt8DrApump
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai/getting-started/useful-links ; https://solscan.io/token/AVyjco9j8vv7ZPkhCpEoPJ3bLEuw7G1wrrNt8DrApump
- Why sufficient / why not (one line): The Tier‑1 documentation gives the token address, and the explorer link confirms the onchain artifact.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established (other than the token).
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): The documentation contains no enumeration of onchain contracts/addresses of the product logic other than the token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that the product breaks down without the blockchain (other than the fact that the object of analysis is onchain data).
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): OC_3=1 requires a justification of the criticality of onchain mechanics as part of the product, not only “analytics about onchain”.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, FLOWER (ecosystem token), on Solana.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai/getting-started/useful-links
- Why sufficient / why not (one line): The Tier‑1 documentation explicitly names the $FLOWER token and gives its contract address.
- 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 role of the token is not established per Tier‑1.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): No claim “FLOWER is paid for service X” was found in the available Tier‑1 sources.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Incentive/collateral/penalty mechanisms requiring the FLOWER token are not established per Tier‑1.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): There is no description of staking/slashing/incentives tied to the token.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the FLOWER token for governance is not established per Tier‑1.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): There is no description of governance mechanics.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token is not established per Tier‑1.
- Evidence: Tier‑1 — https://flowerai.gitbook.io/flowerai
- Why sufficient / why not (one line): The sources contain no justification “can be replaced without loss of meaning”.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://flowerai.gitbook.io/flowerai | Tier‑1 description of the product and the FloweyQuant AI agent (RAG), the claimed analysis scenarios. |
| Tier‑1 | https://flowerai.gitbook.io/flowerai/getting-started/useful-links | Tier‑1: the contract address of the FLOWER token and the project’s official links. |
| Tier‑1 | https://solscan.io/token/AVyjco9j8vv7ZPkhCpEoPJ3bLEuw7G1wrrNt8DrApump | Onchain fact: the FLOWER SPL token on Solana. |
No comments to display
No comments to display