Skip to main content

Catheon Gaming

Catheon Gaming — 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).

Catheon Gaming — a Gaming/Infra project associated with a gaming ecosystem stack and an SDK for integrating blockchain features; there is a token on Polygon (symbol: CATHEON).

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: an ecosystem/platform for Web3 games and the integration of blockchain features into applications via an SDK (claimed).
  • Who it’s for: game studios/publishers and users who interact with in‑game Web3 features.
  • Why onchain/token: onchain is used for the token and the claimed integration of on‑chain data; no confirmed AI component was found per Tier‑1.

How it works (very briefly)

  1. Publisher/developer integrates the SDK and API for working with blockchain features into a game/application.
  2. Platform provides access to on‑chain data and auxiliary integration tools (claimed).
  3. User receives game assets/features with a blockchain component (depending on the specific game/application).
  4. Where the blockchain is: the integration of on‑chain data and the token/transactions on supported networks are claimed.
  5. Token role: the specific utility of the token within the platform is not established.

Quick links: AI thesis fit

Project passport

Field Value
Project name Catheon Gaming
Also known as (aliases) CATHEON
Logo (logo) —
Token symbol (ticker) CATHEON
Category Gaming | Infra
Primary chain (chain) Polygon
Type EVM
Network status mainnet
Consensus (consensus) PoS (Polygon)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0x7e7737C40878e720b32e7bC9CD096259f876d69f
Token model (token_type) —
Max supply 10,000,000,000 CATHEON
Issuance fixed (total supply)
Tokenomics (tokenomics, brief) the website lists distribution categories and wallet addresses (see Evidence)
Governance company
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) Web3 gaming SDK/platform
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 0 / 1
Last verified 2026-02-11

General project overview

Per the available materials, the project includes a token on the Polygon network and documentation for an SDK (CGC SDK) intended for integrating blockchain features into applications. The AI component is not confirmed per Tier‑1 sources.

Features/modules

  • CGC SDK and Core API for integrating blockchain features (per the documentation).
  • Integration tools (minting, dashboards, etc.) are claimed in the SDK documentation.
  • The “Catheon Gaming Center” web application (demo/showcase).

Typical scenarios

  • Scenario 1: a developer integrates the SDK → gets access to on‑chain data without direct integration with the blockchain (claimed).
  • Scenario 2: a user opens the “Gaming Center” → browses games/content (features depend on the client/device).

Getting started (wallet/network)

  • What you need: an EVM wallet is needed to interact with onchain features (depending on the specific application).
  • Network/chain: Polygon (and other networks may be supported by the SDK).
  • Fees: Polygon network fees for transactions.

Architecture/tech (non‑AI)

  • Components: SDK, Core API, web interfaces of dashboards (per the documentation).
  • Where logic runs: transactions and on‑chain data — onchain; the SDK/integration — offchain + access to onchain data.

Token/economics (expanded, no forecasts)

  • Total supply: 10B tokens (per the official token page).
  • Distribution: the token page lists distribution categories and wallet addresses (unvested/vested).
  • Token utility: not established.

Governance

  • A description of a DAO/voting is not established; in this card we record “company” as the default governance model in the absence of a DAO description.

Security and incidents

  • Public audits/bug bounty/incidents: not established.

Project status and timeline

  • The SDK documentation and the website are publicly available; other milestones are not established.

Ecosystem/integrations

  • The SDK documentation lists supported networks (Polygon, BSC, Ethereum, Solana).

AI component of the project

  • What is real AI here? no Tier‑1 confirmations of an AI component were found.
  • What is truly onchain? an ERC‑20 token on Polygon and the claimed integration of on‑chain data via the SDK.
  • Why is a token needed? the utility of the token for the operation of the service is not established.
  • Red flags (based on the information found): possible “AI labeling” around the ecosystem without Tier‑1 confirmations of a specific AI component.

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 medium 2
Token necessity low 0
Evidence Tier‑1 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): no Tier‑1 roadmap/plan for AI was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no Tier‑1 roadmap for AI found.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI functionality is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 sources contain no description of AI models/agents/metrics.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no demo of an AI component was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is a web application of the platform, but it is not a Tier‑1 AI demo.
  • 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): AI metrics were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): no AI tech description was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the available SDK documentation contains no AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Polygon
  • Addresses/identifiers: token contract = 0x7e7737C40878e720b32e7bC9CD096259f876d69f
  • Evidence: Tier‑1 — https://catheongaming.com/catheon/
  • Why sufficient / why not (one line): the official token page records the network, the contract and the total supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: integration of on‑chain data and blockchain features into applications via the SDK (claimed).
  • Evidence: Tier‑1 — https://docs.catheongaming.com/
  • Why sufficient / why not (one line): the documentation describes the integration and access to on‑chain data.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the platform may have offchain components; onchain criticality is not proven.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has an ERC‑20 token on Polygon.
  • Evidence: Tier‑1 — https://catheongaming.com/catheon/
  • Why sufficient / why not (one line): the token page specifies the contract and the network.
  • 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): payment for services with the token is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no Tier‑1 description of the token utility was found.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/collateral/penalties via the token are not confirmed by Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): not established.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description of a governance mechanism.
  • 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): insufficient data on the role of the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://catheongaming.com/catheon/ The Polygon network, the token contract and the total supply of 10B.
Tier‑1 https://docs.catheongaming.com/ Purpose of the SDK: integration of blockchain features and access to on‑chain data.
Tier‑1 https://github.com/CatheonGaming/cgc-evm-public-contracts Existence of a public contracts repository (Catheon Token smart contract).
Tier‑1 — No Tier‑1 source for claim “the project has an AI component” was found.
Tier‑1 — No Tier‑1 source for claim “the token is necessary for the operation of the platform/SDK” was found.

No comments to display

Back to top