How to verify circulating supply on CoinMarketCap

What does circulating supply mean on CoinMarketCap?

Circulating supply is the quantity of a token that a data provider considers available to the market under its own review methodology. The number is not necessarily identical to total supply or to the amount minted on-chain, so your submission should explain the difference rather than treating the terms as interchangeable.

Begin by recording the token contract, the time of the snapshot, the total issued amount at that point and the balances you believe should not count as circulating. Depending on the project, those balances may include locked vesting allocations, tokens held in a treasury, or assets controlled by a contract with documented restrictions. Do not assume that a wallet label alone proves an exclusion: explain who controls the address and why the balance is not available.

A useful calculation can be followed by someone who did not create it:

• State the total supply figure and how you obtained it.
• List each proposed exclusion and its supporting evidence.
• Show the resulting circulating figure and the arithmetic connecting the inputs.
• Note any assumptions, unresolved addresses or scheduled changes.

This distinction matters because market data pages may use circulating supply in displayed calculations. For CoinMarketCap’s broader listing requirements, see how to get listed on CoinMarketCap.

How should you reconcile wallets, vesting and token allocations?

Reconcile supply by matching on-chain balances to a current allocation record and explaining every material category. A tokenomics document is a starting point, but it is not enough if it does not match the deployed contracts and present wallet balances.

Create a working sheet with one row per wallet or contract. Record the address, balance at the chosen snapshot, allocation category, control or beneficiary, restriction mechanism, supporting source and proposed treatment. Keep the source references specific: a vesting contract address, a transaction, an explorer page, a signed agreement where appropriate, or a project-controlled document that explains the allocation. Avoid relying on labels without evidence.

Then check that category totals reconcile to the on-chain supply figure. If a vesting allocation is split across several contracts, account for each contract and ensure the same tokens are not excluded twice. If tokens have been burned, document the address and the basis for treating the balance as inaccessible; do not infer that a transfer to an unfamiliar address proves a burn.

Where a wallet contains both restricted and available tokens, explain the division rather than excluding the entire address by default. Keep a record of rounding, token decimals and snapshot timing so a reviewer can reproduce the arithmetic. A clear table makes inconsistencies visible before you submit.

Which documents make a supply review easier to assess?

A review-ready package connects the calculation to verifiable records and explains how the project controls or restricts each excluded balance. There is no substitute for evidence that matches the token contract and the current state of the project.

Gather the materials that apply to your token:

• A supply calculation with the snapshot date, contract and formula.
• Wallet and contract addresses, balances and allocation labels.
• Tokenomics or allocation materials showing the intended distribution.
• Vesting schedules and contract details for locked allocations.
• Treasury or governance documentation for project-controlled holdings.
• Relevant transaction records or explorer references supporting changes in supply.
• A concise note for exceptions, such as migrated tokens or a supply mechanism that changes balances.

Make sure the documents agree with one another. If your published tokenomics says an allocation is locked but the contract permits an administrator to release it, explain that authority and do not describe the tokens as irreversibly locked. If a spreadsheet uses a different supply snapshot from the explorer evidence, update the figures or state why they differ.

Submit a coherent set of records rather than a large folder with no index. A short cover note should identify the proposed circulating figure, summarize the exclusion logic and point reviewers to the evidence for each category. Keep sensitive internal records limited to what is necessary for review.

How do you submit the circulating supply information?

Submit the calculation through CoinMarketCap’s designated project or support process, using the current instructions available from the platform. The goal is to make the request easy to verify: identify the asset, state what you are asking to update, and provide evidence that supports each part of the calculation.

Before sending, confirm that the token contract and project identifiers are correct, the calculation uses a consistent snapshot, and every exclusion has a matching explanation. Name files descriptively and include an index that maps each excluded balance to its supporting document or on-chain record. If the project has already submitted related listing information, keep the supply explanation consistent with it; the CoinMarketCap listing guide can help you prepare the broader project information.

After submission, monitor the contact channel associated with the request and keep a copy of the exact materials sent. If the reviewer asks for clarification, answer the question directly and revise the calculation if the evidence exposes an error. Avoid sending conflicting versions without identifying which file supersedes the earlier one.

