Skip to main content

nuco.cloud

nuco.cloud (NCDT) — 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).

nuco.cloud — an Infra/Compute / DePIN/Compute project: the website describes products for distributed computing (Skynet/PRO/GO) and mentions AI use cases (“Artificial Intelligence” as the main area of demand). The NCDT token (ERC‑20 on Ethereum) is used in the payment/discount economy and (per the tokenomics page) in the “70% miner / 30% nuco.cloud” payment distribution.

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 service/platform for access to computing resources (including for AI workloads), positioned as a “decentralized mesh hyperscaler”.
  • Who it’s for: clients who need compute capacity; providers/miners (in nuco.cloud GO).
  • Why onchain/token: NCDT is used as a means of payment/discounts and as part of the incentive mechanics (rewards/NUCO↔NCDT bridge per the tokenomics).

How it works (very briefly)

  1. The user does: chooses a product (Skynet/PRO/GO) and buys compute.
  2. The system does: selects compute resources and provides infrastructure/management (per the description on the website).
  3. The user gets: access to compute/hosting/storage and (as claimed) a reduction in cost.
  4. Where the blockchain is: the NCDT token is confirmed onchain (Ethereum); the tokenomics describe the payment and distribution rules.
  5. Token role (if any): a discount when paying in NCDT + the “70% miner / 30% nuco.cloud” economic model; a reward model via the NUCO↔NCDT bridge (per the tokenomics).

Quick links: AI thesis fit

Project passport

Field Value
Project name nuco.cloud
Also known as (aliases) NCDT, NCDToken, nuco.cloud GO, nuco.cloud PRO, nuco.cloud Skynet
Logo (logo) ../assets/269_nuco-cloud_logo.svg
Token symbol (ticker) NCDT
Category AI/Compute | Infra | DePIN/Compute
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 0xe0c8b298db4cffe05d1bea0bb1ba414522b33c1b
Token model (token_type) utility (governance)
Max supply 50,000,000 NCDT
Issuance fixed; a buy‑back & burn plan is described (tokenomics)
Tokenomics (tokenomics, brief) 20% discount when paying in NCDT; 70/30 payment distribution miner/nuco.cloud
Governance company
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI-focused compute infrastructure
Use‑case (use_case) compute for AI workloads
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 1 / 3
Last verified 2026-02-11

General project overview

nuco.cloud describes itself as a “decentralized mesh hyperscaler” and offers a product line: Skynet (a mesh level on top of the PRO infrastructure), PRO (professional data centers), GO (a distributed computing model where private users can “monetize computing power”). On the website, AI is listed as one of the key drivers of demand for compute.

Features/modules

  • Skynet: a mesh network for scaling compute (per the website).
  • PRO: compute/hosting/storage from professional data centers (per the website).
  • GO: a distributed model where users share the resources of their devices and receive rewards (per the website).
  • NCDT tokenomics: a 20% discount when paying in NCDT; payment distribution rules and the NUCO↔NCDT bridge model (tokenomics).

Typical scenarios

  • Scenario 1: a client buys compute → uses it for AI/analytics/rendering, etc. (website).
  • Scenario 2: a client pays in NCDT → receives a discount (tokenomics).
  • Scenario 3: a user participates as a miner in GO → receives rewards (tokenomics: the NUCO↔NCDT bridge is described).

Getting started (wallet/network)

  • What you need: an account/access to the platform; an EVM wallet for NCDT.
  • Network/chain: NCDT — Ethereum (ERC‑20).
  • Fees: gas in ETH for NCDT operations; the cost of compute — per the products’ pricing.

Architecture/tech (non‑AI)

  • Components: a compute management platform + data centers/devices; the NCDT (ERC‑20) and NUCO (TELOS) tokens for GO (tokenomics).
  • Participant roles: clients; miners/resource providers (GO); the team/company.
  • Where logic runs: compute — offchain; onchain — token accounting/transfers and the bridge layer (described).
  • Dependencies: Ethereum (NCDT), TELOS (NUCO), pNetwork bridge (described in the tokenomics).

Token/economics (expanded, no forecasts)

  • Token utility: payment for products in NCDT with a 20% discount (tokenomics).
  • Protocol necessity drivers: incentivizing miners/compute providers (70% of the payment to the miner; NUCO↔NCDT bridge in GO) (tokenomics).
  • Who pays fees: users (gas) during onchain token operations.
  • Where fees go: gas → to Ethereum validators; per the tokenomics, 70% of the payment (when paying in NCDT) goes to the miner, 30% returns to nuco.cloud.
  • Issuance/burn: fixed supply of 50M; a buy‑back & burn plan starting from 2025 is described (tokenomics).
  • Security/incentive mechanisms: discount/payment and the reward model (tokenomics).
  • Distribution and token issuance schedule: the tokenomics describe the supply shares: circulating 50%, company reserve 25% (locked vesting), the other 25% for rewards/development (tokenomics).
  • Treasury: the company reserve is described as locked with a German token custodian (tokenomics), but addresses are not provided in the extracted fragment.

Governance

  • Who makes decisions: company.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: centralization risks of the compute layer; claims about buy‑back & burn require verification of actual transactions; the NUCO↔NCDT bridge is mentioned without addresses/artifacts in the extracted Tier‑1.

Project status and timeline

  • Current status: the Skynet/PRO/GO products are published on the website; the NCDT token exists on Ethereum.
  • Key releases/milestones: news/updates are published on the website.
  • Roadmap: https://nuco.cloud/post/nuco-clouds-2025-roadmap-update---scaling-innovation-and-utility

