{
  "url": "https://blockindex.ai/coin/ccd",
  "name": "Concordium",
  "links": {
    "github": "https://github.com/Concordium",
    "website": "https://www.concordium.com/",
    "whitepaper": "https://www.concordium.com/whitepaper"
  },
  "dScore": 61,
  "market": {
    "priceUsd": 0.00427012963241739,
    "marketCapUsd": 53865261.44576298,
    "volume24hUsd": 508713.35002487,
    "priceChange7dPct": -4.9731302,
    "priceChange24hPct": -5.6885435
  },
  "source": "BlockIndex.AI",
  "supply": {
    "max": null,
    "circulating": 12614432366.838701,
    "circulatingPct": null
  },
  "ticker": "CCD",
  "founder": "Lars Seier Christensen",
  "vcFunded": true,
  "updatedAt": "2026-06-19T12:00:20.365993+00:00",
  "fairLaunch": false,
  "launchYear": 2018,
  "description": "Concordium (CCD) is an identity‑first Layer‑1 blockchain designed to serve compliance‑oriented and enterprise use cases by embedding identity and privacy preserving cryptography directly into the protocol. Launched in 2018 and supported by a foundation and academic collaborators, Concordium positions itself as a payments‑grade settlement layer — branded as “PayFi” — with protocol‑level identity and zero‑knowledge proof (ZKP) capabilities that enable users to prove attributes (such as age or jurisdiction) without revealing personally identifiable information. The design philosophy centers on offering programmable, auditable digital money (Protocol‑Level Tokens, or PLTs) that reduce reliance on smart contracts for asset issuance and instead provide first‑class token primitives within the consensus layer.\n\nTechnically Concordium implements a fork‑free BFT‑style Proof‑of‑Stake consensus (ConcordiumBFT, HotStuff‑inspired) focused on fast finality (2–4 seconds) and high throughput (documented support up to 2,000 TPS). The protocol surface includes PLTs that are issued at the consensus layer and support features like multi‑party locks, scheduled transactions and jurisdictional restrictions, reducing smart‑contract attack surface for issuers. The stack is explicitly designed for identity‑aware transactions: identity attributes are encrypted and can be revealed or attested via ZKPs to counterparties or compliance systems, enabling regulated flows while preserving user confidentiality. Concordium’s architecture and research partnerships (including academic cryptographers) provide the cryptographic pedigree cited in project materials.\n\nFrom an ecosystem perspective Concordium emphasizes regulated adoption: the protocol supports native PLT stablecoins and has multiple integrations into wallets and exchanges. The project has seen native stablecoin issuance on L1 (April 22, 2025) and a series of partnerships and exchange listings throughout 2025–2026 that reflect a strategic push toward PayFi. Wallet support spans hardware (Ledger), desktop and mobile clients (official Concordium desktop/mobile wallets) and popular connectors, improving on‑ramp options for institutions and retail users. Exchange coverage includes tier‑1 centralized venues and at least one DEX listing, broadening market access for CCD. The Concordium Foundation and affiliated research teams steer development and ecosystem coordination rather than an on‑chain DAO model.\n\nTokenomics and market signals are consistent with a mature Layer‑1: total supply is reported at ~14.17B CCD with circulating supply in the ~11.7–11.8B range. Market snapshots in the provided material show a live price near $0.01135 with a market cap in the low hundreds of millions of USD and historical volatility including an ATH in Feb 2022 and cycle lows in 2024. Explicit premine/PIP values and a granular emission schedule were not documented in the supplied files; governance appears foundation‑led and off‑chain, while investor and partnership activity in 2025 signals growing institutional engagement as the project pursues regulated stablecoin rails and enterprise payments integrations.",
  "methodology": "https://blockindex.ai/dscore",
  "classification": {
    "layer": "Layer 1",
    "isToken": false,
    "consensus": "PoS",
    "parentChain": null
  },
  "dScoreComponents": {
    "autonomy": 5,
    "ageHistory": 13,
    "governance": 15,
    "nodeDistribution": 28,
    "initialDistribution": 0
  },
  "decentralizationVerdict": "Decentralized"
}