Civic

What is Civic?

Civic is an application-layer identity and authorization infrastructure project whose CVC token is associated with a long-running effort to make digital identity reusable across wallets, applications, and now AI-agent workflows, rather than forcing every application to run its own fragmented login, KYC, bot-resistance, or credentialing stack. Its core problem is not block production or settlement; it is the trust layer above blockchains and software agents: proving that a user, wallet, or automated agent has the right identity attributes and permissions without exposing more personal data or authority than necessary.

Civic’s defensible position, to the extent it has one, comes from its accumulated identity-verification history, developer tooling, and integrations around Civic Auth, Civic MCP, delegated access, audit trails, and revocation controls, not from a new consensus mechanism or a high-TVL DeFi primitive. (civic.com)

Civic’s market position is best understood as a niche identity and access-control network with a tradable legacy utility token, rather than a dominant Layer 1 or a DeFi protocol with balance-sheet-like assets locked in contracts. As of mid-September 2026, third-party market data placed CVC around the low hundreds by market capitalization, with CoinGecko showing roughly a mid-$30 million market cap and a rank near the 600 range, while the supplied asset snapshot similarly placed market capitalization at about $34 million; those figures are volatile and should be treated as a timestamped liquidity snapshot, not as a measure of product usage.

TVL is not a useful primary metric for Civic because it does not operate like a lending market, DEX, liquid-staking protocol, or collateralized credit system; the more relevant but less transparent metrics are active integrations, credentials, wallets, developers, customers, and authentication events. Civic itself claimed in 2026 that it had verified millions of identities, issued hundreds of thousands of wallets, served 500-plus customers, and had 2,000-plus developers building on its MCP gateway and Auth tools, but those are company-reported scale indicators rather than independently auditable daily-active-user figures. (coingecko.com)

Who Founded Civic and When?

Civic was co-founded in 2015 by Vinny Lingham and Jonathan Smith, with Civic Technologies, Inc. serving as the U.S.-based company behind the project. The original launch came before the 2017 ICO boom fully peaked, at a time when blockchain identity, self-sovereign identity, and utility-token marketplaces were being promoted as alternatives to centralized data brokers and repeated KYC checks. The project later sold CVC in 2017, during the broader token-sale cycle that funded many application-layer Ethereum projects before product-market fit had been established. A 2025 crypto-asset statement prepared for Kraken identified Lingham and Smith as the co-founders, Chris Hart as chief executive, Daniel Kelleher as chief technology officer, and Lingham as co-founder and chairman, while CoinGecko’s Civic profile also traces the project’s origin to 2015. (assets-cms.kraken.com)

The project’s narrative has changed materially over time. The initial Civic thesis centered on a blockchain-based identity-verification marketplace in which users could reuse attested personal information and CVC would help compensate validators and service providers. By 2019, Civic separated the broader identity marketplace concept into Identity.com as an independent nonprofit, underscoring that the original decentralized identity-marketplace vision would not remain solely inside Civic Technologies. By 2024 and 2025, the emphasis had shifted toward Civic Pass, reusable credentials, Solana permissions, embedded wallets, and Auth; in 2025 Civic announced that major Civic Pass functions would be sunset and that resources would move toward Civic Auth and agentic-AI identity. By 2026, the company’s public positioning had moved further toward AI-agent governance and signal-based go-to-market agents built on Civic MCP and Auth, a pivot that gives the business a clearer enterprise-software angle but also widens the analytical gap between the operating company’s products and CVC token value accrual. civic.com

How Does the Civic Network Work?

