Skip to main content

Cindicator

Cindicator — 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).

Cindicator — an AI/Analytics | DeFi project on the Ethereum network, token (symbol: CND).

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 “Hybrid Intelligence” system: a combination of collective forecasts/assessments by people and a set of ML models for analytical signals (per the Tier‑1 whitepaper).
  • Who it’s for: users/analysts who participate in forming forecasts/signals, and consumers of analytical products (per Tier‑1).
  • Why onchain/token: the CND token (ERC‑20) is described in the whitepaper as an infrastructure token for access to products/data/services; the onchain logic mostly boils down to the token.
  • What you can actually touch (Tier‑1): the project’s web platform app.cindicator.com (participation/access to the product).

How it works (very briefly)

  1. The user does: answers questions/gives forecasts (crowd input) and/or consumes analytical indicators.
  2. The system does: aggregates the collective signal and applies ML models/algorithms for adjustments and forming the final signals (per the whitepaper description).
  3. The user gets: aggregated indicators/signals and access to products/data.
  4. Where the blockchain is: the CND token is issued as an ERC‑20 on Ethereum.
  5. Token role: access to part of the products/data/services (per the whitepaper; not financial advice).

Quick links: AI thesis fit

Project passport

Field Value
Project name Cindicator
Also known as (aliases) CND
Logo (logo) ../assets/678_cindicator_logo.svg
Token symbol (ticker) CND
Category AI/Analytics | DeFi
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 0xd4c435f5b09f855c3317c8524cb1f586e42795fa
Token model (token_type) utility (payments)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Tier‑1 whitepaper: the token is used as an infrastructure mechanism of access to products/data/services; supply details are not established in this card.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) hybrid intelligence (crowd + ML models)
Use‑case (use_case) analytical indicators/signals from forecasts
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

In the Tier‑1 whitepaper, Cindicator describes “Hybrid Intelligence” — a combination of collective input (a group of analysts/forecasters) and a set of machine learning models for processing/correcting errors and forming the final indicators/signals. The CND token is described as an infrastructure token for access to part of the products/data/services.

Features/modules

  • Collective intelligence: collecting forecasts/answers from users (“foresters”).
  • ML pipeline: models/algorithms for weighting, error correction and forming the final signals (per the Tier‑1 description).
  • CND token: a mechanism of access to part of the infrastructure/products (per the whitepaper).

Typical scenarios

  • Scenario 1: a user answers questions/makes forecasts → the system aggregates them and forms signals.
  • Scenario 2: a user consumes indicators/analytics → uses them as informational material (not financial advice).

Getting started (wallet/network)

  • What you need: access to the project’s products/interfaces (details are not established in this card).
  • Network/chain: Ethereum (for the CND token).
  • Fees: Ethereum fees apply to operations with the CND token.

Architecture/tech (non‑AI)

  • Components: an offchain platform (forecast collection, ML processing) + the ERC‑20 token CND.
  • Participant roles: user‑forecasters, analytics consumers, platform operators (not detailed).
  • Where logic runs: ML/aggregation — offchain; the token — onchain (Ethereum).
  • Dependencies: Ethereum (token).

Token/economics (expanded, no forecasts)

  • Token utility: access to products/indicators/data/services (described in the whitepaper).
  • Protocol necessity drivers: the token is described as an infrastructure layer of access.
  • Who pays fees: users of the token for transactions on Ethereum.
  • Where fees go: to Ethereum validators (gas).
  • Issuance/burn: — (not established in this card).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: — (not established).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established).
  • How protocol parameters change: — (not established).
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: the quality of signals depends on the methodology and data; without public quality metrics in this card there is a risk of “AI marketing without measurability” (AI_3=0).

Project status and timeline

  • Current status: active (the whitepaper and public channels exist).
  • Key releases/milestones: the whitepaper is dated 2017‑10‑04 (as a document; not as a launch date).
  • Roadmap: — (not established).

Ecosystem/integrations

  • Integrations: — (not established).
  • Partners: — (not established).
  • Where it’s actually used: — (not established).

AI component of the project

  • What is real AI here? the Tier‑1 whitepaper describes ML models/algorithms that process the collective signal and form indicators/signals.
  • What is truly onchain? the ERC‑20 token CND on Ethereum.
  • Why is a token needed? the whitepaper describes the token as a mechanism of access to products/data/services.
  • Red flags (based on the information found): the absence of public quality metrics/benchmarks (AI_3=0); onchain‑washing (onchain mostly boils down to the token); token‑washing (if access can be implemented without the token — this needs to be double‑checked in Tier‑1).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 contains a description of a working AI part (ML pipeline), so this is not “intent only”.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): AI is described as a component of the system, not as a “plan”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): ML models aggregate/correct collective forecasts and form indicators/signals.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): The whitepaper describes hybrid intelligence as the interaction of crowd + ML models.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): Tier‑1: the project has a web platform app.cindicator.com (the product’s demo surface).
  • Evidence: Tier‑1 — https://app.cindicator.com/ ; https://cindicator.com/platform
  • Why sufficient / why not (one line): There is a public product interface that can be checked.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): A Tier‑1 description of reproducible quantitative quality metrics is not recorded in this card.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The whitepaper describes the composition of the system and the classes of models/algorithms used (pipeline).
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): This provides a tech context at the documentation level (without code).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 token CND: 0xd4c435f5b09f855c3317c8524cb1f586e42795fa
  • Evidence: Tier‑1 — https://etherscan.io/token/0xd4c435f5b09f855c3317c8524cb1f586e42795fa
  • Why sufficient / why not (one line): The token contract on a public network confirms the onchain component.
  • 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://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): The token is described, but the protocol onchain logic of the system is not established in Tier‑1.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, CND.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): The whitepaper describes “issuing CND tokens”.
  • 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 as a mechanism of access to products/data/services (as described in the whitepaper).
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): The whitepaper lists products/access for token holders.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Staking/slashing/collateral as a protocol necessity is not established in Tier‑1.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): 1 requires an explicit description of the incentive/penalty mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A governance role of the token is not established in Tier‑1.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): 1 requires an explicit description of voting/governance.
  • 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.
  • Evidence: Tier‑1 — https://cindicator.com/Cindicator_WhitePaper_en.pdf
  • Why sufficient / why not (one line): TK_4=1 requires a separate justification of replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://cindicator.com/Cindicator_WhitePaper_en.pdf Tier‑1: description of Hybrid Intelligence (crowd + ML models) and the purpose of the CND token (access to products/data).
Tier‑1 https://etherscan.io/token/0xd4c435f5b09f855c3317c8524cb1f586e42795fa Onchain fact: the CND token contract on Ethereum.
Tier‑1 https://cindicator.com/ The project’s official website (context/navigation).
Tier‑1 https://app.cindicator.com/ Tier‑1: demo surface (the project’s web platform).

No comments to display

Back to top