Skip to main content

VectorChat AI

VectorChat AI — 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).

VectorChat AI — an AI/Inference \| Infra project on the Ethereum network, token (symbol: CHAT).

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 project that claims “decentralized inference” and subnets/modules for RAG scenarios (chunking subnet, etc.).
  • Who it’s for: developers and teams that need an inference/RAG pipeline and infrastructure for chatbot/assistant scenarios (claimed).
  • Why onchain/token: the CHAT token is observable onchain; the necessity of the token for key functions is not established per Tier‑1 sources.

How it works (very briefly)

  1. The user does: integrates the service/subnet or uses the SDK/interface (claimed).
  2. The system does: performs inference and/or data preparation operations (chunking) for RAG scenarios (claimed).
  3. The user gets: inference answers/results and search over a vector index (RAG logic).
  4. Where the blockchain is: the CHAT token is observable onchain; the rest of the stack is described as offchain/infrastructure.
  5. Token role: not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name VectorChat AI
Also known as (aliases) CHAT
Logo (logo) ../assets/576_vectorchat-ai_logo.svg
Token symbol (ticker) CHAT
Category AI/Inference | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xbb3d7f42c58abd83616ad7c8c72473ee46df2678
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Supply parameters/mandatory token utility are not established per Tier‑1 sources.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) decentralized inference + RAG chunking subnet
Use‑case (use_case) inference/RAG infrastructure for conversational AI
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

General project overview

VectorChat is positioned as a project around infrastructure for conversational AI, including “decentralized inference” and subnets/modules for RAG scenarios (for example, a chunking subnet). The docs also state that the current documentation refers to the Beta and will be replaced.

Features/modules

  • Inference/RAG infrastructure: claimed components for conversational AI.
  • Chunking subnet: a subnet/module for chunking (claimed in the project materials).
  • Toffee platform: mentioned as a new platform (in the project materials).

Typical scenarios

  • Scenario 1: a developer connects the infrastructure/subnet → uses inference and/or chunking in a RAG pipeline (claimed).
  • Scenario 2: a team builds a chatbot/assistant service → uses VectorChat components as infrastructure (claimed).

Getting started (wallet/network)

  • What you need: the documentation and the repository (see links_*).
  • Network/chain: Ethereum (the CHAT token is observable via the Explorer).
  • Fees: Ethereum fees (gas) for operations with the token; the product’s fee model is not established per Tier‑1 sources.

Architecture/tech (non‑AI)

  • Components: offchain infrastructure (inference/chunking), onchain — the CHAT token.
  • Participant roles: users/developers; infrastructure operators (claimed).
  • Where logic runs: AI logic — offchain; token/transactions — onchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources.
  • Protocol necessity drivers: not established per Tier‑1 sources.
  • Who pays fees: not established per Tier‑1 sources.
  • Where fees go: not established per Tier‑1 sources.
  • Issuance/burn: not established per Tier‑1 sources.
  • Security/incentive mechanisms: not established per Tier‑1 sources.
  • Distribution and token issuance schedule: not established per Tier‑1 sources.
  • Treasury: not established per Tier‑1 sources.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: not found per Tier‑1 sources.
  • Bug bounty: not found per Tier‑1 sources.
  • Incidents: not found per Tier‑1 sources.
  • Threat model: risks of centralized infrastructure and risks of the token contract/integrations.

Project status and timeline

  • Current status: active (in terms of the token on Ethereum; the product documentation is marked as beta/being updated).
  • Key releases/milestones: not established per Tier‑1 sources.
  • Roadmap: not found per Tier‑1 sources.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1 sources.

AI component of the project

  • What is real AI here? Inference components and RAG scenarios (chunking subnet, etc.) are claimed; confirmed by the project’s Tier‑1 materials, but without metrics (AI_3=0).
  • What is truly onchain? The CHAT token (ERC‑20) on Ethereum is observable onchain.
  • Why is a token needed? Not established per Tier‑1 sources.
  • Red flags (based on the information found): the docs are marked as “soon to be obsolete” (beta/changing documentation); Tier‑1 metrics/tech details are limited.

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_0 (intent) does not apply, since Tier‑1 already describes the AI modules/purpose of the product (see AI_1).
  • Evidence: Tier‑1 — https://www.vectorchat.ai/
  • Why sufficient / why not (one line): AI_0 is used only in the absence of a confirmed function (AI_1..AI_4=0); here AI_1 is already = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): inference services and components for RAG scenarios (chunking) are claimed.
  • Evidence: Tier‑1 — https://www.vectorchat.ai/
  • Why sufficient / why not (one line): the Tier‑1 source describes the AI purpose and modules at the product level.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a public demo/application unambiguously demonstrating AI features was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): the docs state that this is beta documentation, and no direct demo links were found.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1 sources.
  • Context (version/date/how measured): not established.
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): Tier‑1 quality metrics/benchmarks are absent in the available documentation.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a tech specification of the AI components (architecture/versions/reproduction) was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): the docs contain more links to articles/announcements and no sufficient tech documentation.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: CHAT token: 0xbb3d7f42c58abd83616ad7c8c72473ee46df2678
  • Evidence: Tier‑1 — https://etherscan.io/token/0xbb3d7f42c58abd83616ad7c8c72473ee46df2678
  • Why sufficient / why not (one line): the token address and network are confirmed by the Explorer.
  • 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 sources (other than the token).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xbb3d7f42c58abd83616ad7c8c72473ee46df2678
  • Why sufficient / why not (one line): there is no Tier‑1 proof of the protocol’s onchain logic beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the claimed AI features can be implemented offchain; onchain criticality is not proven.
  • Evidence: Tier‑1 — https://www.vectorchat.ai/
  • Why sufficient / why not (one line): there is no Tier‑1 proof that the product is inoperable without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, CHAT (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xbb3d7f42c58abd83616ad7c8c72473ee46df2678
  • Why sufficient / why not (one line): the token is observable in the Explorer.
  • 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 necessity of paying with the token for the key service is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): the Tier‑1 documentation has no unambiguous “payment for services only in CHAT”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/collateral/penalties via the token are not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): there are no confirmed staking/slashing/collateral parameters.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): a Tier‑1 description of governance is absent.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token has not been assessed (mandatory token utility is not established).
  • Evidence: Tier‑1 — https://docs.vectorchat.ai/
  • Why sufficient / why not (one line): without a confirmed mandatory role of the token, replaceability cannot be reasonably asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.vectorchat.ai/ Positioning: decentralized inference / conversational AI (product description).
Tier‑1 https://docs.vectorchat.ai/ Beta documentation: links to materials on the project’s development and the chunking subnet.
Tier‑1 https://etherscan.io/token/0xbb3d7f42c58abd83616ad7c8c72473ee46df2678 The CHAT token (ERC‑20): contract and network.