Civic is not a Layer 1 blockchain and does not have an independent proof-of-work, proof-of-stake, delegated-proof-of-stake, DAG, or BFT validator consensus system of its own. CVC is an ERC-20 token originally deployed on Ethereum, with additional representations listed for networks such as Polygon PoS and Energi in the supplied contract data, so token settlement inherits the security assumptions of the chain on which a given representation resides. On Ethereum, CVC transfers depend on Ethereum’s proof-of-stake validator set, finality, MEV environment, smart-contract execution, and bridge or wrapper assumptions where cross-chain versions are involved; on Polygon PoS, they inherit Polygon’s validator and bridge architecture; on Energi, they inherit Energi-specific execution and consensus assumptions. In practical terms, Civic’s “network” is an application and credentialing layer that uses blockchains for token accounting and, in certain products, wallet-linked attestations, not a sovereign settlement network with its own validator economics.

Technically, Civic’s current stack is centered on authentication, authorization, credential presentation, embedded wallets, and controlled delegation. Civic Auth supports Web2-style login and Web3 wallets, including Ethereum and Solana embedded-wallet flows, while its documentation describes OAuth 2.0 token exchange, federated identity-provider integration, scoped access, and delegated tokens for AI agents or unattended workflows. In 2025 and 2026, the changelog and product posts showed a series of security and developer-tooling upgrades, including passkey support, dynamic client registration for MCP servers, OAuth client-credentials flows, token exchange, account linking, Python support, programmatic account creation, and security hardening. Civic’s AI-agent architecture is based on putting Civic between an agent and external tools, where it can scope permissions, log calls, enforce guardrails, and revoke access through a kill switch; this is closer to an identity-control plane than to a decentralized validator network. (civic.com)

What Are the Tokenomics of cvc?

CVC has a fixed maximum supply of 1 billion tokens, making it structurally non-inflationary unless a future migration or new token contract were introduced through a separate governance or issuer action. The original allocation, according to the Kraken crypto-asset statement, was 22% to private-sale and early investors, 11% to the public sale, 33% to Civic Technologies with vesting over three years, 33% to a fund controlled by Civic, and 1% to token-sale costs; the same document stated that the company allocation was fully vested in 2020. Supply reporting has not always been perfectly uniform across data vendors, but by mid-September 2026 CoinGecko reported both circulating supply and total supply at 1 billion CVC, while Etherscan’s token page has historically shown a 1 billion max total supply. There is no prominent live emissions schedule comparable to a proof-of-stake reward curve, nor is there a widely advertised protocol burn mechanism that systematically reduces supply as usage grows. (assets-cms.kraken.com)

The harder question is not supply but value accrual. Historically, CVC was designed as a utility token for the Civic identity ecosystem, including payments or rewards around identity attestations and validation; Kraken’s asset statement describes CVC as historically used to reward validators for attesting to identity attributes and to facilitate transactions between identity-marketplace participants. However, the same statement explicitly notes that Civic Auth does not currently rely on CVC for sign-in or wallet creation, which is a critical qualification for investors because the fastest-moving Civic products may not create direct token demand. In the absence of mandatory CVC staking for access, an explicit fee sink, a burn, or a transparent revenue-share mechanism, token value depends less on product usage mechanically flowing to holders and more on whether Civic reintroduces or expands token utility in a credible way. That creates a classic application-token risk: the company may succeed as identity or agent-security middleware while CVC captures only limited economic value unless the token becomes necessary for permissions, attestations, staking, settlement, or governance. (assets-cms.kraken.com)

Who Is Using Civic?

CVC trading volume should not be confused with Civic product adoption. Exchange turnover reflects speculative liquidity, market-maker activity, listings, and short-term narratives around identity or AI agents; it does not prove that a large number of dApps are paying for credentials or that CVC is being used in production workflows. On-chain holder counts and transfers likewise capture token ownership rather than active identity verifications, and many large balances may sit with exchanges, custodians, market makers, or dormant wallets. Civic’s actual utility footprint is better inferred from integrations around Civic Auth, embedded wallets, MCP gateways, reusable credentials, anti-bot controls, and permissioning use cases across Solana, Ethereum-adjacent ecosystems, gaming, compliance-oriented dApps, and agentic workflows. Civic’s 2025 update cited hackathon usage across Solana, XDC, Ethereum events, games, group payments, and RWA-related projects, but those are developer-adoption signals rather than hard recurring-revenue or active-user disclosures. (etherscan.io)

