Skip to main content

Chatoshi

Chatoshi — 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).

Chatoshi — an AI/Agents project on the Solana network, token (symbol: CHATOSHI).

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 application/browser and chat assistant for Solana users: AI insights on projects/the market and help with navigating the ecosystem are claimed.
  • Who it’s for: DeFi users/traders on Solana and developers (via the SDK).
  • Why onchain/token: the existence of an SPL token on Solana is confirmed; the necessity of the token as a mandatory mechanism of the application’s operation is not established per Tier‑1.
  • What you can actually touch (Tier‑1): the web chat chat.chatoshi.ai and the application download for Windows/MacOS from the official website.

How it works (very briefly)

  1. The user does: opens the application/chat and asks a question or requests an analysis of a project/token.
  2. The system does: returns an AI answer/analysis (claimed: market analysis, detection of suspicious tokens).
  3. The user gets: brief insights and navigation across the Solana ecosystem.
  4. Where the blockchain is: per Tier‑1, the website is oriented toward Solana; the project token exists on the Solana network.
  5. Token role (if any): a specific mandatory utility of the token for the operation of the product is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Chatoshi
Also known as (aliases) CHATOSHI, Chatoshi.ai
Logo (logo) ../assets/640_chatoshi_logo.svg
Token symbol (ticker) CHATOSHI
Category AI/Agents | 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 Bhu2wBWxfWkRJ6pFn5NodnEvMCqj9DLfCU5qMvt7pump
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) — (the utility/necessity of the token is not established per Tier‑1).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI assistant for Solana Web3 analysis
Use‑case (use_case) Solana (token analysis + risk signals)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Chatoshi is positioned as an application/browser and chat assistant for Solana users that helps navigate projects and the market and claims functions for detecting suspicious projects/tokens. The website also describes an SDK that allows embedding chat functionality and “web3 analysis” into third‑party web applications.

Features/modules

  • Web3 browser: an interface for working in the Solana ecosystem.
  • AI search / chat assistant: answers and “market analysis” (claimed).
  • Chatoshi SDK: a library/widgets for embedding the chat and an event model (Tier‑1 docs).

Typical scenarios

  • Scenario 1: a user opens the chat and asks about a token/project → gets an AI answer/brief breakdown (claimed).
  • Scenario 2: a user uses the application as a “command center” for navigating Solana → gets unified access to tools (claimed).
  • Scenario 3: a developer embeds the SDK → gets a chat widget/integration (claimed).

Getting started (wallet/network)

  • What you need: a web browser (for chat.chatoshi.ai) or installation of the application (Windows/MacOS).
  • Network/chain: Solana (the product’s focus per Tier‑1).
  • Fees: Solana network fees arise for onchain operations (if the user performs them).

Architecture/tech (non‑AI)

  • Components: the client application/browser + the chat service; the token on the Solana network.
  • Participant roles: users, developers (SDK), the team/product operators.
  • Where logic runs: the AI part — offchain; onchain — the token.
  • Dependencies: the Solana ecosystem, web interfaces, SDK/partner integrations.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (there is only the fact of the token’s existence).
  • Protocol necessity drivers: No Tier‑1 justification of “why without the token the product breaks down” was found.
  • Who pays fees: users for operations on Solana.
  • Where fees go: to Solana validators (per the network rules).
  • Issuance/burn: —.
  • 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: the risk of relying on AI hints; browser/integration risks; risks of the token as a separate onchain asset.

Project status and timeline

  • Current status: active (the website publishes links to downloads/the chat).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: Solana tools/services via links on the website; an SDK for web integrations.
  • Partners: —.
  • Where it’s actually used: the web chat and downloads are available via Tier‑1 links (see Evidence).

AI component of the project

  • What is real AI here? In Tier‑1, an AI assistant/chat is described and functions for analysis and detection of suspicious projects are claimed.
  • What is truly onchain? The SPL token on the Solana network.
  • Why is a token needed? Per Tier‑1, the utility/necessity of the token is not established.
  • Red flags (based on the information found): absence of a Tier‑1 description of AI quality metrics; absence of a Tier‑1 specification of the token utility; mixing “market analysis” with any expectations of returns (not related to DecAI Fit).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI is described as a working part of the product (chat/assistant), not only a roadmap intent.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): The Tier‑1 website describes an “AI-powered chat application” and the available surfaces.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The AI assistant is claimed for web3 analysis/insights and helping the Solana user.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): The Tier‑1 website describes the AI search/market analysis functions and the purpose of the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a web chat and links to application downloads (Windows/MacOS).
  • Evidence: Tier‑1 — https://www.chatoshi.ai/ ; https://partner.chatoshi.ai/docs/getting-started/introduction
  • Why sufficient / why not (one line): Tier‑1 provides a “touchable” surface and documentation on getting started/the SDK.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): Tier‑1 describes the functionality but does not provide quantitative quality metrics.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): The SDK and the basic integration method are described (widgets, display modes, events, quick start).
  • Evidence: Tier‑1 — https://partner.chatoshi.ai/docs/getting-started/introduction ; https://www.chatoshi.ai/
  • Why sufficient / why not (one line): There is a tech doc on integration and a description of the SDK layer.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint Bhu2wBWxfWkRJ6pFn5NodnEvMCqj9DLfCU5qMvt7pump
  • Evidence: Tier‑1 — https://solscan.io/token/Bhu2wBWxfWkRJ6pFn5NodnEvMCqj9DLfCU5qMvt7pump
  • Why sufficient / why not (one line): There is a verifiable onchain artifact (the token on Solana).
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 (other than the token).
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): OC_2 requires addresses/contracts and a description of onchain logic; none of this was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality for the product was found.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): Tier‑1 describes the product as an application/chat; onchain criticality is not proven.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an SPL token, CHATOSHI, on the Solana network.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/ ; https://solscan.io/token/Bhu2wBWxfWkRJ6pFn5NodnEvMCqj9DLfCU5qMvt7pump
  • Why sufficient / why not (one line): The Tier‑1 website publishes the token address; the onchain page confirms the mint.
  • 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): Payment for the service with the token as a mandatory function is not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): There is no description on Tier‑1 of a tariff/access tied to the token.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties requiring the token are not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): There is no Tier‑1 description of staking/slashing/reward mechanics on the token.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.chatoshi.ai/
  • Why sufficient / why not (one line): Tier‑1 has no description of a DAO/voting.
  • 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://www.chatoshi.ai/
  • Why sufficient / why not (one line): There is no specification of “what breaks down without the token” to set 1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.chatoshi.ai/ Official description of the product (chat/browser/SDK), as well as the published token address.
Tier‑1 https://chat.chatoshi.ai/ A “touchable” surface: the application’s web chat.
Tier‑1 https://partner.chatoshi.ai/docs/getting-started/introduction Tier‑1 documentation on the SDK/integration (quick start).
Tier‑1 https://solscan.io/token/Bhu2wBWxfWkRJ6pFn5NodnEvMCqj9DLfCU5qMvt7pump The existence of the token on the Solana network (SPL mint).
Tier‑1 — No Tier‑1 source for claim “the token is necessary as a mandatory mechanism of the product” was found.

No comments to display

Back to top