Skip to main content

Data Universe (SN13)

Data Universe (SN13) — 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).

Data Universe (Subnet 13) — an AI/Data | Infra project on the Bittensor network, token (symbol: —).

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: Bittensor Subnet 13 “Data Universe” — a decentralized layer for collecting/distributing fresh data (including social media) via miners/validators.
  • Who it’s for: subnet participants (miners/validators) and users/businesses/other subnets who need fresh datasets and an API.
  • Why onchain/token: onchain is needed for the subnet mechanics (accounting/incentives/data validation within the Bittensor network); a separate necessity of a “project token” is not established in this card.
  • What you can actually touch (Tier‑1): the Gravity web application (creating data‑collection tasks) and the documentation/guide for Subnet 13.

How it works (very briefly)

  1. The user does: launches data‑scraping tasks via Gravity or integrates via the API.
  2. Miners do: collect data from the supported sources and store it locally/in storage (depending on the mode).
  3. Validators do: periodically index/verify the miners’ data and reward “valuable data” per the subnet mechanics.
  4. Where the blockchain is: participation and incentives are implemented via the Bittensor network (Subnet 13); the observable dynamics — via the subnet dashboards.
  5. Token role (if any): the existence of a separate project token is not confirmed by Tier‑1 in this card; the economic role is described as the subnet’s incentive mechanism.

Quick links: AI thesis fit

Project passport

Field Value
Project name Data Universe (SN13)
Also known as (aliases) Subnet 13; Data Universe
Logo (logo) ../assets/480_data-universe_logo.jpg
Token symbol (ticker) —
Category AI/Data | Infra
Primary chain (chain) Bittensor
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) —
Token contract —
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The subnet’s incentive mechanism rewards “valuable data”; a separate project token is not established per Tier‑1.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) Macrocosmos (the subnet is “owned by Macrocosmos.ai” — per the Tier‑1 GitHub README/docs).
Funding (investors/funding) —
AI component (ai_component) data collection + sentiment analysis + agentic assistant (in products)
Use‑case (use_case) fresh datasets for ML/analytics/inference
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 0 / evidence_score 0
Last verified 2026-02-11

General project overview

Data Universe (Subnet 13) is described in the Tier‑1 documentation as the “decentralized data layer” of Bittensor: miners collect and store data, validators index/verify and reward, and users get access to the data/tasks via the products and the API. The project’s materials explicitly highlight the mechanics of rewarding fresh and “desirable” data, as well as the “miners store — validators query — rewards” architecture.

Features/modules

  • Data collection/storage (Tier‑1): miners scrape data from the sources and store it as DataEntities, grouped into DataEntityBuckets.
  • Indexing/verification/rewards (Tier‑1): validators collect MinerIndexes and reward by value/credibility.
  • Products (Tier‑1): Gravity (no‑code task launch), Mission Commander (an LLM assistant inside Gravity), Nebula (visualization and sentiment).

Typical scenarios

  • Scenario 1: a user creates a scraping task via Gravity → gets a structured dataset/results.
  • Scenario 2: a miner sets up data collection and storage → receives rewards within the incentive mechanism.
  • Scenario 3: a validator verifies the correctness/usefulness of the data → affects the miners’ rewards.

Getting started (wallet/network)

  • What you need: you can start with the Subnet 13 documentation and the Gravity app (see links_*); to participate as a miner/validator — a Bittensor environment (not described in this card).
  • Network/chain: Bittensor (Subnet 13).
  • Fees: depend on participation in the Bittensor network and the infrastructure (not calculated in this card).

Architecture/tech (non‑AI)

  • Components: miners (scraping + storage), validators (indexing/verification/queries), products (Gravity/Nebula) and the API.
  • Participant roles: miners, validators, users/integrators.
  • Where logic runs: data collection and processing — offchain at the participants; incentives/accounting — within the Bittensor network.
  • Dependencies: external data sources (X/Reddit/YouTube, etc.), storage infrastructure (S3‑compatible storage is mentioned), Bittensor infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: the focus of the Tier‑1 sources is the subnet’s incentive mechanism (rewards for useful data); a separate “project token” model is not recorded per Tier‑1.
  • Protocol necessity drivers: the reward mechanics are based on the volume/value of data and credibility; a detailed “token necessity” per the TK flags is not confirmed by Tier‑1.
  • Who pays fees / where fees go: not established per Tier‑1 (in this card).
  • Issuance/burn: not established per Tier‑1 (in this card).
  • Security/incentive mechanisms: credibility checks and penalization for misrepresenting the MinerIndex are described (Tier‑1 README).
  • Distribution and token issuance schedule: not established per Tier‑1 (in this card).
  • Treasury: not established per Tier‑1 (in this card).

Governance

  • Who makes decisions: Macrocosmos/contributors (at a minimum — via the public repositories and documentation; a formal governance model is not extracted per Tier‑1 in this card).
  • How protocol parameters change: via changes to the code/documentation and subnet updates (see GitHub/Docs).
  • Where decisions are discussed/made: GitHub and Discord/Telegram (see links_*).
  • Keys/multisig: not established per Tier‑1 (in this card).

Security and incidents

  • Audits: not established per Tier‑1 (in this card).
  • Bug bounty: not established per Tier‑1 (in this card).
  • Incidents: not established per Tier‑1 (in this card).
  • Threat model: data compliance risks (a Miner Data Compliance Policy is mentioned) and the quality/reliability of the collected data.

Project status and timeline

  • Current status: mainnet (subnet 13 on the Bittensor network; see Explorer).
  • Key releases/milestones: the reference point is the commit history in the repository (see links_*).
  • Roadmap: there are publications/materials (Substack; see links_*), but the roadmap details are not summarized in this card.

