Skip to main content

Datai Network

Datai Network — 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).

Datai Network — an Infra project, token (symbol: DATAI).

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 peer‑to‑peer network that indexes blockchains and answers external queries (per the Tier‑1 documentation).
  • Who it’s for: developers of “projections”, node operators (indexer/gateway) and data consumers (API).
  • Why onchain/token: Tier‑1 describes payment for queries with DATAI tokens and the network’s smart contracts (staking/registry/dispute/reward) on the Ethereum Sepolia testnet.

How it works (very briefly)

  1. The user does: sends queries to the API (gateway) or deploys a “projection”/node.
  2. The system does: nodes index data and serve queries, matching the consumer with indexers.
  3. The user gets: data (for example, active DeFi positions) via endpoints.
  4. Where the blockchain is: the network indexes external blockchains; its own onchain logic/addresses are not established in this card.
  5. Token role: Tier‑1: DATAI is used to pay for queries (consume data).

Quick links: AI thesis fit

Project passport

Field Value
Project name Datai Network
Also known as (aliases) DATAI
Logo (logo) ../assets/675_datai-network_logo.svg
Token symbol (ticker) DATAI
Category Infra
Primary chain (chain) Ethereum
Type EVM
Network status testnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x5E1Fa956C56CD99c8eb4b8ecf703467f7120131A
Token model (token_type) utility (payments)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Tier‑1: the token is used to pay for queries (consume data); supply parameters are not established.
Governance —
Admins/keys —
Audit — (audit in progress; reports not published)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) blockchain indexing + query answering
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 2 / token_score 2 / evidence_score 2
Last verified 2026-02-11

General project overview

In the Tier‑1 documentation, Datai Network (DATAI) describes a peer‑to‑peer network that indexes various blockchains and answers external queries. The model includes the roles of indexer/gateway nodes and developers of “projections”. No Tier‑1 confirmation of an AI component was found — therefore DecAI Fit = 0/6 per the SSOT rule.

Features/modules

  • Projections: data sources/projections that nodes index.
  • Indexer / Gateway nodes: indexing and serving data on request.
  • API endpoints: for example, returning active positions (GET /activePositions).

Typical scenarios

  • Scenario 1: a data consumer makes a request to an endpoint → receives a data structure (for example, the user’s active DeFi positions).
  • Scenario 2: a developer writes a projection → deploys/uses it in the network (per the documentation).
  • Scenario 3: an operator deploys an indexer/gateway node (described as “soon”, details depend on the documentation sections).

Getting started (wallet/network)

  • What you need: access to the documentation and (for queries) a user EVM address.
  • Network/chain: the network indexes various blockchains; its own network/onchain component is not established in this card.
  • Fees: Tier‑1: “consume data” is paid for with DATAI tokens; additionally, Ethereum Sepolia fees apply to the contract’s onchain operations.

Architecture/tech (non‑AI)

  • Components: indexer nodes, gateway nodes, projections, API endpoints.
  • Participant roles: data consumers, node operators, projection developers.
  • Where logic runs: indexing and serving data — offchain (P2P network); the onchain part — the network’s smart contracts (token/staking/registries/dispute/consumer/reward) on the Ethereum Sepolia testnet.
  • Dependencies: the target blockchains that are indexed (see the project documentation).

Token/economics (expanded, no forecasts)

  • Token utility: Tier‑1: payment for queries (consume data) with Datai tokens.
  • Protocol necessity drivers: the token is needed as a mechanism of payment for queries (per Tier‑1).
  • Who pays fees: data consumers (per Tier‑1).
  • Where fees go: — (not established).
  • Issuance/burn: — (not established).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: — (not established).
  • Treasury: — (not established).

Governance

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

Security and incidents

  • Audits: Tier‑1 states that the audit of the contracts is underway, reports will be published later.
  • Bug bounty: —.
  • Incidents: — (not found).
  • Threat model: the network and key contracts are published (Sepolia testnet), but public audit reports based on the audit results have not yet been published.

