Commune AI
Commune AI — 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).
Commune AI — an AI/Other | Infra project (Subspace), token (symbol: C).
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 peer‑to‑peer incentive‑driven coordination system for decentralized AI: onchain “Modules” (identifiers) around offchain objects (including AI models) and the Subspace blockchain for coordination and stake economics (Tier‑1 docs).
- Who it’s for: module/subnet developers, miners/validators, participants who want to provide utility (for example, inference) and receive stake.
- Why onchain/token: onchain is needed for the global namespace of modules, stake and governance; voting and the economy are tied to stake (Tier‑1 docs).
- What you can actually touch (Tier‑1): connect a wallet and access staking/operations through
wallet.communeai.org, as well as set up/run a Subspace node following the instructions in the docs.
How it works (very briefly)
- The participant does: registers/uses a Module (API object), participates in a subnet as a miner/validator or votes/stakes.
- The network does: coordinates Modules and incentive landscapes through onchain stake mechanics; the Subspace blockchain provides consensus and p2p discovery.
- The participant receives: the ability to participate in the network economy (stake/mining/validating) and governance (voting proportional to stake).
- Where the blockchain is: its own Subspace (Commune) network based on Substrate (Tier‑1 docs).
- Token role (if any): the token/stake is used for incentives and voting (Tier‑1 docs).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Commune AI |
| Also known as (aliases) | — |
| Logo (logo) | ../assets/792_commune-ai_logo.svg |
| Token symbol (ticker) | C |
| Category | AI/Other | Infra |
| Primary chain (chain) | Subspace |
| Type | Appchain |
| Network status | mainnet |
| Consensus (consensus) | — |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | native (Subspace) |
| Token contract | — |
| Token model (token_type) | utility (stake + governance) |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | incentive coordination for AI Modules (incl. inference) via subnets |
| Use‑case (use_case) | protocol/network for incentive-driven coordination of decentralized AI Modules |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 3 / token_score 2 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.communeai.org/ |
| Docs | https://communeai.org/docs/getting-started/intro |
| GitHub | https://github.com/commune-ai |
| Releases / Changelog | https://github.com/commune-ai/subspace/commits |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | https://github.com/commune-ai/subspace/security |
| Explorer | https://wallet.communeai.org/ |
| App / Demo | https://wallet.communeai.org/ |
| X | https://twitter.com/communeaidotorg |
| Discord | https://discord.com/invite/communeai |
| Telegram | https://t.me/communecommunity |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/commune-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/commune-ai/ |
General project overview
Commune AI, per the Tier‑1 documentation, describes a peer‑to‑peer incentive‑driven coordination system for decentralized AI: onchain “Modules” (identifiers) in a global namespace that wrap offchain objects (including AI models, datasets, compute) and expose them as APIs. Coordination of modules and incentive landscapes takes place through its own Subspace blockchain (Substrate‑based) and stake economics.
Features/modules
- Public repositories and project documentation.
- Subspace blockchain (Commune) and p2p coordination through Modules/Subnets (Tier‑1 docs).
Typical scenarios
- Scenario 1: a participant stakes/sends tokens and interacts with the network through the official wallet.
- Scenario 2: a participant runs a node/subnet/miner/validator following the documentation and participates in the incentive mechanics.
Getting started (wallet/network)
- What you need: a wallet (SubWallet) and access to the Subspace (Commune) network.
- Network/chain: Subspace (Commune).
- Fees: not established per Tier‑1 sources (depends on network operations).
Architecture/tech (non‑AI)
- Components: Subspace blockchain (Substrate‑based), Modules (onchain identifiers) and offchain module endpoints (API), subnets, p2p discovery/RPC.
- Participant roles: module/subnet developers, miners, validators, stakeholders/voters.
- Where logic runs: coordination/stake/governance — onchain; computation (for example, inference) — offchain behind module APIs.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token/stake utility: stake is used as an economic mechanism (stake is “mined” by providing utility to validator stake; voting is proportional to stake) — Tier‑1 docs.
- Protocol necessity drivers: the network economy and governance are tied to stake (Tier‑1 docs).
- Who pays fees: not established per Tier‑1 sources.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
Project status and timeline
- Current status: —.
- Key releases/milestones: —.
- Roadmap: not found (links_* has
—).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? The protocol coordinates Modules, which can be AI models/datasets/compute; stake is “mined” by providing utility (for example, inference) — Tier‑1 docs.
- What is truly onchain? Subspace blockchain: onchain identifiers (Modules), stake mechanics and governance processes are described in the Tier‑1 documentation.
- Why is a token needed? Tier‑1 docs describe stake economics and voting proportional to stake (utility for incentives and governance).
- Red flags (based on the information found): absence of an explicit Tier‑1 consolidated whitepaper/roadmap in links_* (in this card —
—); most details are distributed across the docs.
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | high | 3 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described in Tier‑1 as an existing area of applicability of the protocol (Modules can be AI models; inference is mentioned), so AI_0 as “intent only” adds no signal.
- Evidence: Tier‑1 — https://communeai.org/docs/getting-started/intro
- Why sufficient / why not (one line): AI_0 applies to “intent only”; here Tier‑1 describes the AI orientation and use cases.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The protocol coordinates Modules (including AI models/compute) and incentive mechanics where utility can be, for example, inference.
- Evidence: Tier‑1 — https://communeai.org/docs/getting-started/intro
- Why sufficient / why not (one line): The Tier‑1 introduction explicitly describes Modules and the example “inference to a model” as utility.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): The Tier‑1 documentation describes reproducible steps for participating in the network (wallet/staking, running a node) and mining/validating scenarios.
- Evidence: Tier‑1 — https://wallet.communeai.org/ ; https://communeai.org/docs/subspace/commune-blockchain ; https://communeai.org/docs/mining/what-is-mining ; https://communeai.org/docs/validating/what-is-validating
- Why sufficient / why not (one line): There is a “how‑to” for participation and running network components; AI model quality metrics (AI_3) are not recorded separately.
- 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 quality metrics are not applicable: an AI component is not established.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): Tier‑1 docs describe the architecture of Modules/Subnets and the Subspace blockchain (Substrate‑based) as the basis of the protocol.
- Evidence: Tier‑1 — https://communeai.org/docs/getting-started/intro ; https://communeai.org/docs/subspace/commune-blockchain
- Why sufficient / why not (one line): Sufficient for understanding the architecture and onchain/offchain separation.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Subspace (Commune).
- Addresses/identifiers: mainnet RPC
wss://api.communeai.net(from the documentation). - Evidence: Tier‑1 — https://communeai.org/docs/subspace/commune-blockchain
- Why sufficient / why not (one line): The Tier‑1 documentation records the existence of the network and endpoints for connecting.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: Modules (onchain identifiers), stake mechanics and governance (voting proportional to stake).
- Evidence: Tier‑1 — https://communeai.org/docs/getting-started/intro ; https://communeai.org/docs/concepts/governance
- Why sufficient / why not (one line): Tier‑1 describes onchain coordination of modules and governance, not just the existence of a token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 1
- “Replace the blockchain” test: without the blockchain, trustless coordination of the global namespace of modules, stake and governance breaks down (the protocol ceases to be a censorship‑resistant p2p system).
- Evidence: Tier‑1 — https://communeai.org/docs/getting-started/intro
- Why sufficient / why not (one line): Tier‑1 positions the system as a censorship‑resistant p2p protocol with stake economics and governance; replacing onchain changes the trust model.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The network uses a token/stake (needed for participation and voting).
- Evidence: Tier‑1 — https://communeai.org/docs/concepts/governance
- Why sufficient / why not (one line): Tier‑1 describes voting power proportional to stake and participation through tokens.
- 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 as payment for the service.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of the token’s role as payment was found.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Stake is “mined” by providing utility to validator stake (the protocol’s incentive mechanism).
- Evidence: Tier‑1 — https://communeai.org/docs/getting-started/intro
- Why sufficient / why not (one line): Tier‑1 describes a stake‑based market system and the mechanism “mined by providing subjective utility”.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): Governance: voting power is proportional to stake.
- Evidence: Tier‑1 — https://communeai.org/docs/concepts/governance
- Why sufficient / why not (one line): Tier‑1 explicitly describes voting and the dependence of voting power on stake.
- 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 per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 justification of the replaceability/irreplaceability of the token.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.communeai.org/ | Official project website (navigation to Tier‑1 materials). |
| Tier‑1 | https://communeai.org/docs/getting-started/intro | Project documentation (description per Tier‑1). |
| Tier‑1 | https://github.com/commune-ai | Tier‑1 development artifact: official GitHub organization. |
| Tier‑1 | https://communeai.org/docs/subspace/commune-blockchain | Subspace blockchain: Substrate‑based network + RPC endpoints (mainnet/testnet). |
| Tier‑1 | https://communeai.org/docs/concepts/governance | Governance: proposals/voting; voting power is proportional to stake. |
| Tier‑1 | https://wallet.communeai.org/ | Official wallet (staking/sending/operations). |
| Tier‑1 | https://communeai.org/docs/installation/setup-wallet | Instructions for the wallet (SubWallet) and operations (stake/unstake/send). |
No comments to display
No comments to display