Skip to main content

DIA

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

DIA — an Infra project: oracle infrastructure (price feeds, randomness and more) with the modular Lumina stack (feeders → Lasernet L2 → Spectra cross‑chain). Token: DIA (ERC‑20, Ethereum; used for staking/security of Lumina).

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 oracle stack that collects market data and delivers it to smart contracts (push/pull), plus additional products such as verifiable randomness.
  • Who it’s for: developers of dApps/protocols who need onchain feeds (DeFi, GameFi, RWA and others).
  • Why onchain/token: data and computations are recorded in onchain components (Lasernet/contracts); the DIA token is used as the staking layer securing Lumina.

How it works (very briefly)

  1. The user does: embeds feed reading (push/pull/getValue) into a smart contract following the guide.
  2. The system does: independent feeder nodes collect data and write it to onchain contracts (Pods) on Lasernet; aggregators form the final value.
  3. The user gets: an onchain value (e.g. an asset price) in a standardized interface.
  4. Where the blockchain is: storage/aggregation/delivery happen via Lasernet onchain contracts and Spectra cross‑chain messaging.
  5. Token role: DIA is used as the staking layer that provides economic security (per the Lumina staking description).

Quick links: AI thesis fit

Project passport

Field Value
Project name DIA
Also known as (aliases) DIA Oracles | DIA Lumina | Lasernet
Logo (logo) ../assets/65_dia_logo.svg
Token symbol (ticker) DIA
Category Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2019
Project status (status) active
Token (standard) ERC-20
Token contract 0x84ca8bc7997272c7cfb4d0cd3d55cd942b3c9419
Token model (token_type) utility (staking + governance)
Max supply 200,000,000
Issuance fixed
Tokenomics (tokenomics, brief) Max total supply 200M (Etherscan).
Governance DAO
Admins/keys —
Audit yes
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) on-chain price feeds + randomness oracles
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 3 / token_score 1 / evidence_score 2
Last verified 2026-02-10

General project overview

DIA is oracle infrastructure for delivering data to smart contracts. According to the DIA Lumina documentation, it is a modular stack where feeders (independent nodes) collect data directly from sources (CEX/DEX and others), write it to onchain contracts (Pods) on Lasernet (an optimistic Ethereum L2 rollup), after which the Aggregator forms the final values and Spectra delivers the data to target networks (push/pull models).

The project is aimed at dApp developers: the documentation has how‑tos for obtaining price data (several methods) and describes the stack components (feeders/lasernet/spectra), as well as the staking layer, where the DIA token serves as the economic basis for the security of updates.

Features/modules

  • Token Price Feeds: push/pull oracles and standard reading interfaces (Tier‑1 docs).
  • Lumina stack: feeders → pods → aggregators on Lasernet (Tier‑1 docs).
  • Spectra: cross‑chain delivery via Hyperlane‑based messaging (Tier‑1 docs).
  • Staking: staking of DIA as a security layer (Tier‑1 docs).
  • Additional products: verifiable randomness (xRandom) and others (Tier‑1 docs home).

Typical scenarios

  • Scenario 1 (DeFi): a protocol reads an asset price from the DIA oracle → uses it to calculate collateral/liq.
  • Scenario 2 (GameFi): a contract receives verifiable randomness (xRandom) → uses it for randomization.
  • Scenario 3 (RWA): a dApp uses RWA feeds (stocks/FX/etc.) → builds synthetics/indices.

Getting started (wallet/network)

  • What you need: choose the target network and the integration method (push/pull/getValue) following the documentation.
  • Network/chain: the oracle products operate on multiple networks; the DIA token — ERC‑20 on Ethereum; staking — on Lasernet mainnet (Tier‑1 staking docs).
  • Fees: gas on the target network for reading/processing, and fees for the pull/push models (described in the Spectra docs).

Architecture/tech (non‑AI)

  • Components: feeder nodes (scrapers/collector/processor), Pods (key‑value oracle contracts), Aggregator (meta‑contract), Lasernet (optimistic L2 rollup), Spectra (message passing) (Tier‑1 docs).
  • Participant roles: feeders collect/write data; aggregator admins configure threshold/timeout and the list of Pods; consumers read values in their contracts.
  • Where logic runs: data collection — offchain at the feeders; storage/aggregation/threshold/timeout — onchain in Pods/Aggregator on Lasernet; delivery to other networks — via Spectra.
  • Dependencies: Spectra uses Hyperlane‑compatible components (ISM/mailboxes), Lasernet is built on the Arbitrum Orbit Stack (Tier‑1 docs).

