Skip to main content

ClinTex CTi

ClinTex CTi — 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).

ClinTex CTi — a project on the Ethereum network, token (symbol: CTI).

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 with the CTI token (ERC‑20) on the Ethereum network; describing the product requires analysis of Tier‑1 sources.
  • Who it’s for: —.
  • Why onchain/token: the token exists, but the necessity of the token for the product is not confirmed by Tier‑1 sources (see the techpaper/docs and onchain artifacts).

How it works (very briefly)

  1. The user does: interacts with the token (transactions/transfers) or the product (not established).
  2. The system does: records operations on the Ethereum network.
  3. The user gets: a confirmed record of the operation on the blockchain.
  4. Where the blockchain is: onchain — the token contract and transactions.
  5. Token role (if any): not confirmed by Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name ClinTex CTi
Also known as (aliases) CTI
Logo (logo) ../assets/720_clintex-cti_logo.svg
Token symbol (ticker) CTI
Category —
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 0xcb8fb2438a805664cd8c3e640b85ac473da5be87
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) —
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 2
Last verified 2026-02-11

General project overview

The project is represented by the CTI token (ERC‑20) on the Ethereum network and public repositories (including a repository with documents/a techpaper). Details of the product, the AI component and the necessity of the token require verification against Tier‑1 documents; this is not confirmed in the available Tier‑1 sources as of the verification date.

Features/modules

  • —.

Typical scenarios

  • Scenario 1: a user transfers the token → the transaction is recorded on the Ethereum network.
  • Scenario 2: a developer studies the repositories → gets access to the source code (if applicable).

Getting started (wallet/network)

  • What you need: a wallet for EVM networks.
  • Network/chain: Ethereum.
  • Fees: Ethereum network fees (gas) for transactions.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract (Ethereum), code repositories, wallets/RPC providers.
  • Participant roles: token holders, developers.
  • Where logic runs: onchain (the token contract) + offchain (product components are not established).
  • Dependencies: Ethereum infrastructure for the token.

Token/economics (expanded, no forecasts)

  • Token utility: No Tier‑1 confirmation of the token utility in the product was found.
  • Protocol necessity drivers: —.
  • Who pays fees: users of the Ethereum network.
  • Where fees go: to Ethereum validators/stakers (at the network level).
  • 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

Project status and timeline

  • Current status: not established.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: EVM wallets and Ethereum infrastructure.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component or AI intent was found.
  • What is truly onchain? The CTI token contract on the Ethereum network and operations with it (Tier‑1: explorer).
  • Why is a token needed? The token exists, but its utility/necessity in the product is not confirmed by Tier‑1 sources.
  • Red flags (based on the information found): Tier‑1 proof of an AI component and of the necessity of the token in the product is absent.

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 partially present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 AI intentions are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable Tier‑1 claim about AI plans.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): What exactly the AI component does is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable description of an AI feature per Tier‑1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Demos/examples of the AI component in operation are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable product demo in links_*.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Metrics/benchmarks were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the AI part is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 documentation with model architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

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

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

  • OC_2 (decision): 0
  • What useful logic is onchain: Tier‑1 confirmation of onchain logic of the product, other than the token, is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No verifiable addresses/descriptions of product contracts beyond the ERC‑20 token were found in the available Tier‑1 sources.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that the product breaks down without onchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no justification of onchain criticality per Tier‑1/2.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, CTI (ERC‑20), on the Ethereum network.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xcB8fb2438A805664cD8c3e640b85AC473DA5BE87
  • Why sufficient / why not (one line): The token contract is available onchain.
  • 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): It is not established that the token is used to pay for the service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No Tier‑1 source with a specific description of payment utility was found.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties using the token are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of the incentive mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): It is not established that the token is used for governance.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics with 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.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no data to justify replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xcB8fb2438A805664cD8c3e640b85AC473DA5BE87 The CTI ERC‑20 token contract and the Ethereum network (onchain fact).
Tier‑1 https://github.com/ClinTex/ Public project repositories (development artifact).
Tier‑1 https://github.com/ClinTex/Documents/blob/master/Clintex_CTi_Techpaper.pdf Tier‑1 project document/techpaper (requires verification of the contents regarding AI/onchain/token claims).
Tier‑1 — No Tier‑1 source for claim “the project has an AI component” was found.
Tier‑2 https://coinmarketcap.com/currencies/clintex-cti/ Token profile (for reference; not proof of technology).

No comments to display

Back to top