Skip to main content

GNUS.AI

GNUS.AI (Genius Token / NFT Collections) — 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).

GNUS.AI — an AI/Compute | Infra project: a network/platform that claims distributed processing of AI/ML tasks on the “idle” compute resources of devices; token (symbol: GNUS).

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 tries to turn the idle compute of devices into a network for distributed data processing (including AI/ML).
  • Who it’s for: application/game developers and device users who can “share” compute.
  • Why onchain/token: onchain is described as the accounting/escrow/payout layer; the GNUS token is used for payments and participant rewards.

How it works (very briefly)

  1. The user does: launches an application/game with the GNUS.AI integration and provides “idle” compute.
  2. The network does: distributes compute tasks across nodes (devices) and aggregates the results.
  3. Validation does: the described mechanism verifies/reconciles the results and records completion.
  4. Where the blockchain is: the blockchain is used for process accounting/escrow and payout distribution.
  5. Token role: GNUS is used as the means of settlement and incentives (rewards) in the ecosystem.

Quick links: AI thesis fit

Project passport

Field Value
Project name GNUS.AI
Also known as (aliases) Genius Token, GNUS
Logo (logo) ../assets/502_genius-token-nft-collections_logo.svg
Token symbol (ticker) GNUS
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x614577036F0a024DBC1C88BA616b394DD65d105a
Token model (token_type) utility (payments + staking + governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The token is described as an instrument for payments for compute and for participant rewards.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) distributed computing for AI/ML
Use‑case (use_case) idle compute network for data processing
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

GNUS.AI describes a system where the compute load (including AI/ML) is distributed across a network of devices. As motivation, participants receive rewards in the GNUS token. The documentation explains the idea of distributed processing of “idle” resources and adaptive allocation of resources according to the network’s needs.

Features/modules

  • Distributed computation: use of idle CPU/GPU of devices.
  • Resource allocation (described): dynamic allocation of compute according to demand.
  • Onchain settlement (described): process accounting and payout distribution via the blockchain/escrow.

Typical scenarios

  • Scenario 1: a user launches an application with the GNUS SDK → the device performs computation during idle periods → receives GNUS.
  • Scenario 2: a requester/application submits a task for processing → the network distributes the computation → after confirmation, the results are returned and the payout is made.

Getting started (wallet/network)

  • What you need: access to the product/integration via an application/SDK (details — in the docs).
  • Network/chain: Ethereum (the token contract) + the project’s own stack/description of the blockchain in the documentation.
  • Fees: Ethereum network fees for operations with the ERC‑20; the internal fee/accounting model is described in the documentation.

Architecture/tech (non‑AI)

  • Components (per the tech docs): a smart contract on Ethereum (an escrow‑like scheme) + a p2p/communication layer (IPFS pub/sub) + a PoW/consensus component (described as “gathers real POW” and submits it to the contract).
  • Participant roles: users/devices (compute nodes), compute requesters, integration developers.
  • Where logic runs: computation — offchain on devices; accounting/escrow/part of the consensus — onchain via the contract.
  • Dependencies: an IPFS‑like stack and related libraries are listed in the tech docs.

Token/economics (expanded, no forecasts)

  • Token utility: payments for compute and rewards to nodes/participants.
  • Protocol necessity drivers: the token is described as the internal “settlement” asset of the system, which links the demand for compute with the supply of compute.
  • Issuance/burn: not established per Tier‑1.

Governance

  • Who makes decisions: not established per Tier‑1.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks to the correctness of computations/communication and to data integrity; the tech docs describe a consensus component and verification via the onchain contract.

Project status and timeline

  • Current status: not established per Tier‑1 (the documentation is up to date, but the network status as “mainnet/testnet” is not recorded in one place).
  • Roadmap: a public roadmap in GitBook (see links_*).

Ecosystem/integrations

  • Integrations: integration via the SDK into applications/games (described in the docs).
  • Partners: a list of partners is published on the website (see links_* Website).

