Cloudbric
Cloudbric — 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).
Cloudbric — an Infra project on the Kaia network, token (symbol: —).
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 cybersecurity project (per the website/whitepaper) with a token on the Kaia network.
- Who it’s for: for users/clients of the product (the exact segments are not systematized per Tier‑1 in the available sources).
- Why onchain/token: onchain records ownership and transfers of the token; the necessity of the token in the product is not established per Tier‑1.
How it works (very briefly)
- The user does: uses the Cloudbric product/service (per the project’s description).
- The system does: provides security functionality (details are not confirmed per Tier‑1).
- The user gets: a result/protection/service (in terms of the project’s description).
- Where the blockchain is: the token and its operations — onchain (Kaia).
- Token role (if any): per Tier‑1, no unambiguous justification of the necessity of the token was found.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Cloudbric |
| Also known as (aliases) | — |
| Logo (logo) | ../assets/528_cloudbric_logo.png |
| Token symbol (ticker) | — |
| Category | Infra |
| Primary chain (chain) | Kaia |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | — |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | cybersecurity |
| 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 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.cloudbric.io |
| Docs | https://ico.cloudbric.io/upload/file/Cloudbric_Whitepaper_EN.pdf |
| GitHub | https://github.com/Cloudbric-Project?tab=repositories |
| Releases / Changelog | https://github.com/Cloudbric-Project/Cloudbric-Contracts/commits/master/ |
| Whitepaper | https://cloudbric.io/whitepaper |
| Roadmap | — |
| Security advisories | https://github.com/Cloudbric-Project/Cloudbric-Contracts/security |
| Explorer | https://kaiascan.io/token/0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1 |
| X | https://twitter.com/cloudbric |
| Discord | — |
| Telegram | https://t.me/cloudbric |
| Medium | https://medium.com/@cloudbric |
| Audit report(s) | https://iosiro.com/audits/cloudbric-crowdsale-smart-contract-audit |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/cloudbric |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cloudbric/ |
General project overview
Per Tier‑1 sources, the project has a website, a whitepaper and a repository with smart contracts, as well as a token on the Kaia network with a public contract. No Tier‑1 confirmation of an AI component (in terms of “what the AI does” + artifacts) was found, so per the SSOT algorithm (ai_score = 0) → DecAI Fit = 0/6.
Features/modules
- Security project: description on the official website/whitepaper.
- Smart contracts (repository): public repository with the contracts.
- Token (Kaia): onchain contract and basic operations.
Typical scenarios
- Scenario 1: the user reads the whitepaper/materials → understands the claimed purpose of the project.
- Scenario 2: the user checks the token and transactions → uses the block explorer.
Getting started (wallet/network)
- What you need: an EVM wallet for the Kaia network.
- Network/chain: Kaia.
- Fees: Kaia network fees for onchain operations.
Architecture/tech (non‑AI)
- Components: the token (onchain, Kaia) + offchain products/services (details are not established per Tier‑1); the project’s smart contracts on GitHub.
- Participant roles: users/token holders; product users.
- Where logic runs: the token — onchain; the product logic — not established per Tier‑1.
- Dependencies: Kaia network infrastructure (for the token) and the product infrastructure (not established).
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 sources.
- Protocol necessity drivers: it is not established that the product does not work without the token.
- Who pays fees: users pay Kaia network fees for onchain operations.
- Where fees go: to the Kaia network validators (network level).
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Keys/multisig: —.
Security and incidents
- Audits: the link to the audit report is in links_* (iOSiro).
- Bug bounty: —.
- Incidents: —.
- Threat model: smart contract risks and offchain infrastructure/product risks.
Project status and timeline
- Current status: —.
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? No Tier‑1 confirmation of an AI component was found.
- What is truly onchain? The token on the Kaia network (contract, transactions and metadata via the block explorer).
- Why is a token needed? Not established per Tier‑1 sources.
- Red flags (based on the information found): AI positioning without technical artifacts; absence of a Tier‑1 explanation of the necessity of the token.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | absent | 0 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 limited | 1 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): No Tier‑1 AI intentions/roadmap were found.
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): Without a Tier‑1 AI claim, this flag remains 0.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): No Tier‑1 description of an AI feature was found.
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): No specific description of an AI component (task/input/output) was found per Tier‑1.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No Tier‑1 demos/examples of an AI component were found (the AI component is not established).
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): Without a confirmed AI component, AI_2 is not raised.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): Quality metrics of the AI component are absent, because the AI component is not established per Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No Tier‑1 tech description of an AI component was found (the AI component is not established).
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): AI_4=1 requires tech docs/a repository/architecture of the AI part.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Kaia
- Addresses/identifiers: token contract: 0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1
- Evidence: Tier‑1 — https://kaiascan.io/token/0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1
- Why sufficient / why not (one line): The onchain contract page confirms the existence of the token and the network.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established per Tier‑1 (other than the token).
- Evidence: Tier‑1 — https://kaiascan.io/token/0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1
- Why sufficient / why not (one line): No Tier‑1 confirmation of useful onchain logic beyond the token was 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://www.cloudbric.io
- Why sufficient / why not (one line): No Tier‑1 justification was found for why onchain is critical for the product.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token on the Kaia network (the contract is in the block explorer).
- Evidence: Tier‑1 — https://kaiascan.io/token/0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1
- Why sufficient / why not (one line): The existence of the token is confirmed by onchain data.
- 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): No Tier‑1 confirmation of payment for the service with the token was found.
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): TK_1=1 requires Tier‑1 terms/tariffs/docs where the token is a mandatory payment.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): No Tier‑1 confirmation of incentives/collateral/penalties with the token was found.
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): TK_2=1 requires economy/incentive rules.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of the use of the token in governance was found.
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): TK_3=1 requires a Tier‑1 governance process and a role of the token in voting.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability/irreplaceability of the token is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.cloudbric.io
- Why sufficient / why not (one line): TK_4=1 requires a Tier‑1 explanation that the token is not necessary.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.cloudbric.io | Tier‑1 source: basic description of the project. |
| Tier‑1 | https://cloudbric.io/whitepaper | Tier‑1 whitepaper of the project (context and description). |
| Tier‑1 | https://github.com/Cloudbric-Project?tab=repositories | Tier‑1 artifact: public organization/repositories of the project. |
| Tier‑1 | https://kaiascan.io/token/0xc4407f7dc4b37275c9ce0f839652b393e13ff3d1 | Onchain fact: the token contract on the Kaia network, transactions and metadata. |
| Tier‑1 | — | No Tier‑1 source for claim “what is real AI here” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “why is a token needed” was found. |
| Tier‑2 | https://iosiro.com/audits/cloudbric-crowdsale-smart-contract-audit | Smart contract audit report (outside onchain facts). |
No comments to display
No comments to display