Skip to main content

Gata

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

Gata — a project that describes itself as infrastructure for decentralized AI computation (compute), data (DataAgent), and applications (for example, GataGPT). The docs describe DGPU (Decentralized GPU Cloud) and a technical architecture with anchoring of data/proofs in BNB Greenfield; token: GATA (BEP‑20 on BNB Smart Chain).

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 platform that aggregates distributed compute resources (GPU/compute) and uses them for AI inference/data work; there is a DGPU Cloud product (beta).
  • Who it’s for: AI developers/teams who need GPUs and AI inference; network participants providing compute.
  • Why onchain/token: onchain is used for anchoring data and “proofs of contribution” in the decentralized BNB Greenfield storage (per the docs); the token exists, but its utility in the “GATA Token” docs is not yet disclosed (a “coming soon” page).
  • What you can actually touch (Tier‑1): DGPU beta (web) → https://decloud.gata.xyz/

How it works (very briefly)

  1. The user does: connects a wallet and uses DGPU Cloud for AI workloads (inference/model deployment) or participates as a compute provider.
  2. The system does: aggregates idle GPU/compute, performs AI computation on data, stores input/output data, and anchors confirmations/contributions in BNB Greenfield.
  3. The user gets: access to compute/inference and (potentially) accounting of the contribution.
  4. Where the blockchain is: BNB Greenfield as a decentralized storage chain for data and proofs; the GATA token — on BNB Smart Chain.
  5. Token role (if any): not confirmed in the Tier‑1 docs (the “GATA Token” page in the docs: coming soon).

Quick links: AI thesis fit

Project passport

Field Value
Project name Gata
Also known as (aliases) GATA, Aggregata (historical name in the GitHub repository)
Logo (logo) ../assets/293_gata_logo.svg
Token symbol (ticker) GATA
Category AI/Compute | AI/Data | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active (website/docs available; DGPU beta described)
Token (standard) BEP-20
Token contract 0x46Ee3BFC281d59009cCD06F1dD6aBDbfCd82FFC3
Token model (token_type) unknown
Max supply 1,000,000,000 GATA (BscScan Max Total Supply)
Issuance fixed max supply (per the explorer)
Tokenomics (tokenomics, brief) utility/distribution are not disclosed in the docs (a “coming soon” page)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) the DGPU docs list investors/funds (as claims)
AI component (ai_component) decentralized GPU cloud + data agent
Use‑case (use_case) AI inference/compute + data production
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 0 / 2
Last verified 2026-02-11

General project overview

Gata positions itself as an “open execution infrastructure for AI” and a set of AI products/modules. The docs describe the Decentralized GPU Cloud (DGPU): access to distributed GPUs via containers/VMs, a serverless API (planned), and model “deployment and inference” scenarios. Separately, the technical architecture describes the DataAgent process: input data is stored in BNB Greenfield, participants perform AI computation locally, and the output data and proofs of contribution are anchored back in BNB Greenfield.

Features/modules

  • DGPU Cloud (beta): decentralized GPU access and AI inference (per the docs).
  • DataAgent: production/validation of data for AI training (per the docs).
  • Applications/interfaces: GataGPT and others (mentioned on the website).

Typical scenarios

  • Scenario 1: a developer connects a wallet → gets access to DGPU → deploys/runs model inference.
  • Scenario 2: a participant provides compute → performs part of the AI computation on the input data → the results/proofs are anchored in BNB Greenfield (claim).

Getting started (wallet/network)

  • What you need: a wallet for interacting with the web products; for the token — BNB Chain.
  • Network/chain: DGPU/DataAgent are claimed as decentralized infrastructure; the token — BNB Smart Chain; the storage chain — BNB Greenfield (per the docs).
  • Fees: network fees for onchain operations.

Architecture/tech (non‑AI)

Per the docs:

  • Input data: stored in BNB Greenfield.
  • AI computation: performed by participants on local compute.
  • Output data + proofs: anchored back in BNB Greenfield (provenance/ownership/integrity).

Token/economics (expanded, no forecasts)

  • Token: GATA (BEP‑20) on BNB Smart Chain, max total supply 1,000,000,000 (BscScan).
  • Utility/distribution: in the current version of the docs, the “GATA Token” section is marked “coming soon”, so the TK utility flags are set conservatively.

Governance

  • Who makes decisions: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.

Project status and timeline

  • Current status: DGPU Cloud is described as “live in beta” (docs).

