CPChain
CPChain (CPC) — 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).
CPChain — an infrastructure IoT blockchain project; the Tier‑1 documentation claims “AI‑decisions based on IoT big data” (intent), as well as multi‑party data transactions and cross‑chain interaction.
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: blockchain infrastructure for IoT tasks and data exchange (Tier‑1 docs).
- Who it’s for: developers/teams building IoT applications and data transactions (claimed).
- Why onchain/token: Tier‑1 confirms the existence of blockchain infrastructure; the onchain component does not boil down to token issuance. The existence of the CPC token/asset is confirmed, but the necessity of the token in the protocol is not established per Tier‑1.
How it works (very briefly)
- The user does: publishes/exchanges data and runs scenarios on the network (claimed).
- The system does: provides multi‑party trust for data transactions and data compatibility (claimed).
- The user gets: verifiable accounting/transactions of data and interaction between participants (claimed).
- Where the blockchain is: the Tier‑1 documentation and repositories confirm the existence of an onchain network/code; additionally, the CPC asset is visible in the block explorer.
- Token role (if any): the CPC token/asset exists; the specific utility of the token is not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | CPChain |
| Also known as (aliases) | Cyber Physical Chain; CPC token |
| Logo (logo) | ../assets/543_cpchain_logo.ico |
| Token symbol (ticker) | CPC |
| Category | AI/Other | Infra |
| Primary chain (chain) | — |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | — |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | — |
| Token contract | — |
| 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) | AI-driven decisions on IoT big data |
| Use‑case (use_case) | IoT data transactions |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 2 / 0 / 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://cpchain.io/ |
| Docs | https://docs.cpchain.io/ |
| GitHub | https://github.com/cpchain |
| Releases / Changelog | https://github.com/CPChain/chain/commits/master/ |
| Whitepaper | https://cpchain.io/whitepaper |
| Roadmap | — |
| Security advisories | https://github.com/CPChain/chain/security |
| Explorer | https://explorer.bnbchain.org/asset/CPC-FED |
| X | https://twitter.com/cpchain_io |
| Discord | https://discord.gg/Z6DVS84 |
| Telegram | https://t.me/cpchain |
| Medium | https://medium.com/cpchain-tech |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cpchain/ |
General project overview
CPChain (Cyber Physical Chain) positions itself as infrastructure for IoT, where the blockchain is used for multi‑party trust in data transactions and for the interaction of data/assets (including cross‑chain).
In the Tier‑1 documentation, AI is mentioned as “AI decisions based on IoT big data” (intent), but without a sufficient tech description of the model/metrics per Tier‑1.
Features/modules
- Multi‑party data transaction (claimed in Tier‑1 docs).
- AI‑decisions on IoT big data (intent; without metrics/architecture per Tier‑1).
- Cross‑chain relay/collaboration (claimed).
Typical scenarios
- Scenario 1: participants exchange data → receive verifiable accounting and trust in data transactions (claimed).
- Scenario 2: a developer builds an IoT application → uses the CPChain network/infrastructure (claimed).
Getting started (wallet/network)
- What you need: launch/connection details — in the docs (see links_*).
- Network/chain: the CPChain network (network details/chain‑ID are not recorded per Tier‑1).
- Fees: not established per Tier‑1.
Architecture/tech (non‑AI)
- Components: the blockchain network + code repositories (see links_*); component details were not recorded.
- Participant roles: network participants/developers/users of data transactions (claimed).
- Where logic runs: part of the logic is onchain on the CPChain network; the details of the distribution — not established.
- Dependencies: — (not found per Tier‑1).
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1.
- Protocol necessity drivers: not established.
- Who pays fees: not established.
- Where fees go: not established.
- Issuance/burn: — (not established).
- 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: — (not established).
- Keys/multisig: — (not established).
Security and incidents
- Audits: — (not found per Tier‑1).
- Bug bounty: —.
- Incidents: — (not found per Tier‑1).
- Threat model: AI is claimed at the intent level, but without technical artifacts; the network status and the contracts/addresses also require re‑checking.
Project status and timeline
- Current status: mainnet (based on the presence of public artifacts and the asset explorer).
- Key releases/milestones: — (not established).
- Roadmap: —.
Ecosystem/integrations
- Integrations: — (not found per Tier‑1).
- Partners: — (not found per Tier‑1).
- Where it’s actually used: — (not found per Tier‑1).
AI component of the project
- What is real AI here? The Tier‑1 docs claim “AI decisions based on IoT big data” (intent), but no metrics/architecture/demo were found per Tier‑1.
- What is truly onchain? The Tier‑1 documentation and repositories confirm the blockchain infrastructure; additionally, the CPC asset is visible in the block explorer.
- Why is a token needed? The CPC token/asset exists; Tier‑1 confirmation of the necessity of the token (payment/incentives/governance) is not established.
- Red flags (based on the information found): AI‑washing risk (intent without technical artifacts), the network/contracts/token utility require re‑checking.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): the Tier‑1 docs claim “Artificial intelligence decisions based on IoT big data”.
- Evidence: Tier‑1 — https://docs.cpchain.io/
- Why sufficient / why not (one line): this records intent, but without metrics/architecture of the AI component.
- 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 (functions/boundaries) is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.cpchain.io/
- Why sufficient / why not (one line): not enough specifics for 1 were found 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 part in operation were not found per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no Tier‑1 demo → 0.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found.
- Context (version/date/how measured): not found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no metrics/benchmarks → 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a tech description/architecture of the AI component is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.cpchain.io/
- Why sufficient / why not (one line): insufficient data for 1 → 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: CPChain (detailed network parameters are not recorded per Tier‑1)
- Addresses/identifiers: docs + the chain repository; CPC asset: CPC-FED
- Evidence: Tier‑1 — https://docs.cpchain.io/, https://github.com/CPChain/chain
- Why sufficient / why not (one line): Tier‑1 docs and code confirm the existence of the network/protocol.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: multi‑party data transactions / infrastructure for data exchange (claimed).
- Evidence: Tier‑1 — https://docs.cpchain.io/
- Why sufficient / why not (one line): the onchain purpose is described as infrastructural and does not boil down to the token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: per Tier‑1, it is not established that without the blockchain the product breaks down (strictly).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient formalized justification for 1 → 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token/asset, CPC (per the explorer data).
- Evidence: Tier‑1 — https://explorer.bnbchain.org/asset/CPC-FED
- Why sufficient / why not (one line): the existence of the asset is confirmed in the block 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 utility of the token as payment for the service is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without confirmation → 0.
- 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 established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance via the token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- 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 → 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.cpchain.io/ | AI intent + a description of the network’s functions (data transactions / cross‑chain) |
| Tier‑1 | https://github.com/CPChain/chain | the network’s source code/repository (a development artifact) |
| Tier‑1 | https://explorer.bnbchain.org/asset/CPC-FED | onchain: the existence of the CPC asset |
| Tier‑1 | — | No Tier‑1 source for claim “the token is necessary as payment/incentives/governance” was found. |
| Tier‑2 | https://coinmarketcap.com/currencies/cpchain/ | reference token profile (not proof of utility) |
| Tier‑3 | — | — |
No comments to display
No comments to display