Token/economics (expanded, no forecasts)

  • Token utility: staking of DIA to secure oracle operations (security layer); the wDIA wrapper for staking (Tier‑1 staking docs).
  • Protocol necessity drivers: staking is described as the Lumina security layer; without staking, the cryptoeconomic model of incentives/penalties for feeders collapses (Tier‑1).
  • Who pays fees: users pay gas on the networks; in the pull/push models there is a fee mechanism for message processing (Spectra docs).
  • Where fees go: the fee mechanism routes funds to the Spectra gas wallet via the ProtocolFeeHook (Tier‑1 spectra docs).
  • Issuance/burn: max total supply 200,000,000 (Tier‑1 Etherscan).
  • Security/incentive mechanisms: staking + planned penalties/slashing/delegation (described in the staking overview).
  • Distribution and token issuance schedule: — (not recorded in the reviewed Tier‑1 sources).
  • Treasury: —.

Governance

  • Who makes decisions: DIA DAO (there is an official Snapshot and Forum in the website’s ecosystem menu).
  • How protocol parameters change: — (a separate sampling of the specific governance processes/rules is needed).
  • Where decisions are discussed/made: forum + snapshot (links — in links_*/Evidence).
  • Keys/multisig: —.

Security and incidents

  • Audits: the docs list audits of the Lumina stack and staking (MixBytes) + the DIAToken audit (Chainsulting) on Etherscan.
  • Bug bounty: there is an official security bounty program.
  • Incidents: — (no Tier‑1 postmortems were found).
  • Threat model: the risk of compromise of feeders/data sources, errors in aggregation/threshold/timeout, cross‑chain messaging risks (Spectra/ISM), economic attacks on staking.

Project status and timeline

  • Current status: mainnet (the oracle stack and documentation are active; the token and staking are described as live).
  • Key releases/milestones: Lasernet mainnet and mainnet staking (mentioned in product posts/docs).
  • Roadmap: product updates are published in the Product section of the blog.

Ecosystem/integrations

  • Integrations: support for many blockchains; cross‑chain delivery via Spectra (Tier‑1 docs).
  • Partners: —.
  • Where it’s actually used: per the docs, “powers over 200 dApps” and a list of use‑cases (Tier‑1 docs home).

