Skip to main content

Roko Network

Roko Network (ROKO) — 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).

Roko Network — an AI/Agents | Infra project on Ethereum, token (symbol: ROKO).

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/platform that describes itself as a network for “human‑machine collaboration”, AI agents and related components (marketplace/orchestration/ledger/DAO).
  • Who it’s for: developers, AI researchers and teams who want to create/experiment with AI agents and related services (claimed).
  • Why onchain/token: onchain records the ROKO token (ERC‑20); the necessity of the token for the product’s key logic is not established per Tier‑1.

How it works (very briefly)

  1. The user does: uses the ecosystem components (for example, marketplace/orchestration; claimed).
  2. The system does: organizes the interaction of people/machines and AI components (claimed).
  3. The user gets: access to services/artifacts (for example, AI agents; claimed).
  4. Where the blockchain is: onchain records the token and transactions; the rest of the logic is described per Tier‑1 as a platform/network without a detailed onchain specification.
  5. Token role (if any): the token exists; specific mandatory roles of the token (payment/incentives/governance) are not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Roko Network
Also known as (aliases) ROKO
Logo (logo) —
Token symbol (ticker) ROKO
Category AI/Agents | 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 0x6f222e04f6c53cc688ffb0abe7206aac66a8ff98
Token model (token_type) —
Max supply 369 369 369 369 ROKO
Issuance fixed (max supply)
Tokenomics (tokenomics, brief) Max total supply is recorded on the token page (Etherscan).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents + orchestration
Use‑case (use_case) AI agents marketplace
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

In its official documentation, Roko Network describes its goal as a “decentralized, self‑organizing network” for human‑machine collaboration and AI components. At the same time, per Tier‑1 no artifact was found that unambiguously shows a working AI product/demo and onchain logic, other than the fact of the token’s existence.

Features/modules

  • AI Agents Marketplace: a platform for creating/managing/trading AI agents as NFTs (claimed).
  • AI Workload Orchestration (Hydra): orchestration of resources for AI workloads (claimed).
  • Roko Ledger / RokoDAO: a ledger and a governance structure (claimed).

Typical scenarios

  • Scenario 1: a developer/user creates an AI agent → uses the marketplace (claimed).
  • Scenario 2: a developer launches an AI workload → uses orchestration (claimed).

Getting started (wallet/network)

  • What you need: an EVM wallet for working with the token; access to the products via the project’s links.
  • Network/chain: Ethereum (the ROKO token — ERC‑20).
  • Fees: Ethereum fees for operations with the token.

Architecture/tech (non‑AI)

  • Components: the ROKO token (ERC‑20), project documentation (GitBook).
  • Participant roles: users/token holders; developers/ecosystem participants (claimed).
  • Where logic runs: onchain — the token and transactions; the claimed services/platform — outside the current sample.
  • Dependencies: Ethereum RPC for onchain operations; the documentation’s web infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Who pays fees: users pay Ethereum fees for operations with the token.
  • Issuance/burn: max total supply 369 369 369 369 ROKO (per the token page).
  • Security/incentive mechanisms: not established per Tier‑1.

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: typical risks of token smart contracts; the risks of the “AI components” are not separately established.

Project status and timeline

  • Current status: mainnet (the token on Ethereum).
  • 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? In Tier‑1 sources, AI agents and orchestration for AI workloads are claimed, but without a demonstration/metrics.
  • What is truly onchain? Onchain — the ROKO token (ERC‑20) and transactions.
  • Why is a token needed? A specific mandatory role of the token is not established per Tier‑1.
  • Red flags (based on the information found): a description of components without reproducible artifacts (demo/code/metrics); it is important to find Tier‑1 evidence of the product actually working.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
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): AI is mentioned as part of the description of components and purposes (not as a “plan without implementation”).
  • Evidence: Tier‑1 — https://docs.roko.network/roko-network/introduction-to-roko-network
  • Why sufficient / why not (one line): The intent flag adds no signal when AI is described as part of the current vision/components.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI agents and orchestration of AI workloads (marketplace/hydra) are described.
  • Evidence: Tier‑1 — https://docs.roko.network/roko-network/introduction-to-roko-network
  • Why sufficient / why not (one line): The Tier‑1 document lists the AI components and their purpose at the level of description.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo/example of using an AI agent/the marketplace was found.
  • Evidence: Tier‑1 — https://docs.roko.network/
  • Why sufficient / why not (one line): The documentation did not provide a reproducible demo surface.
  • 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.roko.network/
  • Why sufficient / why not (one line): No quality metrics of the AI part were identified per 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 AI module’s architecture (versions/model/implementation components) was not found per Tier‑1.
  • Evidence: Tier‑1 — https://docs.roko.network/
  • Why sufficient / why not (one line): More specific technical artifacts (code/architecture/versions) are needed.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ROKO contract: 0x6f222e04f6c53cc688ffb0abe7206aac66a8ff98
  • Evidence: Tier‑1 — https://etherscan.io/token/0x6f222e04f6c53cc688ffb0abe7206aac66a8ff98
  • 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://docs.roko.network/roko-network/introduction-to-roko-network
  • Why sufficient / why not (one line): 1 requires explicit onchain logic of the product (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://docs.roko.network/roko-network/introduction-to-roko-network
  • Why sufficient / why not (one line): No evidence was found that the product breaks down without the blockchain (other than holding the token).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ROKO (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x6f222e04f6c53cc688ffb0abe7206aac66a8ff98
  • 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): The use of the token as mandatory payment for the service is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.roko.network/
  • Why sufficient / why not (one line): The documentation has no clear link between “payment specifically with the token” and a key function.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Token incentives/collateral/penalties are not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.roko.network/
  • Why sufficient / why not (one line): 1 requires a specific incentive mechanism (not found).
  • 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.roko.network/roko-network/introduction-to-roko-network
  • Why sufficient / why not (one line): A mention of a DAO does not equal a description of governance mechanics via 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://docs.roko.network/
  • Why sufficient / why not (one line): 1 requires explicit argumentation “possible without the token” (not found).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.roko.network/roko-network/introduction-to-roko-network Tier‑1 description of the project’s purpose and components (AI agents marketplace, orchestration, DAO; at the level of claims).
Tier‑1 https://etherscan.io/token/0x6f222e04f6c53cc688ffb0abe7206aac66a8ff98 Onchain fact: the ERC‑20 contract of the ROKO token and max total supply.

No comments to display

Back to top