AI component of the project

  • What is real AI here? DGPU Cloud and DataAgent are described as infrastructure for AI inference/computation and AI data production; the docs state that DGPU supports “GPT‑based model deployment and inference” (beta).
  • What is truly onchain? BNB Greenfield is used as decentralized storage for input/output data and for anchoring proofs of contribution (per the technical architecture); the GATA token is onchain on BNB Smart Chain.
  • Why is a token needed? In the Tier‑1 docs, the token utility is not disclosed (a “coming soon” page), so the necessity of the token is not confirmed.
  • Red flags (based on the information found): token‑washing risk — the token exists, but its utility is not described in the docs; quality/throughput/latency metrics are not provided in Tier‑1 with context.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): the AI functionality is described as already existing products (DGPU/DataAgent), so the intent flag is not needed.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/product/decentralized-gpu-cloud
  • Why sufficient / why not (one line): there is a description of a working product (beta) and processes.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform performs AI computation (model deployment/inference) and AI‑driven data production (DataAgent) (claim).
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/product/decentralized-gpu-cloud ; https://gata-1.gitbook.io/gata-docs/architecture/editor
  • Why sufficient / why not (one line): the docs describe AI computation as a function of the platform.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): DGPU is described as “live in beta” and includes the steps “connect wallet → access GPU → run workloads”.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/product/decentralized-gpu-cloud
  • Why sufficient / why not (one line): there are specific steps and an “inference/deployment” example in the docs.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: —
  • Why sufficient / why not (one line): Tier‑1 contains no verifiable quality/performance metrics of the AI service with context.

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

  • AI_4 (decision): 1
  • Claim (one line): the architecture of the DataAgent cycle (input on Greenfield → participants’ compute → output+proofs on Greenfield) and the DGPU components are described.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/architecture/editor ; https://gata-1.gitbook.io/gata-docs/product/decentralized-gpu-cloud
  • Why sufficient / why not (one line): there is a technical description of the data/compute flow and onchain anchoring.

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain (per the token); BNB Greenfield (storage chain, per the docs)
  • Addresses/identifiers: GATA token: 0x46Ee3BFC281d59009cCD06F1dD6aBDbfCd82FFC3
  • Evidence: Tier‑1 — https://bscscan.com/token/0x46Ee3BFC281d59009cCD06F1dD6aBDbfCd82FFC3
  • Why sufficient / why not (one line): the onchain fact of the token is confirmed by the explorer.

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

  • OC_2 (decision): 1
  • Claim (one line): input/output data and proofs of contribution are “anchored back” in BNB Greenfield (claim) — onchain use beyond the token.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/architecture/editor
  • Why sufficient / why not (one line): the docs describe onchain anchoring of data/proofs as part of the architecture.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • Claim (one line): Tier‑1 contains no strict proof that without a blockchain the product completely loses its meaning (although provenance/ownership are claimed as a goal).
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/architecture/editor
  • Why sufficient / why not (one line): “criticality” (the replace‑the‑blockchain test) is not explicitly justified.

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Evidence: Tier‑1 — https://bscscan.com/token/0x46Ee3BFC281d59009cCD06F1dD6aBDbfCd82FFC3

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): the Tier‑1 docs contain no statement that DGPU/the products are paid for with the GATA token.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/product/decentralized-gpu-cloud
  • Why sufficient / why not (one line): “credits” and the beta are described, but no link to GATA is specified.

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/staking/collateral in the GATA token are not described in the Tier‑1 docs.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/architecture/images-and-media
  • Why sufficient / why not (one line): the “GATA Token” section in the docs is marked coming soon.

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance in the GATA token is not described in the Tier‑1 docs.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/architecture/images-and-media
  • Why sufficient / why not (one line): no information.

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the necessity of the token for the operation of the product is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://gata-1.gitbook.io/gata-docs/architecture/images-and-media
  • Why sufficient / why not (one line): without a described utility, the irreplaceability of the token cannot be asserted.

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.gata.net Official website: positioning of the products (GataGPT, DeCloud, DataAgent).
Tier‑1 https://gata-1.gitbook.io/gata-docs/product/decentralized-gpu-cloud Description of DGPU Cloud and “live in beta”, usage steps.
Tier‑1 https://gata-1.gitbook.io/gata-docs/architecture/editor Technical architecture of DataAgent and anchoring in BNB Greenfield.
Tier‑1 https://gata-1.gitbook.io/gata-docs/architecture/images-and-media The “GATA Token” page (coming soon) — absence of utility disclosure in the docs.
Tier‑1 https://bscscan.com/token/0x46Ee3BFC281d59009cCD06F1dD6aBDbfCd82FFC3 The token contract and max total supply on BNB Chain.
Tier‑1 https://github.com/Aggregata-xyz/aggregata The project repository (historical name/content).

No comments to display

Back to top