AI component of the project

  • What is real AI here? An AI component is not claimed as a mandatory part of the DIA Oracles product (within the Tier‑1 sources).
  • What is truly onchain? onchain oracles: Pods/Aggregators on Lasernet + delivery of updates to target networks (Tier‑1 docs).
  • Why is a token needed? DIA is used for staking as a security layer (Tier‑1 staking docs); it is also used in governance (DAO).
  • Red flags (based on the information found): AI‑washing — none; onchain‑washing — low (the architecture is explicitly onchain); token‑washing — low (the staking layer is described as part of security).

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): in the reviewed Tier‑1 sources, DIA is positioned as oracle infrastructure, without an AI roadmap as a core part.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/home
  • Why sufficient / why not (one line): there is no AI roadmap as a key part → AI_0=0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): an AI function as a product/protocol is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/home
  • Why sufficient / why not (one line): oracles/feeds/randomness are described, without an AI component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): the demo relates to oracle integration, not to AI.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/guides/how-to-guides/fetch-price-data
  • Why sufficient / why not (one line): there is no AI demo → AI_2=0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.diadata.org/docs/home
  • Why sufficient / why not (one line): AI metrics are absent, since an AI component is not confirmed.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): an AI architecture is not applicable; the architecture of the oracle stack is described.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/dia-stack/overview
  • Why sufficient / why not (one line): this is not an AI technical description → AI_4=0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (token) + Lasernet (oracle L2; Tier‑1 docs).
  • Addresses/identifiers: DIA ERC‑20 0x84ca8bc7997272c7cfb4d0cd3d55cd942b3c9419.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x84ca8bc7997272c7cfb4d0cd3d55cd942b3c9419 , https://www.diadata.org/docs/dia-stack/overview
  • Why sufficient / why not (one line): there are onchain identifiers and a description of the onchain layer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Pods (key‑value), Aggregators (median/threshold/timeout), cross‑chain delivery contracts (RequestOracle/PushOracleReceiver) (Tier‑1).
  • Evidence: Tier‑1 — https://www.diadata.org/docs/dia-stack/architecture/core-components/lasernet/overview , https://www.diadata.org/docs/dia-stack/architecture/core-components/spectra
  • Why sufficient / why not (one line): onchain contracts and their functions are described (not only the token).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain storage/aggregation/delivery, a trustless oracle feed for smart contracts is not achievable.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/dia-stack/overview
  • Why sufficient / why not (one line): the stack is explicitly positioned as onchain processing/settlement for oracles.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the DIA token exists (ERC‑20, Ethereum).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x84ca8bc7997272c7cfb4d0cd3d55cd942b3c9419
  • Why sufficient / why not (one line): the onchain fact of the token is confirmed.
  • 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): direct “pay‑in‑DIA” access/subscription as a mandatory mechanism is not recorded in Tier‑1.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/home
  • Why sufficient / why not (one line): the utility is confirmed via staking, not as a paywall.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): staking of DIA is the security layer: stakers/feeders lock DIA, rewards/penalties are provided for, with an evolution toward slashing/delegation.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/guides/general-guides/dia-staking
  • Why sufficient / why not (one line): the Tier‑1 staking docs directly describe the token’s role in security.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is likely (DAO/snapshot), but the Tier‑1 rules/processes of the token‑governance mechanics are not recorded as a formal standard.
  • Evidence: Tier‑1 — https://diadata.org/dao/governance ; https://vote.diadata.org/#/ ; https://forum.diadata.org/
  • Why sufficient / why not (one line): Tier‑1 records the channels (portal + forum + voting) but does not record a single formal governance process “as a protocol standard” → we keep 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): DIA is built into the security layer of Lumina staking, so “a token just for show” is not confirmed.
  • Evidence: Tier‑1 — https://www.diadata.org/docs/guides/general-guides/dia-staking
  • Why sufficient / why not (one line): if the token is used for the security layer, it is functionally not “replaceable without loss” in the current design.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.diadata.org/docs/home that the project is an oracle stack (feeds/randomness), for devs, product overview.
Tier‑1 https://www.diadata.org/docs/dia-stack/overview the architecture of the Lumina/Lasernet stack, onchain computation/settlement.
Tier‑1 https://www.diadata.org/docs/dia-stack/architecture/core-components/feeders how feeders collect data and write it to Pods on Lasernet.
Tier‑1 https://www.diadata.org/docs/dia-stack/architecture/core-components/lasernet/overview Pods/Aggregator, threshold/timeout, onchain aggregation and the getValue() interface.
Tier‑1 https://www.diadata.org/docs/dia-stack/architecture/core-components/spectra cross‑chain delivery (push/pull), the fee mechanism, Hyperlane/ISM.
Tier‑1 https://www.diadata.org/docs/guides/how-to-guides/fetch-price-data how to integrate price feeds (push/pull/getValue).
Tier‑1 https://www.diadata.org/docs/guides/general-guides/dia-staking the DIA token as the staking security layer (rewards/penalties).
Tier‑1 https://etherscan.io/token/0x84ca8bc7997272c7cfb4d0cd3d55cd942b3c9419 the DIA token (ERC‑20), max supply 200M; token contract/audit.
Tier‑1 https://www.diadata.org/docs/guides/resources/audits the list of audits (Lumina stack / staking / DIAOracleV2).
Tier‑1 https://www.diadata.org/docs/guides/resources/security-bounty-program the bug bounty program.
Tier‑1 https://www.diadata.org/blog/post/2025-in-review-product-development/ product milestones (Lasernet mainnet, staking, audits) — status/timeline context.
Tier‑1 https://diadata.org/dao/governance governance portal: how to participate in the DIA DAO (navigation to the forum and voting).
Tier‑1 https://vote.diadata.org/#/ DAO voting: the Snapshot interface for DIA DAO votes.
Tier‑1 https://forum.diadata.org/ DAO forum: discussion/proposals and context for votes.

No comments to display

Back to top