Ecosystem/integrations

  • Integrations: pNetwork bridge (NUCO↔NCDT, claimed on the tokenomics); the data center suppliers/partners listed on the website — as context.
  • Partners: — (not recorded in this card without explicit Tier‑1 confirmations with details).
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? in the extracted Tier‑1, nuco.cloud describes itself as a compute provider for AI workloads (AI as a use case), not as a developer of models/agents; the news/roadmap mention an “AI‑focused Layer‑2 blockchain” (as a plan).
  • What is truly onchain? the NCDT token is confirmed (ERC‑20, address on the tokenomics and Etherscan).
  • Why is a token needed? utility in payment (20% discount) and in the miner/nuco.cloud payment distribution economy; the NUCO↔NCDT bridge model for GO is also described.
  • Red flags (based on the information found): AI‑washing risk (AI — mainly as a “client use case for compute”, without its own AI product/metrics); onchain logic other than the token/the described bridge is not confirmed by addresses; buy‑back & burn — a plan/claim, verification of execution is needed.

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 low 1
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): nuco.cloud claims AI as a key use case for compute and writes about an “AI‑Focused Layer‑2 Blockchain” (as a direction/plan in the news/roadmap).
  • Evidence: Tier‑1 — https://nuco.cloud/ ; https://nuco.cloud/post/german-government-confirms-grant-to-support-development-of-nuco-clouds-ai-focused-layer-2-blockchain
  • Why sufficient / why not (one line): there is a Tier‑1 claim about an AI direction, but no Tier‑1 evidence of its own AI module/models.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): in the extracted Tier‑1 there is no description of its own AI component (models/agents/inference) — the project is about compute infrastructure.
  • Evidence: Tier‑1 — https://nuco.cloud/
  • Why sufficient / why not (one line): “AI” appears as a use case of demand for compute, not as a function of an AI product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): an AI demo is not applicable: in the extracted Tier‑1 there is no AI product/module to demonstrate; there are compute products.
  • Evidence: Tier‑1 — https://nuco.cloud/
  • Why sufficient / why not (one line): the demo relates to the compute platform, not to an AI model/agent.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://nuco.cloud/
  • Why sufficient / why not (one line): there are no AI quality metrics (as a model/agent).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): in the extracted Tier‑1 there is no technical description of an AI architecture/models; there is a description of compute products.
  • Evidence: Tier‑1 — https://nuco.cloud/
  • Why sufficient / why not (one line): the AI architecture is not disclosed.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: NCDT token: 0xe0c8b298db4cffe05d1bea0bb1ba414522b33c1b
  • Evidence: Tier‑1 — https://etherscan.io/token/0xe0c8b298db4cffe05d1bea0bb1ba414522b33c1b ; https://nuco.cloud/token-economy/tokenomics
  • Why sufficient / why not (one line): the token address is confirmed by the explorer and published on the tokenomics page.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: in the extracted Tier‑1 there are no addresses/contracts that implement compute settlement/accounting (other than the token); the bridge is described as a “pNetwork bridge”, but without addresses.
  • Evidence: Tier‑1 — https://nuco.cloud/token-economy/tokenomics ; https://nuco.cloud/
  • Why sufficient / why not (one line): without specific onchain artifacts we consider that mainly the token is confirmed.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the compute platform can function without a blockchain as well; the token layer of discounts/payments is supplementary.
  • Evidence: Tier‑1 — https://nuco.cloud/ ; https://nuco.cloud/token-economy/tokenomics
  • Why sufficient / why not (one line): onchain criticality is not proven; onchain looks like payments/incentives.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, NCDT.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xe0c8b298db4cffe05d1bea0bb1ba414522b33c1b ; https://nuco.cloud/token-economy/tokenomics
  • Why sufficient / why not (one line): the NCDT token is confirmed by the explorer and published on the tokenomics page.
  • 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): tokenomics: clients who pay in NCDT receive a 20% discount on products.
  • Evidence: Tier‑1 — https://nuco.cloud/token-economy/tokenomics
  • Why sufficient / why not (one line): payment/a discount when paying in the token is described.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the tokenomics describe a reward model for miners in GO and the 70% miner / 30% nuco.cloud payment distribution.
  • Evidence: Tier‑1 — https://nuco.cloud/token-economy/tokenomics
  • Why sufficient / why not (one line): there is a described incentive model with payment distribution.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the governance utility of NCDT is not confirmed in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://nuco.cloud/token-economy/tokenomics
  • Why sufficient / why not (one line): the tokenomics page describes payments/discounts/bridge, but not governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): discounts/payment for compute can be implemented without NCDT as well (fiat/USDC), leaving the infrastructure product in place.
  • Evidence: Tier‑1 — https://nuco.cloud/token-economy/tokenomics ; https://nuco.cloud/
  • Why sufficient / why not (one line): the value of the compute product does not depend on the token; the token serves pricing/incentives.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://nuco.cloud/token-economy/tokenomics NCDT utility (discount, payment distribution, supply of 50M, NUCO↔NCDT bridge, buy‑back & burn plan)
Tier‑1 https://etherscan.io/token/0xe0c8b298db4cffe05d1bea0bb1ba414522b33c1b the onchain address and max total supply of NCDT (ERC‑20)
Tier‑1 https://nuco.cloud/ the positioning of the compute products and of AI as a key use case of demand

No comments to display

Back to top