How to Verify Circulating Supply on CoinMarketCap: Process and Documents

What Does Circulating Supply Mean on CoinMarketCap?

Circulating supply is an estimate of the number of tokens available to the market according to the data provider's methodology. It may be less than total supply: issued tokens are not necessarily available for circulation if they are locked, vesting, or excluded under a justified project policy.

For verification, it is important to show not only the final number but also the logic of the calculation. Prepare a simple equation: the total volume of issued tokens minus confirmed unissued, locked, or otherwise unavailable parts equals the stated circulating supply. Do not combine different categories in one line: project reserve, team and investor tokens, assets in a vesting contract, and burned tokens require separate explanations.

Before submission, check three things:

• whether the total volume matches the contract data and tokenomics;
• whether each exclusion can be linked to a specific address or contract;
• whether the description of token availability matches the unlock conditions.

This logic helps the reader understand the figure on the asset page and helps the team detect inconsistencies before contacting CoinMarketCap. If the project has not yet gone through CoinMarketCap listing, first understand the requirements for the asset page: the listing application and supply confirmation are related but not identical.

How to Calculate Circulating Supply Before Submission

Calculating circulating supply starts with an inventory of tokens, not with a desired value for the page. Create a distribution table and for each category record the total balance, storage address, access status, and source of confirmation.

A practical workflow:

• export balances of significant wallets and contracts from the network explorer;
• reconcile the total volume with the token parameters and published tokenomics;
• mark assets in lockup, vesting, or other restriction contracts;
• separate tokens available to the market from excluded ones and document the reason;
• recalculate the total and verify it aligns with the distribution table.

Do not exclude a balance just because the team considers it a "long-term reserve." You need to show why the funds are not available to the market and what mechanism ensures this. For example, for a vesting contract, provide the address, unlock conditions, and a link to on-chain confirmation; for a treasury, explain access authority and usage order. If tokens move between wallets, reflect the movement so that the same balance is not counted twice.

Record the calculation date and keep the working table together with the source data. This allows you to repeat the verification after an unlock or balance change. General listing principles are covered in the guide on CoinMarketCap listing, and verifying current supply data can be managed as a separate task.

What Documents and Confirmations to Prepare

A good document package allows every figure to be verified without guesswork. Prepare materials so that the address, token category, access status, and balance amount are linked together.

Include in the working package:

• token contract address and the network in which it is issued;
• distribution table with categories, balances, and addresses;
• list of addresses you propose to exclude from circulating supply;
• links to the explorer for contracts, wallets, and significant transactions;
• vesting or lockup conditions and schedule of future unlocks;
• description of the burn mechanism, if relevant to the calculation;
• public tokenomics and explanation of discrepancies between documents.

For each wallet, add a short note: who or what it belongs to, who has access, why the tokens are there, and why the balance is accounted for in that way. If the address is controlled by a smart contract, provide its purpose and parameters that allow understanding the restrictions. If a document is not public, prepare a secure way to transmit it to the review team in advance; do not publish access secrets or private keys.

Check the spelling of the name, ticker, network, and addresses across all files. Versions with different numbers or outdated schedules complicate the review. The supply verification service can help assemble the calculation and bring confirmations into a unified structure, but the source data must still reflect the project's state.

How Does Circulating Supply Verification Work on CoinMarketCap?

Submission begins with defining the goal: the project needs to confirm the current figure, update it after a tokenomics change, or correct outdated information. This determines which materials to attach and which sections of the page to reconcile.

Before sending, appoint one person responsible for the numbers and one for communication. Then assemble the final package and ensure it explains the calculation without internal abbreviations or contradictions. In the form or communication channel that CoinMarketCap specifies for the project, state the request directly: what value is proposed for verification, as of what date it is calculated, and what documents confirm the exclusion categories. Use the current official process of the platform; do not send sensitive data through unofficial contacts.

After submission, keep a copy of the sent materials and record requests for clarification. If the platform asks to clarify a specific address or category, respond precisely: provide evidence, update the table, and verify that the final value still reconciles. Do not send multiple calculation versions without indicating which one is current.

