Skip to main content

Onchain AI

Onchain 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).

Onchain AI — an AI/Other \| Infra project (per public claims) + a token on Ethereum (symbol: OCAI).

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: the OCAI token (ERC‑20, Ethereum) + a set of claims about an “L1 blockchain with an AI chatbot/contract creation tool”.
  • Who it’s for: users/developers (per the claims), but per the available sources no confirmed Tier‑1 technical artifacts of the L1/AI module were found.
  • Why onchain/token: the onchain fact is the existence of the OCAI token on Ethereum; the rest of the onchain architecture (L1) is not confirmed per the available sources.

How it works (very briefly)

  1. The user does: interacts with the OCAI token (transfer/DEX operations) on the Ethereum network.
  2. The system does: the token’s smart contract keeps records of balances and transfers.
  3. The user gets: an onchain‑verifiable balance/transfer.
  4. Where the blockchain is: Ethereum mainnet (for the token).
  5. Token role: the “whitepaper” on the project’s domain claims that the token is used for transfers/staking/fee payments, but verifiable onchain mechanics for this are not confirmed per the available sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Onchain AI
Also known as (aliases) OCAI, Onchain AI Token
Logo (logo) ../assets/567_onchain-ai_logo.svg
Token symbol (ticker) OCAI
Category AI/Other | 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 0x4309E88D1D511F3764Ee0F154cEE98d783B61f09
Token model (token_type) —
Max supply 100,000,000 OCAI (max total supply)
Issuance fixed
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI chatbot/"Web3GPT"
Use‑case (use_case) no-code contract generation
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Onchain facts on the OCAI token on Ethereum are reliably confirmed (contract and max supply in Etherscan). At the same time, the “whitepaper”/description on the onchain-ai.com domain looks like a broker affiliate website and contains irrelevant marketing inserts; the docs.onchain-ai.com domain is also marked as expired. The OnchainAItech GitHub account has no public repositories.

Therefore, any statements about an L1 network, an AI chatbot and “Web3GPT” are treated as claims, not verified technical facts.

Features/modules

  • OCAI ERC‑20 token: an onchain contract on Ethereum.
  • Claims about “AI chatbot / Web3GPT / L1”: without verifiable Tier‑1 artifacts.

Typical scenarios

  • Scenario 1: the user transfers OCAI → onchain accounting on Ethereum.
  • Scenario 2: the user reads the claims about “Web3GPT/L1” → requires re‑checking against Tier‑1 artifacts (code/addresses/docs).

Getting started (wallet/network)

  • What you need: an EVM wallet (for onchain operations with the token).
  • Network/chain: Ethereum mainnet.
  • Fees: Ethereum gas for transactions.

Architecture/tech (non‑AI)

  • Components: the OCAI token contract + standard EVM tools.
  • Participant roles: token holders.
  • Where logic runs: onchain — token accounting; offchain — interfaces/wallets.
  • Dependencies: Ethereum RPC/infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: the “whitepaper” claims transfers/staking/fee payments, but verifiable onchain mechanics for this are not confirmed (per the available sources).
  • Who pays fees: Ethereum gas.
  • Issuance/burn: max total supply is given in Etherscan.

Governance

  • Who makes decisions: — (not established per the available sources).
  • How protocol parameters change: — (not established per the available sources).
  • Where decisions are discussed/made: — (not established per the available sources).
  • Keys/multisig: — (not established per the available sources).

Security and incidents

  • Audits: — (not found).
  • Bug bounty: — (not found).
  • Incidents: — (not established).
  • Threat model: standard risks of an ERC‑20 token + risks of unreliable/unconfirmed claims.

Project status and timeline

  • Current status: mainnet (the token on Ethereum)
  • Key releases/milestones: — (not found)
  • Roadmap: — (not found)

Ecosystem/integrations

  • Integrations: — (not established)
  • Partners: — (not established)
  • Where it’s actually used: — (not established)

AI component of the project

  • What is real AI here? The project’s domain has claims about an “AI chatbot module / Web3GPT”, but no reliable Tier‑1 confirmation of an AI component/AI intent was found (the “whitepaper” page looks like a broker affiliate website).
  • What is truly onchain? the OCAI token contract on Ethereum.
  • Why is a token needed? transfers/staking/fee payments are claimed, but no onchain confirmation of the mechanics was found per the available sources.
  • Red flags (based on the information found): the “whitepaper” looks like a broker affiliate website; the docs domain is expired; GitHub has no public repositories.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present (per token/onchain) 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): no reliable Tier‑1 declaration of AI intentions was found; the domain has claims about AI/Web3GPT, but the source looks like a broker affiliate website.
  • Evidence: Tier‑2 — https://onchain-ai.com/whitepaper
  • Why sufficient / why not (one line): due to the low reliability of the “whitepaper” and the absence of technical artifacts, intent is not counted (conservatively).
  • Conflict note (if any): the source looks like an affiliate website, so all dependent flags (AI_1..AI_4) remain 0.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): “what exactly the AI does” is not confirmed by verifiable Tier‑1 technical artifacts.
  • Evidence: Tier‑2 — https://onchain-ai.com/whitepaper
  • Why sufficient / why not (one line): there are descriptions, but without code/demo/metrics we set 0 (conservatively).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no demo of the AI module was found per the available sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 demo/product.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: — (not found)
  • Context (version/date/how measured): — (not found)
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no Tier‑1 metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the tech description/architecture of the AI module is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): code/docs/versions are absent.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: OCAI token (0x4309E88D1D511F3764Ee0F154cEE98d783B61f09)
  • Evidence: Tier‑1 — https://etherscan.io/token/0x4309E88D1D511F3764Ee0F154cEE98d783B61f09
  • Why sufficient / why not (one line): the address and max supply are available in Etherscan.
  • 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 — —
  • Why sufficient / why not (one line): there are no verifiable addresses/code of the L1 logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not confirmed (per the available sources).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 justification.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, OCAI.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x4309E88D1D511F3764Ee0F154cEE98d783B61f09
  • Why sufficient / why not (one line): the token is confirmed 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 role of the token is not confirmed by verifiable artifacts.
  • Evidence: Tier‑1 — https://onchain-ai.com/whitepaper
  • Why sufficient / why not (one line): there is a claim, but no onchain mechanics.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): staking/incentives are claimed, but not confirmed.
  • Evidence: Tier‑1 — https://onchain-ai.com/whitepaper
  • Why sufficient / why not (one line): there are no verifiable contracts/docs.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the governance role of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no Tier‑1 artifacts.
  • 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.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 replaceability test.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0x4309E88D1D511F3764Ee0F154cEE98d783B61f09 OCAI token contract on Ethereum + max total supply.
Tier‑2 https://onchain-ai.com/whitepaper Claims about an L1 + AI chatbot/Web3GPT and the role of the token (as a claim; the page looks like a broker affiliate website; requires technical confirmation).
Tier‑1 https://docs.onchain-ai.com/ The docs domain is marked as expired (Tier‑1 documentation is unavailable).
Tier‑1 https://github.com/OnchainAItech GitHub account without public repositories (no code/releases).
Tier‑3 https://t.me/Onchain_AI Telegram channel with positioning (claim; not proof).
Tier‑2 https://www.coingecko.com/en/coins/onchain-ai Profile (for reference; not Tier‑1).

No comments to display

Back to top