AI component of the project

  • What is real AI here? the project claims processing of AI/ML tasks on distributed nodes (idle compute) and describes this in the documentation.
  • What is truly onchain? there is an ERC‑20 contract on Ethereum and a described onchain settlement/escrow layer.
  • Why is a token needed? the token is used as the mechanism for payments for compute and for reward distribution.
  • Red flags (based on the information found): performance/quality/cost metrics are claimed in general phrases; AI_3 requires benchmarks with context (versions/methodology).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
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/ML processing is described as a current goal of the system, not only as future plans.
  • Evidence: Tier‑1 — https://docs.gnus.ai/gnus.ai-gitbook/about-gnus.ai/how-does-it-work
  • Why sufficient / why not (one line): We do not single out AI intent separately, since Tier‑1 describes AI/ML as the main scenario.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The network processes compute tasks, including AI processing and data analysis, on distributed device nodes.
  • Evidence: Tier‑1 — https://docs.gnus.ai/gnus.ai-gitbook/about-gnus.ai/how-does-it-work ; https://gnus.ai
  • Why sufficient / why not (one line): The documentation directly describes AI processing as a class of tasks.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 “what you can touch” (app/demo) with a specific entry point was found.
  • Evidence: Tier‑1 — https://docs.gnus.ai
  • Why sufficient / why not (one line): Without an explicit demo/app URL we do not raise the flag.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.gnus.ai
  • Why sufficient / why not (one line): No reproducible set of metrics (speed/cost/quality) with context was found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is a tech doc on the system components (contract/communication/IPFS layer/PoW component).
  • Evidence: Tier‑1 — https://docs.gnus.ai/gnus.ai-gitbook/technical-information/super-genius-blockchain-technical-details
  • Why sufficient / why not (one line): The document lists the components and the flow; this is sufficient for “tech context present”.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: GNUS ERC‑20 contract: 0x614577036F0a024DBC1C88BA616b394DD65d105a
  • Evidence: Tier‑1 — https://etherscan.io/token/0x614577036F0a024DBC1C88BA616b394DD65d105a
  • Why sufficient / why not (one line): The token contract in the explorer is the minimal confirmation of the onchain component.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: accounting/escrow‑like settlement for payouts and consensus (per the tech description).
  • Evidence: Tier‑1 — https://docs.gnus.ai/gnus.ai-gitbook/technical-information/super-genius-blockchain-technical-details
  • Why sufficient / why not (one line): The tech doc describes a smart‑contract escrow‑like layer as part of the system.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 that the system cannot operate without the blockchain (rather than turning into a centralized settlement service).
  • Evidence: Tier‑1 — https://docs.gnus.ai/gnus.ai-gitbook/technical-information/super-genius-blockchain-technical-details
  • Why sufficient / why not (one line): OC_3=1 requires an explicit argument of irreplaceability; not found per Tier‑1.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, GNUS (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x614577036F0a024DBC1C88BA616b394DD65d105a
  • Why sufficient / why not (one line): The existence of the token contract is confirmed by the explorer.
  • 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): The token is used to pay for compute services/task processing in the network.
  • Evidence: Tier‑1 — https://gnus.ai
  • Why sufficient / why not (one line): The website describes “pay for compute services” within the GNUS ecosystem.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Participants receive GNUS for providing compute (reward system).
  • Evidence: Tier‑1 — https://docs.gnus.ai/gnus.ai-gitbook/about-gnus.ai/how-does-it-work ; https://gnus.ai
  • Why sufficient / why not (one line): The documentation links the amount of compute to the amount of GNUS rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.gnus.ai
  • Why sufficient / why not (one line): TK_3=1 requires an explicit section on governance mechanics; not found.
  • 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://gnus.ai
  • Why sufficient / why not (one line): TK_4=1 requires an explicit argument “it can be replaced”; not found per Tier‑1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://gnus.ai Product description: distributed processing power for AI/ML workloads; the role of the token in payments/rewards.
Tier‑1 https://docs.gnus.ai/gnus.ai-gitbook/about-gnus.ai/how-does-it-work Explanation of distributed computation and of the link compute ↔ GNUS rewards.
Tier‑1 https://docs.gnus.ai/gnus.ai-gitbook/technical-information/super-genius-blockchain-technical-details Tech description of the components: contract/escrow‑like layer, IPFS pub/sub, PoW component.
Tier‑1 https://etherscan.io/token/0x614577036F0a024DBC1C88BA616b394DD65d105a The GNUS token contract on Ethereum.
Tier‑2 https://www.coingecko.com/en/coins/genius-ai Token profile/metadata (for reference).
Tier‑2 https://coinmarketcap.com/currencies/genius-token-nft-collections/ Token profile/metadata (for reference).

No comments to display

Back to top