CUDOS
CUDOS — 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).
CUDOS — an Infra project on the Ethereum 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: a project positioned in Tier‑1 sources as infrastructure/a platform around compute (cloud/distributed computing).
- Who it’s for: users and teams that need compute; providers of computational resources.
- Why onchain/token: the onchain fact is recorded as a token contract on Ethereum; the necessity of onchain/the token for the product is not established per Tier‑1.
How it works (very briefly)
- The user does: requests/uses compute (per the description in Tier‑1 sources).
- The system does: matches demand for compute with available resources (details of the mechanics are not established).
- The user gets: a computational result/access to resources (details not established).
- Where the blockchain is: the onchain facts in this card show a token contract on the Ethereum network.
- Token role (if any): the existence of the token is established by the contract; the role/utility of the token is not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | CUDOS |
| Also known as (aliases) | Cudos |
| Logo (logo) | ../assets/721_cudos_logo.svg |
| Token symbol (ticker) | — |
| Category | Infra |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x817bbDbC3e8A1204f3691d14bB44992841e3dB35 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | compute infrastructure (positioning only) |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.cudos.org/ |
| Docs | https://docs.cudos.org/ |
| GitHub | https://github.com/CudoVentures/ |
| Releases / Changelog | https://github.com/CudoVentures/cudos-node/commits |
| Whitepaper | https://assets.cudos.foundation/2022/03/cudos-technical-paper.pdf |
| Roadmap | https://www.cudos.org/blog/the-2024-roadmap-for-cudos-a-year-of-innovation-and-collaboration |
| Security advisories | https://github.com/CudoVentures/cudos-node/security |
| Explorer | https://etherscan.io/token/0x817bbDbC3e8A1204f3691d14bB44992841e3dB35 |
| X | https://twitter.com/CUDOS_ |
| Discord | https://discord.com/invite/cudos |
| Telegram | https://t.me/cudostelegram |
| Medium | https://medium.com/cudos |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/cudos |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cudos/ |
General project overview
CUDOS is positioned in Tier‑1 sources (official website/documentation/repositories) as an infrastructure project around compute. Only verifiable artifacts (Tier‑1 links and onchain facts) are recorded within this card, and conclusions about AI/onchain/token are drawn conservatively: where there is no confirmation, it is marked as “not established”.
Features/modules
- Project documentation: an entry point to the description and components.
- Source code/repositories: public repositories of the organization.
- Token on Ethereum: an onchain artifact in the form of a token contract.
Typical scenarios
- Scenario 1: a team looks for a compute solution → studies the project’s Tier‑1 documentation/materials → decides whether to test it (details of “getting started” are not established).
- Scenario 2: a user checks the token’s onchain artifacts → uses the explorer to view the contract and basic parameters.
Getting started (wallet/network)
- What you need: — (no unified “quickstart” was found per Tier‑1).
- Network/chain: Ethereum (for the onchain part in the form of a token).
- Fees: Ethereum network fees apply to transactions with the token.
Architecture/tech (non‑AI)
- Components: — (without a detailed technical analysis; see Tier‑1 documentation/repositories).
- Participant roles: —.
- Where logic runs: —.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1.
- Protocol necessity drivers: not established.
- Who pays fees: token users (transactions on Ethereum).
- Where fees go: to Ethereum validators (network fees).
- Issuance/burn: —.
- Security/incentive mechanisms: —.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: —.
Project status and timeline
- Current status: —.
- Key releases/milestones: —.
- Roadmap: No Tier‑1 roadmap was found (links_* contains
—).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? No confirmation of an AI component or AI intent was found per Tier‑1 (AI_0..AI_4 = 0).
- What is truly onchain? An onchain artifact in the form of a token contract on the Ethereum network.
- Why is a token needed? The existence of the token is established per the contract; the necessity/utility of the token is not established per Tier‑1.
- Red flags (based on the information found): risk of AI‑washing (if AI is claimed without Tier‑1 artifacts); risk of onchain‑washing (if “onchain” boils down to the token only); what to double‑check: whether Tier‑1 contains explicit AI intent and whether there is protocol onchain logic beyond the token.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | low | 0 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 1 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): No Tier‑1 AI intent (roadmap/official declaration) was found.
- Evidence: Tier‑1 — https://www.cudos.org/ ; https://docs.cudos.org/
- Why sufficient / why not (one line): Without explicit wording about AI intentions in Tier‑1, we set 0.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): It is not established per Tier‑1 what exactly “the AI does” as a component of the product/protocol.
- Evidence: Tier‑1 — https://docs.cudos.org/
- Why sufficient / why not (one line): Without a specific description of the AI feature in Tier‑1, we set 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): Tier‑1 demos/examples of the AI component in operation are not established.
- Evidence: Tier‑1 — https://www.cudos.org/ ; https://docs.cudos.org/
- Why sufficient / why not (one line): Without an explicit demo surface for AI, we set 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://docs.cudos.org/
- Why sufficient / why not (one line): No reproducible set of AI quality metrics/benchmarks was found per Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A Tier‑1 tech description specifically of the AI component/model versions is not established.
- Evidence: Tier‑1 — https://docs.cudos.org/ ; https://assets.cudos.foundation/2022/03/cudos-technical-paper.pdf
- Why sufficient / why not (one line): Without an explicit AI tech description/versions, we set 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0x817bbDbC3e8A1204f3691d14bB44992841e3dB35
- Evidence: Tier‑1 — https://etherscan.io/token/0x817bbDbC3e8A1204f3691d14bB44992841e3dB35
- Why sufficient / why not (one line): The contract address and onchain history are observable via the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established (other than the token).
- Evidence: Tier‑1 — https://docs.cudos.org/
- Why sufficient / why not (one line): No confirmation of protocol onchain logic beyond the token was found per Tier‑1.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: what breaks down without onchain is not established (per current Tier‑1 data).
- Evidence: Tier‑1 — https://docs.cudos.org/
- Why sufficient / why not (one line): OC_3=1 requires an explicit justification of onchain criticality; 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 (contract on Ethereum).
- Evidence: Tier‑1 — https://etherscan.io/token/0x817bbDbC3e8A1204f3691d14bB44992841e3dB35
- Why sufficient / why not (one line): The existence of the token contract is a sufficient onchain fact for TK_0=0.
- 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): The claim “the token is used to pay for the service” is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.cudos.org/ ; https://assets.cudos.foundation/2022/03/cudos-technical-paper.pdf
- Why sufficient / why not (one line): Without an explicit description of the mechanics of payments with the token, we set 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): The use of the token for incentives/collateral/penalties is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.cudos.org/ ; https://assets.cudos.foundation/2022/03/cudos-technical-paper.pdf
- Why sufficient / why not (one line): Without a verifiable description of incentives/collateral/penalties, we set 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the token in governance is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.cudos.org/
- Why sufficient / why not (one line): TK_3=1 requires explicit Tier‑1 governance mechanics with the token; not found per Tier‑1.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token with alternatives (USDC/subscription) is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.cudos.org/
- Why sufficient / why not (one line): TK_4=1 requires an explicit justification of “can be replaced without loss of meaning”; not found per Tier‑1.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.cudos.org/ | Official project website (Tier‑1 entry point to the description/docs). |
| Tier‑1 | https://docs.cudos.org/ | Official documentation (used to verify AI/onchain/token claims). |
| Tier‑1 | https://github.com/CudoVentures/ | Public project organization/repositories (development artifacts). |
| Tier‑1 | https://assets.cudos.foundation/2022/03/cudos-technical-paper.pdf | Project technical document (Tier‑1). |
| Tier‑1 | https://etherscan.io/token/0x817bbDbC3e8A1204f3691d14bB44992841e3dB35 | Onchain fact: the token contract on the Ethereum network. |
| Tier‑1 | — | No Tier‑1 source for claim “the project has an AI component or AI intent” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “the token is necessary for the service/incentives/governance” was found. |
| Tier‑2 | https://www.coingecko.com/en/coins/cudos | Reference token profile (not proof of utility). |
| Tier‑2 | https://coinmarketcap.com/currencies/cudos/ | Reference token profile (not proof of utility). |
No comments to display
No comments to display