Skip to main content

Covalent

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

Covalent — an AI/Data project, token (symbol: CXT; formerly CQT).

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: blockchain data infrastructure/service (API/tools) for developers; the website separately positions it as data for AI/agents.
  • Who it’s for: developers of onchain applications and services that need structured onchain data.
  • Why onchain/token: per the Tier‑1 Covalent Network documentation, the CXT token is used for operator/delegator staking and governance; the onchain part includes token/staking contracts (Ethereum) and the ProofChain contract (Moonbeam).

How it works (very briefly)

  1. The user does: requests data through the project’s API/SDK/tools.
  2. The system does: aggregates/structures onchain data across multiple networks (per the project’s claim).
  3. The user gets: structured data for an application/analytics.
  4. Where the blockchain is: data processing/indexing — offchain infrastructure; settlement/staking and some confirmations of work — onchain (Ethereum/Moonbeam).
  5. Token role (if any): CXT is the Covalent Network token for staking and governance (Tier‑1 docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name Covalent
Also known as (aliases) CQT
Logo (logo) ../assets/718_covalent_logo.svg
Token symbol (ticker) CXT
Category AI/Data | 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 0x7ABc8A5768E6bE61A6c693a6e4EAcb5B60602C4D
Token model (token_type) utility (network access + staking + governance)
Max supply 1 000 000 000 CXT (minted at genesis)
Issuance —
Tokenomics (tokenomics, brief) —
Governance offchain voting (Snapshot)
Admins/keys —
Audit yes
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) data for AI + agents
Use‑case (use_case) on-chain data API for apps
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 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Covalent provides access to structured blockchain data through API/SDK/tools. On the website, the project is positioned as data infrastructure useful for AI and agent applications. However, its own AI mechanics “inside” the product are not described per Tier‑1 sources (rather, it is data infrastructure used by AI/agents).

Per the Tier‑1 Covalent Network documentation, the CXT token is used for operator/delegator staking and governance; the documentation also lists onchain contracts (Ethereum/Moonbeam) related to staking and publishing proofs.

Features/modules

  • GoldRush: a set of tools/SDK/API for developers (per the project’s claim).
  • Support for multiple networks: coverage of 100+ blockchains is claimed.

Typical scenarios

  • Scenario 1: a developer requests data → receives a structured response through API/SDK.
  • Scenario 2: a developer builds an application/analytics → uses the project’s data as a source.

Getting started (wallet/network)

  • What you need: access to the project’s API/documentation.
  • Network/chain: Ethereum (CXT token/staking); Moonbeam (ProofChain).
  • Fees: Ethereum network fees (gas) for token transactions.

Architecture/tech (non‑AI)

  • Components: offchain data infrastructure (indexers/storage/API); onchain token/staking contracts (Ethereum) and ProofChain (Moonbeam).
  • Participant roles: data developers/users, token holders.
  • Where logic runs: processing/indexing — offchain; settlement/staking/some confirmations — onchain.
  • Dependencies: infrastructure/nodes of the supported networks (for reading data), Ethereum/Moonbeam (for the network’s onchain contracts).

Token/economics (expanded, no forecasts)

  • Token utility: per the Tier‑1 documentation, CXT is a governance token and a staking asset for operators/delegators that keep the network running.
  • Protocol necessity drivers: —.
  • Who pays fees: users of the Ethereum network for token transactions.
  • Where fees go: to Ethereum validators/stakers (at the network level).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: there is a public page with audits (see links_*).
  • Bug bounty: there is a public bounty repository (see links_*).
  • Incidents: —.
  • Threat model: indexing/data infrastructure risks + standard ERC‑20 token risks.

