Skip to main content

Kambria

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

Kambria — an AI/Other project (DeepTech open innovation; AI/robotics intent) on the Ethereum network, token (symbol: KAT).

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 platform/ecosystem for open DeepTech initiatives (including AI/Robotics) and a DAO model of joint ownership/commercialization of solutions.
  • Who it’s for: DAO participants (contributors and funds), developers/partners, “solution seekers” and the community.
  • Why onchain/token: the token is used as a means of interactions/payment and accounting for operations in the ecosystem (including participation in DAO mechanics).

How it works (very briefly)

  1. The participant chooses a DAO/initiative: joins a DAO, funds/participates in the development of a solution.
  2. The ecosystem organizes processes: DAO interactions and transactions are recorded through integrations and smart contracts (within the Kambria DAOs model).
  3. The participant receives: access to participation/purchases/licenses and the opportunity to participate in revenue distribution under DAO rules (if the solution is commercialized).
  4. Where the blockchain is: the KAT token (ERC‑20) and related operations/contracts used in the DAO model.
  5. Token role: KAT is needed for interactions in the ecosystem (payments, funding/participation, etc., per the tokenomics).

Quick links: AI thesis fit

Project passport

Field Value
Project name Kambria
Also known as (aliases) KAT
Logo (logo) ../assets/701_kambria_logo.svg
Token symbol (ticker) KAT
Category AI/Other | Infra
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 0x14da230d6726c50f759bc1838717f8ce6373509c
Token model (token_type) utility (payments)
Max supply 5 000 000 000 KAT (max supply)
Issuance —
Tokenomics (tokenomics, brief) KAT is claimed to be “necessary for interactions” in the ecosystem; ERC‑20 and BEP‑20 addresses and supply statistics on 2 networks are provided (update 2024‑11‑24).
Governance DAO (Kambria DAOs; integration with XDAO)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) DeepTech open innovation (AI/robotics)
Use‑case (use_case) DAO co-ownership + commercialization of tech solutions
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 2 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

Kambria describes itself as an open innovation platform for DeepTech (including AI/Robotics/Blockchain/IoT) and develops the Kambria DAOs model, where the community can co‑own technological solutions: participate in development/commercialization and receive revenue sharing under predefined rules.

Per Tier‑1 sources, the current focus initiative is Kambria DAOs, which are “running on XDAO” (a third‑party platform), while the Kambria team additionally develops smart contracts/integrations to ensure transparency of DAO transactions and implement the DAO financial model.

Features/modules

  • Kambria DAOs: a DAO model for co‑ownership of technologies (participation, contribution, revenue distribution).
  • Smart contracts/integrations: development of contracts for integration with the DAO platform and transaction transparency is claimed.
  • KAT tokenomics: token roles in ecosystem interactions.

Typical scenarios

  • Scenario 1: a participant funds a DAO → receives participation/rights within the DAO model and potential revenue sharing upon commercialization.
  • Scenario 2: a participant buys/uses an IP license/product → settlements/operations follow ecosystem rules, a role for KAT is claimed.

Getting started (wallet/network)

  • What you need: a wallet for Ethereum (for ERC‑20 KAT) and access to the project’s products/DAO processes.
  • Network/chain: Ethereum (ERC‑20 KAT); a BEP‑20 version is also mentioned in the tokenomics.
  • Fees: Ethereum network fees for operations with the token.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token and contract repository; smart contracts for integration with the DAO platform are claimed.
  • Participant roles: the model organizer/operator (Kambria), DAO participants, partners (dev/judge/production/channel/service/community).
  • Where logic runs: part of the logic — onchain (token/contracts), part — offchain (organization and operational processes).
  • Dependencies: the third‑party XDAO platform (mentioned as “DAO builder and management”).

Token/economics (expanded, no forecasts)

  • Token utility: KAT is claimed to be necessary for interactions in the ecosystem (payment/participation/rewards within Kambria DAOs processes).
  • Protocol necessity drivers: the Tier‑1 tokenomics lists token roles for different groups (solution seekers, innovators, manufacturers, community).
  • Issuance/burn: the Tier‑1 tokenomics gives a max supply of 5B and provides total/circulating supply statistics on two networks (update 2024‑11‑24).

Governance

  • Who makes decisions: a DAO model (Kambria DAOs) using XDAO is claimed.
  • How protocol parameters change: not established per Tier‑1.