If the asset does not yet have a page, separate this process from the CoinMarketCap listing application. For internal control, you can maintain a common task list for listings and verification: page status, calculation status, date of last reconciliation, and responsible person.

How to Reconcile the Calculation with Wallets and Unlock Schedule

Reconciliation is needed so that the calculation reflects the actual state of tokens, not just the distribution plan from the document. Match addresses and on-chain balances with the project table, then verify that each balance is assigned to exactly one category.

Start with addresses that significantly affect the total: vesting contracts, treasury, reserves, bridges, and lockup contracts. For each, record the current balance, access rights, and movement rules. Check if there is an administrative function that can change timelines or transfer assets: if such a possibility exists, do not describe the lockup as unconditional. State the actual conditions, not just the team's intention.

The unlock schedule must match the tokenomics and the current calculation. Unlocked tokens can change circulating supply, so prepare an update procedure: who receives the notification, who recalculates the categories, and where the new version is published. If a bridge creates a representation of the token in another network, explain how double counting of the original and wrapped asset is avoided.

Before sending, go through a checklist: addresses open, labels are clear, balances are current as of one date, and the sum of categories matches the total. This same discipline will be useful for subsequent listing profile updates when asset information changes.

CoinMarketCap vs CoinGecko: How Supply Verification Differs

CoinMarketCap and CoinGecko are different platforms, so one submission does not replace a separate data verification on the other. For both, prepare a consistent base: contract address, distribution, calculation method, and confirmations for excluded balances, then work with each platform's current procedure.

When comparing CoinMarketCap vs CoinGecko, do not rely only on what the public page shows. Compare which values are listed, when they were last updated, and whether the supply explanations match. If the data diverges, first find the reason: different reconciliation dates, an updated balance, a different unlock status, or different source documents. Fix the source and submit an explanation to each platform separately.

CoinMarketCap vs DEXScreener is a comparison of different tasks. CoinMarketCap displays reference information about the asset within its page and data model; DEXScreener focuses on market pairs and decentralized exchange data. Pair visibility there does not confirm circulating supply on CoinMarketCap and does not replace distribution documents.

If the project needs verification on another aggregator, use a separate guide on CoinGecko listing. For working with market pairs, read the material on DEXScreener trending: it is a separate mechanism, not a way to confirm token supply.

What Can Delay Confirmation and How to Maintain Data?

Preparation is most often complicated by inconsistent arithmetic, lack of explanations for addresses, and discrepancies between tokenomics and contract state. Before submission, it is useful to ask a colleague who did not participate in the calculation to reconstruct the total using only the attached materials. If they cannot determine what is included and excluded, the package needs clarification.

CoinMarketCap independently evaluates the submitted evidence and applies its own methodology to circulating supply. Therefore, the project cannot promise acceptance of a specific classification, an exact update date, or retention of the value without revision; you can be responsible for the completeness and consistency of the submitted materials, but not for the platform's decision. Be especially thorough in explaining balances in wallets with flexible access rights: the presence of a balance alone does not prove that tokens are locked.

Keep the calculation current after unlocks, wallet movements, contract changes, or tokenomics updates. Maintain a version log with the date, balance sources, and a brief description of changes. For a significant change, do not just replace one number: update the distribution table, address explanations, and unlock schedule so they tell the same story.

For the next verification cycle, appoint a responsible person in advance and prepare a reconciliation template. This reduces the likelihood of gathering evidence from scratch again and helps the team explain updated information to token holders.

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. Define the purpose of the requestClarify whether you need to confirm the current circulating supply, update it after changes, or correct outdated information. Note the date as of which the data is calculated.
2. Collect on-chain dataCheck the contract, wallet balances, and address restrictions. Save explorer links and explain the purpose of each significant address.
3. Reconcile calculation and documentsMatch the distribution table, tokenomics, and unlock schedule. Ensure each excluded balance has a specific justification.
4. Submit the package through the current channelUse the form or process specified by CoinMarketCap for the project. State the request unambiguously and attach materials supporting the stated calculation.
5. Respond to clarifications and update dataKeep a history of correspondence and respond with evidence relevant to the question. After balance changes or unlocks, recalculate the supply and update related documents.