The circulating supply verification service can help organize the evidence and submission package. For a broader view of listing-related work, see listings and verification.

What should you do when circulating supply changes?

Update the calculation when new issuance, an unlock, a burn, a migration or a change in wallet control affects the tokens available to the market. A previously accepted explanation may no longer describe the current state after a material change.

Maintain a change log that records what changed, when it took effect, which addresses were affected and how the new figure was calculated. Compare the updated on-chain state with the allocation schedule and the project’s published materials. If an unlock moves tokens from a restricted contract to a wallet, document the transition and reassess whether the balance still qualifies for exclusion under the platform’s review.

For a token migration, distinguish old and new contracts, explain the conversion or migration process, and show how you avoid counting the same economic supply twice. For elastic or rebasing designs, describe the mechanism in plain language and identify how the snapshot was produced. Do not reuse a fixed-supply calculation if the token’s mechanics can change balances.

Keep public-facing tokenomics, the supply worksheet and any platform submission aligned. If the project cannot reconcile a figure immediately, record the unresolved item and investigate it before presenting a revised number as final. The CoinGecko listing guide is useful when you also need to prepare supply information for another data provider; treat each provider’s review as separate.

How can you quality-check a supply submission?

Quality-check the submission by asking whether an independent reviewer can trace every figure from the calculation to its source. A polished document is not persuasive if its addresses, totals or stated restrictions cannot be verified.

Run this review before sending:

• Confirm the asset contract and snapshot time in every relevant file.
• Recalculate category totals and check that no balance appears twice.
• Match each exclusion to an address and an explanation of its restriction.
• Verify that vesting records, tokenomics and on-chain evidence do not conflict.
• Check that the proposed circulating figure follows from the stated inputs.
• Remove obsolete drafts or mark them clearly so they are not mistaken for current data.

Ask a team member who did not build the worksheet to follow the calculation. If they cannot tell why a balance is excluded, add the missing evidence or revise the treatment. Keep a clean internal copy of the final submission and the date it was sent, so later updates can be compared against the same method.

This preparation also makes future updates easier: the team can identify changed balances instead of rebuilding the entire case from memory. For adjacent visibility work, distinguish data verification from placements or campaigns; a CoinMarketCap trending guide addresses a different goal and does not replace accurate supply documentation.

What is outside a project’s control during CoinMarketCap review?

A project can control the clarity and completeness of its evidence, but CoinMarketCap controls its review outcome and how it applies its methodology to a particular asset. Submitting a calculation does not itself establish that the platform will accept every proposed exclusion or display the requested figure.

In particular, wallet ownership, contractual restrictions and governance control may require interpretation. A team’s description of a treasury or vesting arrangement is evidence to assess, not a binding decision for the platform. The reviewer may request additional records, ask for a revised calculation or apply a different treatment to a balance. Platform procedures and data presentation can also change, so check current official instructions before you submit or follow up.

The practical response is to make the case auditable, answer review questions with relevant records and keep project materials consistent while the request is pending. Do not announce that a supply figure has been verified until the platform’s page reflects the accepted information. If your submission involves a special token mechanic or disputed wallet classification, describe it explicitly rather than hiding uncertainty in a footnote.

The work can cover evidence organization and submission support, but it cannot dictate CoinMarketCap’s classification, review timing or final displayed value. The deliverable is the agreed documentation and support process, not control over the platform’s decision.

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. Set the snapshotRecord the token contract, snapshot time and current on-chain supply. Use the same reference point throughout the calculation and supporting documents.
2. Map balances to allocationsList relevant wallets and contracts, their balances, and the allocation or restriction associated with each one. Flag addresses whose control or status is unclear.
3. Build and test the calculationShow the inputs, exclusions and arithmetic in a reproducible worksheet. Reconcile the totals against tokenomics and on-chain records.
4. Assemble evidenceAttach the records that support each exclusion and add an index explaining where reviewers can verify each claim.
5. Submit and maintain the recordFollow CoinMarketCap’s current submission process, retain the submitted version and respond to clarification requests with consistent, relevant evidence.