Skip to main content

Chromia

Chromia (CHR) — 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).

Chromia — an AI/Other | Infra L1 “relational blockchain” platform for dApp chains (sidechains) and Rell smart logic; the Roadmap has a separate “blockchain enabled AI” track (AI extensions: inference/vector DB/memory for agents). Token: CHR (ERC‑20; used for hosting fees, provider stakes, etc. — Tier‑1).

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 L1 platform for dApps, where data and state are stored in a relational DB (PostgreSQL) and applications run as separate “dapp chains”.
  • Who it’s for: developers of dApps/games/DeFi and teams that value fast queries/indexing and separate chains per application.
  • Why onchain/token: onchain is needed as a shared database + consensus (PBFT‑style, anchoring in a PoW network); the CHR token is used to pay hosting fees and for provider staking (Tier‑1).

How it works (very briefly)

  1. The user does: interacts with a dApp (web/mobile), sends transactions and queries.
  2. The system does: the validators of the specific dApp chain execute the Rell logic and record the state in the relational DB, reaching BFT consensus.
  3. The user gets: fast confirmations and the ability to run complex queries against the state of the dApp chain.
  4. Where the blockchain is: separate dapp chains + system chains; anchoring in a PoW chain strengthens finality.
  5. Token role: CHR is used as the economic layer (hosting fees for dApps, provider stakes/collateral, etc.; Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Chromia
Also known as (aliases) Chromapolis (legacy name) | CHR
Logo (logo) ../assets/59_chromia_logo.png
Token symbol (ticker) CHR
Category AI/Other | Infra
Primary chain (chain) Chromia
Type Appchain
Network status mainnet
Consensus (consensus) PBFT-style (Chromia; Postchain)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x8a2279d4a90b6fe1c4b30fa660cc9f926797baa2
Token model (token_type) utility (payments + staking + governance)
Max supply 571,051,090.121661 (Etherscan “Max Total Supply”)
Issuance fixed cap (conflict noted)
Tokenomics (tokenomics, brief) The whitepaper (2019) describes a 1B limit and the distribution; Etherscan shows a “Max Total Supply” of 571.051M (conflict between sources).
Governance provider governance (whitepaper)
Admins/keys —
Audit yes
Bug bounty —
Team (team) ChromaWay / Chromia Devcenter (whitepaper: initial centralization)
Funding (investors/funding) —
AI component (ai_component) AI extensions (inference/vector DB/memory)
Use‑case (use_case) relational L1 for dApp chains + fast queries
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

Chromia is an L1 platform for decentralized applications that emphasizes storing state in a relational DB (PostgreSQL) and the fact that each application has its own chain (dapp chain). The idea is to give dApps fast queries/indexing “out of the box” and to scale horizontally via a set of chains.

The whitepaper (2019) describes the architectural elements: Postchain, PBFT‑style consensus and an anchoring mechanism in a PoW network to strengthen finality. The Roadmap (Tier‑1) also has a separate “blockchain enabled AI” track (for example, AI Inference Extension, Vector DB Extension, Neural Interface for AI agents) — mostly as a plan/intent.

Features/modules

  • Relational model: the state and data of dApps are stored in a relational DB; fast queries/indexing.
  • Dapp chains / sidechains: separate chains per application, horizontal scaling.
  • Rell: a specialized language for the “relational” logic of dApps.
  • Anchoring: strengthening finality via anchoring in a PoW chain (described in the whitepaper).
  • Extensions (roadmap): modular containers/extensions, including the AI direction (Tier‑1 roadmap).

Typical scenarios

  • Scenario 1 (dApp team): writes the dApp backend in Rell → deploys a dapp chain → gets fast queries/confirmations and its own fee model.
  • Scenario 2 (user): uses an application that stores data onchain and queries it quickly (games/DeFi/social apps).
  • Scenario 3 (AI intent): use the Python client and “AI extensions” for AI agents/vector search/inference (per the Roadmap; the demo is a separate milestone).

Getting started (wallet/network)

  • What you need: development tools (Chromia CLI) + the documentation/whitepaper (see links_*).
  • Network/chain: Chromia (the main network) + the CHR ERC‑20 token on Ethereum for liquidity/integrations.
  • Fees: the whitepaper describes hosting fees (paid by the dApp as a whole) and an application‑level fee model.

Architecture/tech (non‑AI)

  • Components: Postchain (the core), system chains (directory/root/token root/anchoring), dapp chains, SDK/CLI, bridges (see the audits summary).
  • Participant roles: providers (nodes/validators), dApp developers, application users.
  • Where logic runs: the Chromia L1 (dapp chains + system chains); anchoring uses external PoW networks (described in the whitepaper).
  • Dependencies: PostgreSQL (as part of the Postchain design), external chains for anchoring/bridging (whitepaper + audit summary).

Token/economics (expanded, no forecasts)

  • Token utility: the whitepaper describes CHR as the token for hosting fees (dApps pay the nodes), the “standard currency” of the ecosystem and provider stakes (provider collateral/stake).
  • Protocol necessity drivers: provider staking/collateral and payment of hosting fees are built into the platform’s economy.
  • Who pays fees: per the whitepaper, the dApp as a whole pays hosting fees; users may pay fees according to the rules of the specific application.
  • Where fees go: to providers/nodes (node compensation) + system pools (described in the whitepaper).
  • Issuance/burn: the whitepaper (2019) describes a limit of 1B tokens; Etherscan shows a different “Max Total Supply” (see the passport; conflict).
  • Security/incentive mechanisms: provider stake/collateral + economic incentives (whitepaper); security risks and mitigations are partially reflected in the audit summary.
  • Distribution and token issuance schedule: available in the whitepaper (percentages + unlock schedule; see the source).
  • Treasury: the whitepaper describes system accounts/pools (public good, dev pool, etc.).

Governance

  • Who makes decisions: the whitepaper describes governance via providers (provider governance) and a transition from initial centralization to a more decentralized model.
  • How protocol parameters change: via governance mechanisms (described at the whitepaper level; for details of the current process, see the official resources).
  • Where decisions are discussed/made: — (not extracted per Tier‑1).
  • Keys/multisig: —.

Security and incidents

  • Audits: there is a summary of external audits by Cure53 / Trail of Bits / Quantstamp and HackNet (Tier‑1 blog).
  • Bug bounty: — (there is no Tier‑1 program page in links_*).
  • Incidents: — (not found per Tier‑1).
  • Threat model: BFT consensus + the risk of validator collusion/compromise; anchoring as a strengthening of finality (whitepaper).

Project status and timeline

  • Current status: mainnet (per the official description/resources).
  • Key releases/milestones: CLI releases are published in the release notes; the roadmap is updated quarterly.
  • Roadmap: published at chromia.com/roadmap (Tier‑1).

Ecosystem/integrations

  • Integrations: the dev toolchain (CLI), bridges (mentioned in the audit summary), the planned Extensions SDK/Marketplace (roadmap).
  • Partners: — (not extracted per Tier‑1).
  • Where it’s actually used: — (a separate overview of the ecosystem’s dApps is needed; outside the current overview).

AI component of the project

  • What is real AI here? per the Tier‑1 Roadmap: Extensions for AI inference, a vector DB and a “memory bank” for AI agents are planned/being developed; also the Python client as an integration layer.
  • What is truly onchain? the Chromia L1 (dapp chains + system chains), PBFT‑style consensus and anchoring (whitepaper).
  • Why is a token needed? per the whitepaper, CHR is needed for hosting fees (paying the nodes), provider staking/collateral and the ecosystem economy.
  • Red flags (based on the information found): AI‑washing — moderate risk (there is a Tier‑1 roadmap, but the demo/metrics are still ahead); what to double‑check: the existence of a public testnet demo (Q3/2025 in the roadmap), the current status of the AI extensions and documentation.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity high 3
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the Roadmap has explicit AI milestones: AI Inference Extension, Vector Database Extension, Neural Interface for AI agents, AI Inference Testnet Demo.
  • Evidence: Tier‑1 — https://chromia.com/roadmap
  • Why sufficient / why not (one line): this is a Tier‑1 roadmap/plan, but not proof of a working AI component right now.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): the Roadmap describes “what will be done” by AI inference/VectorDB/Neural Interface, but these are intentions; the current AI functionality as a product is not confirmed by a Tier‑1 demo/SDK in links_*.
  • Evidence: Tier‑1 — https://chromia.com/roadmap
  • Why sufficient / why not (one line): without a reproducible current AI product we record 0.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): the Roadmap contains a future “AI Inference Testnet Demo” milestone, but no current Tier‑1 demo/quickstart for the AI part was found in links_*.
  • Evidence: Tier‑1 — https://chromia.com/roadmap
  • Why sufficient / why not (one line): a plan ≠ a demo; therefore AI_2=0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://chromia.com/roadmap
  • Why sufficient / why not (one line): metrics/benchmarks of AI inference/VectorDB are not published in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a technical description of the AI extensions was not extracted from the Tier‑1 links available in the card; there are only roadmap milestones.
  • Evidence: Tier‑1 — https://chromia.com/roadmap
  • Why sufficient / why not (one line): without a document/repository on the AI extensions we record 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Chromia (L1) + Ethereum (CHR ERC‑20)
  • Addresses/identifiers: CHR ERC‑20: 0x8a2279d4a90b6fe1c4b30fa660cc9f926797baa2
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf, https://etherscan.io/token/0x8a2279d4a90b6fe1c4b30fa660cc9f926797baa2
  • Why sufficient / why not (one line): there is a Tier‑1 whitepaper on the network + the onchain fact of the token in the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: dapp chains (sidechains) with Rell logic and consensus; system chains (directory/root/anchoring, etc.).
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf
  • Why sufficient / why not (one line): the whitepaper describes the platform’s onchain architecture (not reducible to the token).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain consensus/data, the platform ceases to be a “decentralized database” for dApps (the core meaning of Chromia per the whitepaper).
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf
  • Why sufficient / why not (one line): the onchain part = the foundation of 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, CHR (ERC‑20), and a described role of the token in the platform’s economy.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x8a2279d4a90b6fe1c4b30fa660cc9f926797baa2, https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf
  • Why sufficient / why not (one line): the token is confirmed onchain, the roles are described in the whitepaper.
  • 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): whitepaper: CHR is used by dApps to pay hosting fees (node compensation).
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf
  • Why sufficient / why not (one line): the token economics section explicitly lists the roles of the token, including fees.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): whitepaper: providers are required to hold a CHR stake as collateral; the roadmap also speaks of Native Staking.
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf, https://chromia.com/roadmap
  • Why sufficient / why not (one line): stake/collateral is described as an incentive/security mechanism.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the whitepaper describes governance (at the level of providers and system mechanisms); the roadmap contains a “Chromia Governance” milestone (native CHR stakers).
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf, https://chromia.com/roadmap
  • Why sufficient / why not (one line): Tier‑1 sources link governance to staking/providers.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): per Tier‑1, the token is built into fees + provider stake + governance; we do not draw a strict conclusion about replaceability.
  • Evidence: Tier‑1 — https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf
  • Why sufficient / why not (one line): given explicit token roles we record 0 (conservatively).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://a.storyblok.com/f/203563/x/41527f8df4/chromia-platform-whitepaper-2019-en.pdf Tier‑1: the Chromia architecture (relational L1, dapp chains, PBFT‑style, anchoring) + the roles of the CHR token (hosting fees, provider stakes, governance) and token distribution (limit 1B).
Tier‑1 https://chromia.com/roadmap Tier‑1: roadmap, including AI milestones (AI inference/vector DB/memory, Python client, AI testnet demo) and governance/staking plans.
Tier‑1 https://docs.chromia.com/cli/cli-release-notes Tier‑1: active development of tooling (Chromia CLI release notes).
Tier‑1 https://blog.chromia.com/exec-summary-audits-and-hacknet/ Tier‑1: summary of the audits (Cure53/Trail of Bits/Quantstamp) and HackNet + links to the full reports.
Tier‑1 https://etherscan.io/token/0x8a2279d4a90b6fe1c4b30fa660cc9f926797baa2 Tier‑1: the onchain fact of the CHR ERC‑20 token (address, decimals, holders, max total supply per Etherscan).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top