The strongest identifiable ecosystem adoption has been around identity and attestation infrastructure rather than broad consumer usage of CVC itself. Civic joined the Solana Attestation Service, a credential system for issuing and verifying KYC, professional, compliance, and identity attestations on Solana, and Civic’s own SAS announcement described reusable verifications for wallets, proofs of personhood, KYC/KYB-style checks, anti-Sybil controls, sanctions screening, and accredited-investor-style credential types. The SAS website lists Civic among trusted participants, and Civic’s 2025 update noted media coverage of its role in permissioning infrastructure and interoperability across Solana. Separately, Civic’s 2026 company page claims 500-plus customers, millions of identities verified, and hundreds of thousands of wallets issued; those figures support the view that Civic has operated real identity infrastructure, but they still do not disclose how much of that usage requires CVC or translates into token-denominated fees. civic.com

What Are the Risks and Challenges for Civic?

Civic’s first major risk is regulatory ambiguity. CVC emerged from the 2017 ICO era, and a private securities class action filed in 2020 alleged that Civic and its officers offered and sold CVC as unregistered securities; the Stanford Securities Class Action Clearinghouse records that the case was voluntarily dismissed on or around April 27, 2021, so that proceeding does not appear to be an active merits judgment against Civic. Still, dismissal of a private suit is not the same as a definitive U.S. regulatory classification, and Civic has no CVC spot ETF or commodity-style regulatory safe harbor. Kraken’s Canadian due-diligence statement said CVC was unlikely to be a security or derivative under Canadian securities legislation, but that analysis is jurisdiction-specific and platform-specific. Centralization risk is also nontrivial: Civic’s products are largely company-operated software services, not autonomous public infrastructure, and the historical token allocation gave large shares to Civic Technologies and a Civic-controlled fund. Users and developers therefore take issuer, product-continuity, compliance, and service-availability risk in addition to ordinary smart-contract and chain-settlement risk. (securities.stanford.edu)

The competitive landscape is broad and economically unforgiving. In crypto identity, Civic competes with on-chain credential issuers, proof-of-personhood systems, wallet-attestation standards, KYC vendors, compliance APIs, and projects such as Ontology, Metadium, SelfKey, and other decentralized-identity providers referenced in Kraken’s risk statement. In AI-agent authorization, Civic is not only competing with crypto-native identity projects but also with enterprise identity and access-management vendors, OAuth and OIDC tooling providers, policy engines, secret-management platforms, MCP gateways, and cloud-native security vendors that may already control customer procurement channels. This is a structurally difficult market because identity buyers value trust, compliance, integrations, and liability allocation more than token alignment, and because many customers may prefer a conventional SaaS contract over a token-mediated network.

The main economic threat to CVC is therefore not just that Civic loses users, but that Civic wins users through products that abstract away or bypass the token. (assets-cms.kraken.com)

What Is the Future Outlook for Civic?

Civic’s near-term outlook depends on whether it can turn its identity history into a durable role in AI-agent governance and multi-chain credentialing without leaving CVC economically stranded. Verified recent roadmap and upgrade signals point toward Auth and MCP rather than a CVC protocol fork: Civic’s 2025 and 2026 changelog shows passkeys, OAuth enhancements, dynamic client registration, MCP tool authorization, token exchange, programmatic account creation, Python support, and security hardening, while the company’s 2025 Civic Pass update confirmed a strategic shift away from Pass toward Civic Auth and agentic-AI identity.

The current infrastructure thesis is plausible because agents that touch Gmail, Slack, Stripe, databases, CRMs, wallets, or internal APIs need scoped permissions, auditability, and emergency revocation.

The investment problem is that the strongest product-market-fit path may look like enterprise middleware revenue rather than token-mediated network demand, so the future of CVC specifically depends on whether Civic can create transparent, necessary, and regulatorily durable token utility around credentials, permissions, staking, or ecosystem settlement. (docs.civic.com)