Project status and timeline

  • Current status: active (there is documentation and endpoints).
  • Key releases/milestones: there are release notes (see links_*).
  • 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? No Tier‑1 confirmation of an AI component was found.
  • What is truly onchain? Tier‑1: contract addresses are published (Sepolia testnet), including the DATAI token, staking and registry/dispute/reward/consumer contracts.
  • Why is a token needed? Tier‑1: DATAI is used to pay for queries and for staking/disputes/rewards to network participants.
  • Red flags (based on the information found): AI‑washing (if the project is marketed somewhere as AI, but Tier‑1 confirmation is absent); a lack of Tier‑1 details on onchain/payment contracts.

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 medium 2
Token necessity medium 2
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 declaration of AI intent was found.
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): The documentation describes a data indexing/query network without an AI roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI features are not described in Tier‑1.
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): There is no description of an AI module/model.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No demo of an AI component was found (an AI component is not established).
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): 1 requires a demo surface of the AI component.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): AI metrics are not applicable (an AI component is not established).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): No tech description of an AI component was found (an AI component is not established).
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): The documentation describes the indexing network/endpoints.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (Sepolia testnet)
  • Addresses/identifiers: DataiToken: 0x5E1Fa956C56CD99c8eb4b8ecf703467f7120131A; Staking: 0x02fB3504e096285fbC82b6e8105bF62f4121f0F1; NodeRegistry: 0xc20EEA506642e8527De6BD20fe91a1d9aEA84887; ProjectionRegistry: 0x2a96F6A4FbF70F0012184b234D7B9078B09BA2C9; Dispute: 0xa5cDAa8ff8837Be9AaBb5D3Fbf29735662d9B626; Rewarder: 0x393486e61A6F97CD2092Ea3806fe2Db06B9B2892.
  • Evidence: Tier‑1 — https://datai.network/docs/contracts/deployed-contracts/
  • Why sufficient / why not (one line): Tier‑1 publishes the addresses of the key contracts on the network (Sepolia testnet).
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: staking/registries/dispute/reward/consumer deposits as part of the onchain coordination of network participants (per the Tier‑1 contract documentation).
  • Evidence: Tier‑1 — https://datai.network/docs/contracts/token-functionality ; https://datai.network/docs/contracts/deployed-contracts/
  • Why sufficient / why not (one line): Tier‑1 describes onchain functions other than “the token exists”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not applicable (an onchain component is not established).
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): Without a confirmed onchain core we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The DATAI token is mentioned in Tier‑1.
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): In the documentation overview the project is called “Datai Network (DATAI)” and payment with tokens is mentioned.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): “Consume data” is paid for with Datai tokens.
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): The Tier‑1 overview explicitly mentions payment for queries with tokens.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Tier‑1 describes staking DATAI for nodes/projections, stakes in disputes and the distribution of rewards to participants.
  • Evidence: Tier‑1 — https://datai.network/docs/contracts/token-functionality
  • Why sufficient / why not (one line): There is an explicit Tier‑1 description of staking/disputes/rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A governance role of the token is not established in Tier‑1.
  • Evidence: Tier‑1 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): There is no description of voting/governance.
  • 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 — https://docs.datai-network.org/
  • Why sufficient / why not (one line): TK_4=1 requires a separate justification of replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.datai-network.org/ Tier‑1: description of Datai Network (blockchain indexing, node roles, payment for queries with tokens).
Tier‑1 https://docs.datai-network.org/data-consumers/endpoints Tier‑1: an example API endpoint (GET /activePositions) and the parameter format (ethereum address).
Tier‑1 https://github.com/Datai-Network/datai-projections-sdk Tier‑1: the SDK repository (a development artifact for projections).
Tier‑1 https://datai.network/docs/release-notes/release-0-0-1 Tier‑1: release notes (the project’s life cycle).
Tier‑1 https://datai.network/docs/contracts/audit/ Tier‑1: the audit of the contracts is “in progress”, reports will be published.
Tier‑1 https://datai.network/docs/contracts/deployed-contracts/ Tier‑1: the network’s contract addresses (Sepolia testnet), including the DATAI token and staking/registry/dispute/reward.
Tier‑1 https://datai.network/docs/contracts/token-functionality Tier‑1: DATAI utility (payments, staking, disputes, rewards; governance — potentially in the future).
Tier‑1 — No Tier‑1 source for claim “the project’s AI component” was found.

No comments to display

Back to top