Security and incidents

  • Audits: not found in Tier‑1 sources.
  • Bug bounty: not found in Tier‑1 sources.
  • Incidents: not established.

Project status and timeline

  • Current status: active (there are up‑to‑date tokenomics/supply updates).
  • Roadmap: the roadmap link is in links_*.

Ecosystem/integrations

  • Integrations: integration of Kambria DAOs with XDAO and development of smart contracts for transaction transparency are mentioned.
  • Where it’s actually used: use cases are described in the Tier‑1 tokenomics (by participant roles).

AI component of the project

  • What is real AI here? In Tier‑1 sources, AI is mentioned as part of the platform’s DeepTech focus/applicability; no Tier‑1 confirmation of a working AI component of the protocol was found.
  • What is truly onchain? The KAT ERC‑20 token and contract repository; development of smart contracts for DAO transactions/integration is claimed.
  • Why is a token needed? In the Tier‑1 tokenomics, KAT is described as necessary for interactions and operations in the Kambria/Kambria DAOs ecosystem.
  • Red flags (based on the information found): AI is listed as part of “DeepTech”, but without a specific description of an AI component of the product; part of the DAO logic relies on a third‑party platform.

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 1
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): AI is mentioned in Tier‑1 as part of the platform’s DeepTech focus/applicability.
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): This records AI intent/applicability, but does not prove a working AI component of the product at the protocol level.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No Tier‑1 description of a specific AI feature in the product was found (what exactly AI does).
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): Mentioning AI as a DeepTech field does not reveal how the AI component works.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A demo/example of the AI in operation was not found per Tier‑1.
  • Evidence: Tier‑1 — https://kambria.io/
  • Why sufficient / why not (one line): AI_2=1 requires a verifiable “surface” (app/demo) showing what exactly AI does.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://kambria.io/
  • Why sufficient / why not (one line): No reproducible set of AI quality metrics was found per Tier‑1 (with version/data context).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI component (architecture/versions/model) was not found per Tier‑1.
  • Evidence: Tier‑1 — https://kambria.io/
  • Why sufficient / why not (one line): A document/repo describing the architecture of the AI part is required, rather than just a list of fields.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 KAT: 0x14da230d6726c50f759bc1838717f8ce6373509c
  • Evidence: Tier‑1 — https://etherscan.io/token/0x14da230d6726c50f759bc1838717f8ce6373509c ; https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): There is a specific token contract and a Tier‑1 tokenomics page with the address.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: development of smart contracts for integration with the DAO platform and transparency of DAO transactions is claimed (within the Kambria DAOs model).
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/ ; https://github.com/kambria-platform/kambria-contracts
  • Why sufficient / why not (one line): Beyond the token, there is a Tier‑1 mention of using/developing contracts for DAO mechanics.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established per Tier‑1 that the model/product breaks down without the blockchain (part of the logic relies on offchain processes and a third‑party platform).
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): OC_3=1 requires an explicit argument about “what exactly breaks down” when replacing onchain with a regular DB.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, KAT (ERC‑20; a BEP‑20 version is also mentioned).
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): The Tier‑1 tokenomics lists contract addresses and KAT roles.
  • 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): KAT is described as necessary for interactions in the ecosystem, including purchases/payments (for example, buy NFT IP licenses, purchases in Kambria DAOs ecosystem).
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): Tier‑1 lists use cases of the token as a means of settlements/interactions.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Mechanisms of collateral/penalties/staking for security are not established per Tier‑1.
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): TK_2=1 requires specific descriptions of staking/slashing/collateral.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of KAT specifically is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): The tokenomics mentions different tokens/roles in DAOs (for example, GT), but the KAT↔governance link is not recorded as mandatory.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token (for example, with USDT) is not established per Tier‑1.
  • Evidence: Tier‑1 — https://kambria.io/tokenomics/
  • Why sufficient / why not (one line): TK_4=1 requires explicit confirmation that the token is not a necessary mechanism, but only a “wrapper”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://kambria.io/tokenomics/ The purpose of Kambria/Kambria DAOs; roles of the KAT token; ERC‑20 address and supply statistics (update 2024‑11‑24).
Tier‑1 https://github.com/kambria-platform/kambria-contracts The existence of a public repository of the project’s smart contracts (a development artifact of the onchain part).
Tier‑1 https://etherscan.io/token/0x14da230d6726c50f759bc1838717f8ce6373509c Onchain fact of the existence of the KAT ERC‑20 token and the contract address.

No comments to display

Back to top