Skip to main content

DataHighway

DataHighway — 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).

DataHighway — an Infra project (claimed: Kusama parachain), token (symbol: DHX).

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 decentralized organization that claims IoT data NFT collection/trading and a data market (per the description on the website).
  • Who it’s for: IoT data providers and data consumers; DAO participants.
  • Why onchain/token: per the Tier‑1 project description, DHX is used to trade IoT Data NFTs/F‑NFTs in the Inter‑Chain Data Marketplace; DHX mining and the dependence of mining rewards on participation/staking (delegator/collator) are also described.

How it works (very briefly)

  1. The user does: publishes/sells or buys IoT data (including in the Data NFTs/F‑NFTs format — per the project description).
  2. The system does: keeps records of operations and rules (claimed: onchain infrastructure/parachain).
  3. The user gets: access to data or the result of a transaction.
  4. Where the blockchain is: the project claims to be building IoT‑oriented parachain infrastructure/marketplace; the verifiable onchain artifact is the DHX token contract (BEP‑20) in the explorer.
  5. Token role (if any): per the Tier‑1 project description, DHX is used as a token for trading IoT data (Data NFTs/F‑NFTs) and participates in mining mechanics (including boosts for staking).

Quick links: AI thesis fit

Project passport

Field Value
Project name DataHighway
Also known as (aliases) DHX
Logo (logo) ../assets/715_datahighway_logo.svg
Token symbol (ticker) DHX
Category Infra
Primary chain (chain) Kusama
Type Appchain
Network status —
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) —
Token (standard) BEP-20
Token contract 0x11d9f5d36ba3996962142c1c32467acebb697009
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) IoT data marketplace
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

DataHighway describes itself as a decentralized organization/project around IoT data collection and trading and a data market, as well as a parachain project in the Polkadot/Kusama ecosystem. An AI component is not identified per Tier‑1 sources. Verifiable onchain artifact: the DHX token contract (BEP‑20) in the explorer.

Features/modules

  • IoT data NFTs / F‑NFTs: a claimed data/asset format.
  • DAO: a claimed participation/voting model.

Typical scenarios

  • Scenario 1: a provider publishes data → the data becomes available for purchase/subscription (details not established).
  • Scenario 2: a participant holds/stakes the token → interacts with the ecosystem (details not established).

Getting started (wallet/network)

  • What you need: a wallet for BNB Smart Chain (for the DHX token) and access to the project’s products (not established).
  • Network/chain: BNB Smart Chain (for the DHX token).
  • Fees: BNB Smart Chain network fees for token transactions.

Architecture/tech (non‑AI)

  • Components: the DHX token contract (BEP‑20), project repositories (if applicable), clients/wallets.
  • Participant roles: data providers, data buyers, DAO participants, token holders.
  • Where logic runs: product logic is not established; the token — onchain (BSC).
  • Dependencies: BNB Smart Chain infrastructure for the token.

Token/economics (expanded, no forecasts)

  • Token utility: per the Tier‑1 project description, DHX is used to trade IoT Data NFTs/F‑NFTs in the Inter‑Chain Data Marketplace; DHX mining and boosts/rewards for participation and staking (delegator/collator) are also described.
  • Protocol necessity drivers: —.
  • Who pays fees: users of the BNB Smart Chain network for token transactions.
  • Where fees go: to BNB Smart Chain validators (at the network level).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: DAO is claimed, details are not established.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: No Tier‑1 audit report(s) found.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: standard risks of the token contract and EVM infrastructure.

Project status and timeline

  • Current status: not established.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? An AI component is not identified per Tier‑1 sources.
  • What is truly onchain? The DHX token contract (BEP‑20) and operations with it (Tier‑1: explorer).
  • Why is a token needed? Per the Tier‑1 project description, DHX is used to trade IoT Data NFTs/F‑NFTs; DHX mining and boosts/rewards for staking (delegator/collator) are also described.
  • Red flags (based on the information found): Tier‑1 proof of an AI component is absent; onchain logic of the marketplace/parachain is claimed, but requires verification through specific onchain artifacts of the network (not just the token).

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 partially present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 AI intentions are not identified.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable Tier‑1 claim about AI plans.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): What exactly the AI component does is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable description of an AI feature per Tier‑1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Demos/examples of the AI component in operation are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable product demo in links_*.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

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

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the AI part is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 documentation with model architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: BEP‑20 contract: 0x11d9f5d36ba3996962142c1c32467acebb697009
  • Evidence: Tier‑1 — https://bscscan.com/token/0x11d9f5d36BA3996962142c1c32467AcEBb697009
  • Why sufficient / why not (one line): The onchain artifact (the token contract) is available 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: parachain features are claimed (inter‑chain data market, DAO governance, roaming agreements) and Substrate node/pallet code is published (POC/prototype).
  • Evidence: Tier‑1 — https://www.datahighway.com/ ; https://github.com/DataHighway-DHX/DataHighway-Parachain
  • Why sufficient / why not (one line): The Tier‑1 website and official repository describe/show onchain logic of the product, not just token issuance.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

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

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, DHX (BEP‑20).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x11d9f5d36BA3996962142c1c32467AcEBb697009
  • Why sufficient / why not (one line): The token contract is available onchain.
  • 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): DHX is described as a token with which IoT data (Data NFTs/F‑NFTs) is “traded” in the Inter‑Chain Data Marketplace.
  • Evidence: Tier‑1 — https://www.datahighway.com/
  • Why sufficient / why not (one line): The Tier‑1 website explicitly describes that IoT data will be traded using DHX tokens.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): DHX mining and increased rewards/boosts for staking DHX as a delegator or collator are described.
  • Evidence: Tier‑1 — https://www.datahighway.com/
  • Why sufficient / why not (one line): The Tier‑1 website describes the link between participation/staking and mining rewards (incentive mechanics).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): It is not established that the token is used for governance.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics with the token.
  • 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 data to justify replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.datahighway.com/ Project description (IoT data market, claimed infrastructure).
Tier‑1 https://github.com/DataHighway-DHX/DataHighway-Parachain Public Substrate code of the parachain node; claimed areas (data market, DAO governance, roaming hub).
Tier‑1 https://bscscan.com/token/0x11d9f5d36BA3996962142c1c32467AcEBb697009 The DHX token contract (onchain fact).
Tier‑1 — No Tier‑1 source for claim “the project has an AI component” was found.
Tier‑3 https://coinmarketcap.com/currencies/datahighway/ Token profile (for reference; not proof of technology).

No comments to display

Back to top