Skip to main content

Datum

Datum (DAT) — 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).

Datum — an infrastructure project for storing/exchanging data using blockchain infrastructure; token (symbol: DAT).

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: infrastructure and an SDK for storing data and managing access to it (positioned as “Blockchain Data Storage and Monetization”).
  • Who it’s for: for dApp developers, product teams and end users (mobile app/ID).
  • Why onchain/token: the DAT token is used as a means of payment for storage/access and as incentives for network participants.

How it works (very briefly)

  1. The user/application does: stores data via the SDK or uses Datum App/ID.
  2. The system does: stores data/metadata and manages access based on the project’s blockchain infrastructure.
  3. The user gets: controlled access/sharing of data and the ability to interact with dApps via identity.
  4. Where the blockchain is: record‑keeping and management of data access/exchange are positioned as running on the “Datum blockchain”.
  5. Token role: DAT is used to pay for storage/access and for rewards to participants/nodes (per the project’s claim).

Quick links: AI thesis fit

Project passport

Field Value
Project name Datum
Also known as (aliases) DAT, Datum Network
Logo (logo) ../assets/681_datum_logo.svg
Token symbol (ticker) DAT
Category Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0x81c9151de0c8bafcd325a57e3db5a5df1cebf79c
Token model (token_type) utility (payments + staking + rewards)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) DAT is used to pay for storage/access and for rewards to network participants (per the project’s claim).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) data storage + access management
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 2 / 1
Last verified 2026-02-11

General project overview

Per Tier‑1 sources, the project is positioned as “Blockchain Data Storage and Monetization” infrastructure with an SDK for developers and a mobile app/ID for users. The claimed focus is on data storage, access control and data exchange using blockchain infrastructure.

Features/modules

  • An SDK (datum-sdk) for working with data.
  • Datum App / Datum ID (per the project’s claim).
  • Payment/incentive mechanics with the DAT token for storage/access/rewards.

Typical scenarios

  • Scenario 1: a developer connects the SDK → stores/reads user data via the API → gets identifiers/operation results.
  • Scenario 2: a user manages what to share → receives rewards (per the project’s claim).

Getting started (wallet/network)

  • What you need: for developers — access to the SDK and documentation; for users — the app/an account (per the project’s claim).
  • Network/chain: Ethereum (the ERC‑20 DAT token); the project also claims its own network/explorer.
  • Fees: not established per Tier‑1 (see Evidence).

Architecture/tech (non‑AI)

  • Components: SDK/client applications; a blockchain layer for record‑keeping/access management (per the project’s claim).
  • Participant roles: users, developers, nodes/masternodes (per the project’s claim).
  • Where logic runs: part of the logic is claimed as onchain (“Datum blockchain”), the client part — in the apps/SDK.
  • Dependencies: not established per Tier‑1.

Token/economics (expanded, no forecasts)

  • Token utility: payment for data storage/access and incentives for network participants (per the project’s claim).
  • Protocol necessity drivers: DAT is claimed as the “fuel” of data exchange/storage resources.
  • Who pays fees: product teams and developers (per the project’s claim).
  • Where fees go: to nodes/participants (per the project’s claim); distribution details are not established per Tier‑1.
  • Issuance/burn: not established per Tier‑1.
  • Security/incentive mechanisms: masternodes/rewards are mentioned; details are not established per Tier‑1.
  • Distribution and token issuance schedule: not established per Tier‑1.
  • Treasury: not established per Tier‑1.

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: not established per Tier‑1.
  • Where decisions are discussed/made: not established per Tier‑1.
  • Keys/multisig: not established per Tier‑1.

Security and incidents

  • Audits: not found per Tier‑1.
  • Bug bounty: not found per Tier‑1.
  • Incidents: not established per Tier‑1.
  • Threat model: not established per Tier‑1.

Project status and timeline

  • Current status: not established per Tier‑1.
  • Key releases/milestones: not established per Tier‑1.
  • Roadmap: No Tier‑1 roadmap found (see Evidence).

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? Per Tier‑1 sources, no confirmation of an AI component or an AI roadmap (AI intent) for the product/protocol was found.
  • What is truly onchain? The project positions data storage/exchange as using blockchain infrastructure; there is also the ERC‑20 DAT token on Ethereum.
  • Why is a token needed? Per the project’s claim, DAT is used to pay for storage/access and for rewards to network participants.
  • Red flags (based on the information found): Tier‑1 artifacts for the AI part are absent; key tokenomics/governance parameters are not established per Tier‑1; double‑check the current state of the “Datum blockchain” and the status of the network.

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 partial 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 AI roadmap/declaration of AI intentions for the product was found.
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): no explicit AI roadmap/AI intent was found on the project’s Tier‑1 page.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No Tier‑1 confirmation that the product contains a working AI component was found.
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): “AI” as a working component is not established per Tier‑1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No demo of the AI component itself was found per Tier‑1.
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): there is no subject of verification (an AI component is not established).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found (an AI component is not established).
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): AI quality metrics are absent in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): No Tier‑1 tech description of an AI component was found (the AI component is not established).
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): per Tier‑1 there is no AI architecture/model versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 DAT: 0x81c9151de0c8bafcd325a57e3db5a5df1cebf79c
  • Evidence: Tier‑1 — https://etherscan.io/token/0x81c9151de0c8bafcd325a57e3db5a5df1cebf79c
  • Why sufficient / why not (one line): there is a Tier‑1 onchain artifact (the token contract in the explorer).
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the project positions data storage/exchange and access management as using the blockchain (“Datum blockchain”).
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): The Tier‑1 description points to blockchain logic that does not boil down to the token alone.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification was found that the product breaks down without the blockchain.
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): onchain criticality is not established per the operational test.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, DAT (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x81c9151de0c8bafcd325a57e3db5a5df1cebf79c
  • Why sufficient / why not (one line): the existence of the token is confirmed by the onchain explorer.
  • 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): Developers/product teams pay DAT for data storage (per the project’s claim).
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): The Tier‑1 “Powered by the DAT Token” section describes payment in DAT for storage.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Participants/masternodes and users receive DAT as a reward (per the project’s claim).
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): The Tier‑1 description states “Masternodes earn DAT…” and “users earn DAT…”.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation that DAT is used for governance was found.
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): no Tier‑1 description of the token’s governance mechanics was found.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token (for example, with a subscription/stablecoin) is not established per Tier‑1.
  • Evidence: Tier‑1 — https://datum.org/
  • Why sufficient / why not (one line): there is no Tier‑1 “replaceable/irreplaceable” argument in terms of protocol necessity.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://datum.org/ Product description: data storage/monetization; the role of the DAT token (storage/sharing/storing/accessing).
Tier‑1 https://app.datum.org/ Tier‑1: app/demo surface (Datum app).
Tier‑1 https://gettingstarted.datum.org/docs/introduction.html The existence of developer docs/positioning of the SDK.
Tier‑1 https://github.com/Datum/datum-sdk/blob/master/docs/example.md An example of SDK usage (developer artifact).
Tier‑1 https://etherscan.io/token/0x81c9151de0c8bafcd325a57e3db5a5df1cebf79c Onchain artifact: the ERC‑20 DAT token contract.
Tier‑1 — No Tier‑1 source for claim “the product has an AI component” was found.
Tier‑1 — No Tier‑1 source for claim “onchain is critical (OC_3)” was found.

No comments to display

Back to top