Ecosystem/integrations

  • Integrations: the Gravity app + API; an MCP for integration with Claude/Cursor is mentioned (Tier‑1 GitHub README).
  • Partners: the documentation mentions use cases by other subnets (as context); no separate verification of partners was performed in this card.
  • Where it’s actually used: examples of use cases are listed in the Tier‑1 README/Docs (semantic use of data, sentiment, etc.).

AI component of the project

  • What is real AI here? the project’s materials claim sentiment analysis and an agentic LLM assistant (Mission Commander) as part of the products (Tier‑1 GitHub README/Docs).
  • What is truly onchain? the subnet’s incentive mechanism and the participation of miners/validators within the Bittensor network.
  • Why is a token needed? the necessity of a “separate project token” is not established; the economic mechanics are described at the subnet level.
  • Red flags (based on the information found): conflating the “project token” (from aggregators) with the real protocol incentives of the subnet without Tier‑1 confirmation; what to double‑check: whether there is a separate token and why it is needed.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
Token necessity low 0
Evidence Tier‑1 present 0
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 sources describe a working product and the subnet mechanics (AI_1/AI_2/AI_4), so “intent without evidence” does not apply.
  • Evidence: Tier‑1 — https://docs.macrocosmos.ai/subnets/subnet-13-data-universe ; https://github.com/macrocosm-os/data-universe/blob/main/README.md
  • Why sufficient / why not (one line): There is a description of the current implementation/interfaces, not only a plan.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The project’s products/materials claim sentiment analysis and an agentic assistant (Mission Commander) for choosing terms/phrases for scraping tasks.
  • Evidence: Tier‑1 — https://github.com/macrocosm-os/data-universe/blob/main/README.md ; https://docs.macrocosmos.ai/subnets/subnet-13-data-universe
  • Why sufficient / why not (one line): Tier‑1 sources describe AI functions as part of the product (sentiment/LLM assistant).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is an accessible Gravity user interface for launching scraping tasks and obtaining datasets.
  • Evidence: Tier‑1 — https://app.macrocosmos.ai/gravity ; https://docs.macrocosmos.ai/subnets/subnet-13-data-universe
  • Why sufficient / why not (one line): This is a reproducible “demo surface” (what you can touch) and is consistent with links_*/TL;DR/Evidence.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/macrocosm-os/data-universe/blob/main/README.md
  • Why sufficient / why not (one line): No specific reproducible quality metrics/benchmarks of the AI part (sentiment/LLM) with versions/dates were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is a Tier‑1 repository with code/structure and documentation on the subnet (miner/validator, incentive mechanism, terms).
  • Evidence: Tier‑1 — https://github.com/macrocosm-os/data-universe ; https://github.com/macrocosm-os/data-universe/blob/main/README.md
  • Why sufficient / why not (one line): The public code and docs provide technical context for verifying the mechanics.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Bittensor (Subnet 13)
  • Addresses/identifiers: Subnet 13 (SN13)
  • Evidence: Tier‑1 — https://docs.macrocosmos.ai/subnets/subnet-13-data-universe
  • Why sufficient / why not (one line): The Tier‑1 documentation directly identifies the subnet and its role.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the role of miners/validators, indexing/verification of data and rewards per the incentive mechanism within the subnet.
  • Evidence: Tier‑1 — https://github.com/macrocosm-os/data-universe/blob/main/README.md ; https://docs.macrocosmos.ai/subnets/subnet-13-data-universe
  • Why sufficient / why not (one line): The protocol logic of the subnet and the incentives are described, not “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the Bittensor network, the incentive mechanism and the verifiable participation/rewards of miners/validators break down.
  • Evidence: Tier‑1 — https://github.com/macrocosm-os/data-universe/blob/main/README.md
  • Why sufficient / why not (one line): The subnet model relies on the network protocol for incentives and validation.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): Per Tier‑1, neither the fact “the project has no token” nor “a separate project token exists” was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): We set TK_0=1 only with explicit proof of the absence of a token; here the data are insufficient.
  • 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): Not established: mandatory payment with a separate project token for the Gravity/API service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires an explicit Tier‑1 pay‑for‑service mechanism.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Not established: collateral/penalties/incentives in terms of a separate project token (as distinct from the subnet incentives in the network).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires a specific token mechanism and a Tier‑1 source.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via a separate project token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires an explicit governance mechanism and a source.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token has not been assessed (there is no Tier‑1 role of a separate project token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Data on the token’s role in the protocol are needed to discuss replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.macrocosmos.ai/subnets/subnet-13-data-universe Tier‑1 description of Subnet 13: purpose, architecture, why “fresh data”, links to the interfaces.
Tier‑1 https://github.com/macrocosm-os/data-universe/blob/main/README.md Tier‑1 description of the mechanics: miners/validators, miner index, incentive mechanism, the Gravity/Nebula/MCP products.
Tier‑1 https://app.macrocosmos.ai/gravity What you can touch: the UI for launching scraping tasks (AI_2 sync).
Tier‑1 — No Tier‑1 source for claim “a separate project token is mandatory for pay‑for‑service / collateral / governance” was found.
Tier‑2 https://taostats.io/subnets/13/chart Context: observable dynamics of Subnet 13 (dashboard aggregator).
Tier‑2 https://www.coingecko.com/en/coins/data-universe Reference profile (context).
Tier‑2 https://coinmarketcap.com/currencies/data-universe/ Reference profile (context).

No comments to display

Back to top