Skip to main content

enqAI

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

enqAI (formerly NoiseGPT) — an AI/Inference project on Ethereum, token (symbol: ENQAI).

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 project that describes the ENQAI token as an element of an ecosystem around LLM nodes/inference (claimed).
  • Who it’s for: node operators/network participants and inference clients (claimed).
  • Why onchain/token: the ENQAI token is used for node incentives, discounts for inference clients, governance and staking (per the documentation).

How it works (very briefly)

  1. The user does: holds/uses the ENQAI token and participates in the network’s scenarios (claimed).
  2. The system does: uses tokenomic incentives to support LLM nodes/inference (claimed).
  3. The user gets: discounts/incentives/participation in governance (claimed).
  4. Where the blockchain is: onchain — the token and transactions; AI inference/nodes — offchain infrastructure.
  5. Token role (if any): incentives/staking/governance and discounts (per the documentation).

Quick links: AI thesis fit

Project passport

Field Value
Project name enqAI
Also known as (aliases) ENQAI | NoiseGPT
Logo (logo) ../assets/558_noisegpt_logo.svg
Token symbol (ticker) ENQAI
Category AI/Inference
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2023
Project status (status) active
Token (standard) ERC-20
Token contract 0x710287D1D39DCf62094A83EBB3e736e79400068a
Token model (token_type) utility (payments + staking + governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The token is described as an instrument of incentives (LLM nodes), discounts for inference clients, governance and staking.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) LLM nodes + inference
Use‑case (use_case) AI inference network
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

In the Tier‑1 documentation, the ENQAI token is described as an element of an ecosystem around LLM nodes and inference: incentives for nodes, discounts for clients and governance/staking structures. At the same time, per Tier‑1 no demo/quality metrics of the AI part itself were found (hence the AI assessment is conservative).

Features/modules

  • LLM nodes incentives: tokenomic incentives for nodes (claimed).
  • Staking / security: staking as part of security (claimed).
  • Governance: claimed in the documentation.

Typical scenarios

  • Scenario 1: an operator maintains an LLM node → receives incentives (claimed).
  • Scenario 2: an inference client uses the network → receives a discount when using the token (claimed).

Getting started (wallet/network)

  • What you need: an EVM wallet for working with the token; access to the project’s products/infrastructure.
  • Network/chain: Ethereum.
  • Fees: Ethereum fees for operations with the token.

Architecture/tech (non‑AI)

  • Components: the ENQAI token (ERC‑20), offchain infrastructure of nodes/inference (claimed), project documentation.
  • Participant roles: LLM node operators; inference clients; token holders.
  • Where logic runs: onchain — the token and transactions; offchain — LLM nodes / inference.
  • Dependencies: Ethereum RPC; offchain node infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): incentives for LLM nodes; discount for inference clients; governance; staking/security; uptime incentives.
  • Who pays fees: users pay Ethereum fees for operations with the token.
  • Issuance/burn: — (not established per Tier‑1).
  • Security/incentive mechanisms: staking and incentives are described as part of security/sustainability (claimed).

Governance

  • Who makes decisions: governance via the token (claimed); the details of the process are not established per Tier‑1.
  • How protocol parameters change: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of the token smart contract and risks of the offchain node infrastructure.

Project status and timeline

  • Current status: active (based on the presence of public documentation/the token contract).
  • Key releases/milestones: —.
  • Roadmap: — (not established).

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? LLM nodes and inference are mentioned as the purpose of the ecosystem (claimed).
  • What is truly onchain? Onchain — the ENQAI token (ERC‑20).
  • Why is a token needed? Incentives/staking/governance and discounts for inference (per the documentation).
  • Red flags (based on the information found): without a Tier‑1 demo/metrics of the AI part (AI_2/AI_3), the actual operability and quality should be double‑checked.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as the purpose of the ecosystem (LLM nodes / inference), not as a “plan without implementation”.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): The intent flag adds no signal when AI is stated as the current goal/purpose.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The tokenomics describe LLM nodes and inference clients as key roles of the ecosystem.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): The documentation directly lists the roles (LLM nodes, inference clients) and the purpose of the token.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo surface (inference interface/nodes) was found.
  • Evidence: Tier‑1 — https://enqai.com/
  • Why sufficient / why not (one line): Without a specific demo, AI_2 remains 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://enqai.gitbook.io/enqai-documentation/
  • Why sufficient / why not (one line): No reproducible quality metrics were found in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the inference/node architecture is not established per Tier‑1.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/
  • Why sufficient / why not (one line): 1 requires a more specific technical artifact (architecture/versions).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ENQAI contract: 0x710287D1D39DCf62094A83EBB3e736e79400068a
  • Evidence: Tier‑1 — https://etherscan.io/token/0x710287D1D39DCf62094A83EBB3e736e79400068a
  • Why sufficient / why not (one line): The token contract is observable in a public explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: per Tier‑1, the existence of protocol‑level onchain logic other than the token is not established.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): 1 requires contracts/logic not reducible to the token (not found).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): It is not shown that the key function of AI inference breaks down without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ENQAI (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x710287D1D39DCf62094A83EBB3e736e79400068a
  • Why sufficient / why not (one line): The token contract is observable in the explorer.
  • 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): Mandatory payment for inference with the token is not established per Tier‑1 (there is the wording “discount for inference clients”).
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): A discount ≠ a mandatory payment with the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The token is used for incentives of LLM nodes and for security via staking.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): The documentation directly lists incentives and staking/security.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Governance is stated as a role of the token in the documentation.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): “governance” is listed among the roles of 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 per Tier‑1.
  • Evidence: Tier‑1 — https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token
  • Why sufficient / why not (one line): 1 requires an explicit argument “possible without the token” (not found).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://enqai.gitbook.io/enqai-documentation/project-overview/enqai-token Roles of the ENQAI token: incentives for LLM nodes, discount for inference clients, governance, staking/security, uptime incentives; the token contract.
Tier‑1 https://etherscan.io/token/0x710287D1D39DCf62094A83EBB3e736e79400068a Onchain fact: the ERC‑20 token ENQAI on Ethereum.
Tier‑2 https://www.coingecko.com/en/coins/noisegpt Token profile (for reference; context, not evidence).