Project status and timeline

  • Current status: active (based on product availability and repositories).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? The project positions the product as data infrastructure for AI/agents, but its own AI module inside the product is not described per Tier‑1.
  • What is truly onchain? Token/staking contracts (Ethereum) and the ProofChain contract (Moonbeam) for confirmations of operators’ work (Tier‑1 docs).
  • Why is a token needed? CXT is used for staking and governance in Covalent Network (Tier‑1 docs).
  • Red flags (based on the information found): AI positioning without a tech description of an AI module; “data for AI” must not be confused with “AI inside the protocol”.

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 medium 2
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 project is positioned as infrastructure for AI and agent applications (“Agents need data”).
  • Evidence: Tier‑1 — https://www.covalenthq.com/
  • Why sufficient / why not (one line): The Tier‑1 website directly links the product to AI/agents as the target application.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): An AI module of its own inside the product is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): At the Tier‑1 level, there is positioning “for AI/agents”, but no description of what exactly AI does inside the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A demo of an AI component is not established (demos of data tools are possible, but not of an AI module).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): AI_2 requires a demo of AI in operation; no Tier‑1 demo of an AI module was found.
  • 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 were not found.
  • 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 part (model/versions) is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 documentation with AI module architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum; Moonbeam
  • Addresses/identifiers: CXT ERC‑20: 0x7ABc8A5768E6bE61A6c693a6e4EAcb5B60602C4D; CXT staking: 0xfe97b0C517a84F98fc6eDe3CD26B43012d31992a; ProofChain (Moonbeam): 0x7487b04899c2572A223A8c6eC9bA919e27BBCd36
  • Evidence: Tier‑1 — https://www.covalenthq.com/docs/resources/contract-addresses
  • Why sufficient / why not (one line): The Tier‑1 page with contract addresses records onchain artifacts of the network (Ethereum/Moonbeam).
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: operator/delegator staking (Ethereum) and the ProofChain contract for publishing proofs of operators’ work (Moonbeam).
  • Evidence: Tier‑1 — https://www.covalenthq.com/docs/resources/contract-addresses ; https://www.covalenthq.com/docs/resources/operator-faq
  • Why sufficient / why not (one line): Tier‑1 documentation describes onchain contracts and their role in the operation of the network, not just token issuance.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that the product breaks down without onchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no justification of onchain criticality per Tier‑1/2.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, CXT (ERC‑20) on the Ethereum network.
  • Evidence: Tier‑1 — https://www.covalenthq.com/docs/resources/contract-addresses
  • Why sufficient / why not (one line): The token contract is available onchain.
  • 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): Per the Tier‑1 documentation, CXT is described as a settlement/staking/governance token, not a “payment token” for direct API payment.
  • Evidence: Tier‑1 — https://www.covalenthq.com/docs/cxt/overview
  • Why sufficient / why not (one line): In the Tier‑1 documentation, there is no claim that a user “pays in CXT” directly; a scenario with a stablecoin and market buy is described.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): CXT is staked by operators/delegators to secure the network and receive rewards.
  • Evidence: Tier‑1 — https://www.covalenthq.com/docs/cxt/overview ; https://www.covalenthq.com/docs/cxt/tokenomics
  • Why sufficient / why not (one line): Tier‑1 documentation directly describes staking as a function of the token and a network security mechanism.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): CXT is used for voting on proposals (governance) in Covalent Network (Snapshot process).
  • Evidence: Tier‑1 — https://www.covalenthq.com/docs/resources/governance ; https://www.covalenthq.com/docs/cxt/tokenomics
  • Why sufficient / why not (one line): Tier‑1 documentation sets voting rules and records the role of the token as a governance token.
  • 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.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no data to justify replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.covalenthq.com/ Positioning of the product as data infrastructure (including for AI/agents) and a description of data products.
Tier‑1 https://www.covalenthq.com/docs/cxt/overview The role of the CXT token: staking and governance; description of “infrastructure currency/settlement”.
Tier‑1 https://www.covalenthq.com/docs/resources/contract-addresses Addresses of the CXT (Ethereum), staking (Ethereum) and ProofChain (Moonbeam) contracts; CQT is listed as deprecated.
Tier‑1 https://www.covalenthq.com/docs/resources/operator-faq Minimum staking requirements for operators and an explanation of why proofs are published on Moonbeam.
Tier‑1 https://www.covalenthq.com/docs/resources/governance The governance process and voting rules (Snapshot), including “1 CXT = 1 vote”.
Tier‑1 https://www.covalenthq.com/docs/resources/audits Public audits page (security artifact).
Tier‑2 https://coinmarketcap.com/currencies/covalent/ Token profile (for reference; not proof of technology).

No comments to display

Back to top