Circulating supply verification on CoinGecko and CoinMarketCap

What does circulating supply verification cover?

Circulating supply verification explains which tokens are treated as available to the market and how that figure is derived. It is not simply a tokenomics headline: a reviewer needs to understand the supply calculation, the status of excluded balances, and the evidence behind each classification.

A sound submission connects your published supply figure to the token’s actual mechanics. We map relevant contract balances and project-controlled allocations, then describe why particular tokens are circulating or excluded. Depending on the project, this may include vesting contracts, locked liquidity, treasury holdings, team allocations, staking arrangements, burns, or bridge representations. We do not assume that a label alone proves a balance is unavailable; the explanation must fit how tokens can move in practice.

This service is useful when a project is preparing for a tracker review, has a supply figure that differs across sources, or needs to update its records after a tokenomics change. It also helps establish a repeatable basis for future updates, rather than treating verification as a one-time form submission.

If your wider objective is to establish or update a tracker profile, review CoinGecko listing support alongside this work. For context on the full listing and verification workflow, see Listings and verification.

What evidence should you prepare for CoinGecko supply verification?

Prepare evidence that lets a reviewer follow the supply calculation from the token contract to the figure you report. The CoinGecko supply verification process is easier to assess when the explanation, public tokenomics, and verifiable addresses agree.

Before submission, assemble a concise evidence folder with:

• The token contract address, chain, and relevant explorer links.
• The current total and circulating supply figures, with a written calculation.
• Addresses and balances for locked, vested, treasury, or otherwise excluded tokens.
• Vesting schedules, lock terms, or contract documentation that explains restrictions.
• A description of burns, emissions, bridge representations, and any supply changes.
• Public tokenomics or documentation that matches the figures in the request.

For each excluded balance, state who controls it, whether it can move, and what event could make it available. If tokens are locked only until a specific condition or date, describe that condition rather than calling them permanently unavailable. For wrapped or bridged assets, clarify how the representation relates to the original supply so a reviewer can understand whether counting both would overstate the figure.

Check that the project website, tracker profile, tokenomics materials, and submission use the same terminology. If the contract or project identity has changed, resolve that context before sending the request; contract migration and rebranding updates may be relevant.

How to verify supply on CoinGecko and CoinMarketCap

To verify supply on CoinGecko or CoinMarketCap, make the calculation auditable, submit it through the relevant platform process, and respond to questions with evidence tied to specific balances. The platforms review their own data and make their own decisions; our role is to make your case clear and manage the project-side work.

We begin by reconciling the figures you currently publish with contract data and tokenomics documents. Next, we build a supply schedule that distinguishes circulating tokens from excluded allocations and records the evidence for each category. We then check the project’s public information for conflicting figures or outdated descriptions, prepare the submission materials, and coordinate follow-up with your team.

A practical sequence is:

• Confirm token identity, chain, contract, and the figure being requested.
• Reconcile supply data with balances, locks, vesting, and project disclosures.
• Document assumptions and identify evidence gaps before submission.
• Prepare the platform-facing explanation and supporting links.
• Submit and organize clear responses to reviewer questions.

The CoinGecko and CoinMarketCap requests should be prepared separately where their forms or review questions differ. Shared evidence can be reused, but the explanation should answer each platform’s specific request. For a broader profile review on CoinMarketCap, see CoinMarketCap listing support; supply work can also be paired with CoinMarketCap community verification.

How do you make a circulating-supply calculation reviewable?

A reviewable calculation shows the starting supply, each included or excluded category, and the reason for its treatment. Reviewers should not have to infer how the headline figure was produced from scattered announcements or wallet labels.

Start with a short summary of the method, then support it with a balance schedule. Separate categories that have different restrictions instead of combining all project-held tokens into a single unexplained reserve. For every excluded allocation, link to the contract, vesting terms, lock evidence, or other public material that supports the description. Note any assumption that could change the figure, such as scheduled unlocks, emissions, or a supply adjustment.

A useful internal check is to ask whether an independent reader could reproduce the reported figure using your materials. Confirm that the relevant balances are not counted twice, that burned tokens are distinguished from tokens that are merely locked, and that bridged representations are explained. Then compare the result with the circulating-supply figure on your website and other public profiles.

If an on-chain explorer has incomplete or outdated project information, address that source as part of the preparation. Our explorer token information update can help align public contract context with the supply explanation. The aim is not to make the number look favourable; it is to make the methodology understandable and consistent.

What does the supply verification service include?

The service includes a structured review of your supply evidence, a documented calculation, submission preparation, and support with platform follow-up. The exact work plan is agreed after we understand the token model and the state of your records.

Typical project deliverables include:

• A review of tokenomics, public supply figures, and relevant on-chain references.
• A category-by-category supply breakdown with explanations for excluded balances.
• A list of missing or conflicting evidence for your team to resolve.
• Submission-ready text and organized supporting links for CoinGecko and CoinMarketCap.
• Coordination of project responses to questions raised during review.

Timing is shaped by how quickly your team can provide wallet details, contract documentation, and current tokenomics, as well as by each platform’s review process. If the initial materials are complete and consistent, preparation can move directly to submission. If balances have unclear ownership, vesting terms are not public, or figures conflict across project channels, resolving those issues comes first. We identify such gaps early so the team can assign them to the appropriate owner.

The starting price is from $1,500 / project. The engagement is scoped around the supported platform requests and the condition of the project’s evidence. To plan adjacent listing work, see other crypto tracker listings or contact us through project contact.

What can affect a CoinGecko or CoinMarketCap review?

A strong submission can make your supply calculation easier to assess, but it cannot control a platform’s classification or review outcome. CoinGecko and CoinMarketCap each apply their own review processes, data standards, and decisions; neither approval nor a particular timing can be promised by an agency.

For circulating supply specifically, reviewers may need to assess whether a balance is genuinely unavailable, whether the supporting lock or vesting evidence is sufficient, and whether your reported figure agrees with public information. A token held by the project is not automatically excluded simply because the team describes it as reserved. Likewise, a burn claim needs evidence that the tokens are no longer spendable, not only an announcement. If the contract permits movement or the terms are unclear, the platform may reach a different classification from the project’s preferred one.

We therefore focus on the parts your team can control: traceable addresses, clear restrictions, consistent disclosures, and prompt, evidence-based replies. Do not submit a figure that your public records cannot support. If the calculation changes after an unlock, migration, or tokenomics update, refresh the documentation rather than relying on an old approval as proof of the current supply. For a related profile issue, see listing profile remediation.

Prices

Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.

How it works

1. Review the token modelWe confirm the token identity, chain, contract, current supply figures, and the project’s intended calculation. Your team provides the relevant tokenomics and public records.
2. Reconcile balances and evidenceWe map circulating and excluded categories to on-chain references, lock terms, vesting information, and other available documentation. Unclear or conflicting items are flagged for resolution.
3. Prepare platform submissionsWe write a concise explanation and organize supporting links for the applicable CoinGecko and CoinMarketCap requests. Each submission is tailored to the information being requested.
4. Coordinate review follow-upWe help your team answer reviewer questions with relevant evidence and keep project records aligned. Any change to the calculation is documented for future updates.