CoinGecko Crypto Treasuries Methodology

Last updated: October 2, 2026

Understanding CoinGecko’s Crypto Treasury (DATCo) holdings dataset in detail to:

  • Use it as historic time series data on public-company digital asset treasuries
  • Track this Vs. enterprise value and premium/discount to NAV
  • Assess latency, data quality, methodology, and licensing (including internal distribution rights and delivery mechanisms)

 

1. Data Coverage & Assets

  • Focus is on entities (including public companies and governments) holding crypto in their treasuries
  • CoinGecko supports both single‑asset and multi‑asset holdings entities:
  • For each entity, CoinGecko tracks:
    • Each disclosed purchase event (delta)
    • Total cumulative holdings after that event

 

2. Sources of Truth

We emphasize a “first‑hand source only” policy:

  1. Regulatory filings
    • US: 10‑Q, 10‑K, 8‑K and similar SEC filings
    • Used as the anchor to reconcile and validate the time series
  2. Official company disclosures
    • Press releases from the company itself
    • Investor relations announcements
    • The company’s holdings dashboard on its official website
    • In some cases, when an official press release or announcement isn’t available, we may rely on social media posts from the entity’s official X account for updates
  3. Regional nuance
    • In some jurisdictions (e.g., Japan, Hong Kong), companies may not file with regulators for every treasury update, but will issue press releases
    • In those cases, CoinGecko relies on the official press release as the primary source

CoinGecko does not ingest data from:

  • Third‑party new sites or social media accounts (e.g., Twitter/X)
  • Unofficial on-chain analytics dashboards
  • Crowd‑sourced wallet tags

These may be used as signals but are not accepted as inputs to the published dataset unless backed by an official disclosure.

 

3. On‑Chain Data & Wallet Tagging

  • CoinGecko does not update treasury holdings purely based on on‑chain wallet movements
  • Even if wallets attributed (by third parties like Arkham) show inflows to, say, Strategy:
    • Holdings are not adjusted until there is an official disclosure (filing or press release)
  • Reason:
    • Wallet attribution is often self‑tagged or crowd‑sourced
    • No guarantee of 100% accuracy
    • CoinGecko prefers high‑confidence, auditable data from first-hand disclosures

 

4. Update Process & Latency

  •  CoinGecko monitor:
    • Company press releases
    • Regulatory filings
    • X posts
  • A self-serve treasury listing form and treasury update form for people to submit updates that we may have missed, and submissions are validated by CoinGecko staff, with the same criteria as above, before being introduced to our site. 
  • Refer to this guide to learn more about how to update your treasury information.

Data refresh frequency:

  • CoinGecko aims for timely updates (T+1 at best for major updates), but the required time for smaller or less frequently reported data may fluctuate depending on internal resource capacity and the official data sources available.
  • CoinGecko does not currently have 24/7 global monitoring for this dataset, and thus cannot guarantee the necessary speed for use cases requiring same-day or intra-day updates due to these intrinsic operational constraints.

 

5. Reconciliation & Error Handling

How CoinGecko checks that data is “correct”:

  • Throughout the quarter:
    • Update treasury holdings on each new press release/filing
  • When 10‑Q / 10‑K (or local equivalent) is released:
    • Compare cumulative holdings vs the reported number
    • If numbers diverge:
      • Recognize that intermediate announcements might have:
        • Batched multiple purchases
        • Omitted small purchases
        • Used inconsistent totals
        • Excluded balances earned from staking

How adjustments are done:

  • CoinGecko does not restate the entire historical time series
  • Instead:
    • CoinGecko updates the latest total holdings to match the latest official filing
    • Maintain the transaction deltas recorded from interim announcements
  • Result:
    • API will provide:
      • Per‑transaction delta (e.g., +100 BTC)
      • New total holdings (e.g., 100,100 BTC)
    • There can be cases where:
      • The sum of historical deltas ≠ latest total
      • CoinGecko effectively adds a manual adjustment at the point of reconciliation to bring the total in line with filings

CoinGecko accepts that perfect reconciliation is sometimes impossible where disclosures are incomplete or inconsistent, and prioritizes aligning the current total to the best available official figure.

 

6. Data Delivery Mechanism (Today - 2026)

For the treasury dataset today:

  • Delivery is via REST API only:
    • Endpoints include:
      • Full transaction‑level records (deltas)
      • Total holdings per disclosure date
  • No current support for:
    • Push‑based feeds
    • S3 / Snowflake / flat‑file dumps

 

If you have any questions or concerns, please do not hesitate to submit a support ticket.