How to Verify Circulating Supply on CoinMarketCap

What does CoinMarketCap circulating supply verification establish?

CoinMarketCap circulating supply verification is an evidence review of the quantity a project reports as circulating and the reasoning behind that figure. Your task is to make the number reproducible: another reviewer should be able to trace it from the stated supply base through the balances and exclusions used in your calculation.

Circulating supply is not simply the amount minted, nor is it necessarily the total supply less one broad category. Tokens held in vesting contracts, project treasuries, liquidity arrangements or other controlled addresses may need to be explained individually. The relevant treatment depends on the facts of the allocation and the methodology you disclose.

Before gathering files, write a short methodology note that answers:

• What supply figure are you reporting, and as of what date and time?
• Which addresses and balances are included or excluded?
• What evidence supports each classification?
• Which events could change the figure, such as an unlock or token migration?

This framing also helps readers interpret market capitalization alongside the reported supply. For the broader profile process, see how to get listed on CoinMarketCap.

Which documents should you prepare before submitting?

Prepare a compact evidence file that connects the token’s published allocation plan to verifiable on-chain records. A reviewer should not have to infer why a wallet is excluded or reconcile different totals across unrelated documents.

A practical file usually brings together:

• Token contract address, chain, decimals and links to relevant explorer pages.
• Current tokenomics or allocation document, with a version date.
• Vesting schedules, unlock terms and contract addresses for locked allocations.
• A wallet register with address, label, balance, classification and evidence source.
• Treasury, team, investor, ecosystem and liquidity allocation records where applicable.
• Burn evidence or migration documentation if either affects the reported quantity.

Use primary evidence where possible: contract data, explorer records, published vesting terms and project-controlled documents. A spreadsheet is useful for the calculation, but it should link to the underlying sources rather than stand in for them. If a wallet label is based on project knowledge rather than public data, say so and provide the supporting record.

Keep one dated “source of truth” folder. Separate current evidence from superseded schedules, and name files so the relationship is obvious—for example, a vesting schedule should identify the allocation it explains. This discipline makes the submission easier to review and future updates easier to reproduce.

How do you reconcile balances into a defensible figure?

Reconcile circulating supply by starting with a defined supply base, then documenting every material inclusion and exclusion. The calculation should be a transparent bridge from the token’s on-chain state to the figure you submit, with no unexplained adjustment between the two.

Build a worksheet with one row per relevant address or allocation. Include its balance at the chosen snapshot, label, treatment, reason, and evidence link. Add the included balances and excluded balances separately, then compare the result with your reported figure and published tokenomics. If the contract or explorer exposes a different total, explain what accounts for the difference rather than silently replacing one source with another.

Check the worksheet for common points of confusion:

• Are balances taken at the same snapshot time and on the same chain?
• Are vesting contracts counted consistently with the stated methodology?
• Are treasury and operational wallets distinguished from public-market holdings?
• Are burned tokens supported by verifiable evidence of their status?
• Do decimals, migrations or wrapped representations create duplicate counts?

Have a second person reproduce the total from the source links. Record the snapshot date and any assumptions in the file itself. If a value is estimated or a wallet’s purpose is uncertain, mark that clearly and resolve it before submission rather than presenting an assumption as an on-chain fact.

How should you explain locked tokens, treasury wallets and unlocks?

Explain each allocation according to its actual access, restrictions and role; labels alone do not establish whether tokens should be treated as circulating. A wallet register is strongest when its classification is supported by contract terms, governance records or other evidence that a reviewer can inspect.

For locked allocations, connect the balance to the relevant vesting contract and schedule. Identify the beneficiaries or allocation category where that information is public, and show how released tranches affect the calculation. For treasury holdings, distinguish assets reserved for a defined purpose from tokens already distributed or available to trade. For liquidity-related balances, state the address, the token balance and the arrangement that explains how it is used.

A useful table can make the logic clear:

When an unlock occurs, update the dated calculation, wallet register and public tokenomics together. This avoids a mismatch between an old profile figure and newer project documents. For help structuring the evidence set, review circulating supply verification.

How do you submit the CoinMarketCap supply update?

Submit a concise update through CoinMarketCap’s current official support or profile-update route, with the calculation and evidence arranged so the reported number can be checked efficiently. Confirm the current route and instructions on CoinMarketCap Support before sending; do not rely on an old form or an informal message as proof of submission.

Put the requested figure, snapshot date, methodology summary and primary evidence links near the beginning. Attach the wallet register and supporting documents in a consistent format. If the update relates to a migration, unlock or other change, state what changed and how that event alters the calculation. Keep a copy of the submitted version so any follow-up refers to the same inputs.

A clear handoff includes:

• The token name, contract address and chain.
• The current reported figure and proposed figure, with the as-of date for each.
• A brief explanation of the calculation and material exclusions.
• Direct links to the evidence, plus contact details for the person who can clarify it.

Before sending, check that the number in the message matches the worksheet and the project’s public materials. If a reviewer asks for clarification, answer the specific question and update the evidence file rather than sending a second, conflicting calculation. This approach keeps the submission auditable from first contact through any requested revision.

When should you review the reported supply again?

Review the calculation whenever a token event can change balances, access or the way an allocation is classified. A verified figure is useful only while its evidence remains aligned with the token’s current state and the project’s published records.

Set an internal review trigger for vesting releases, new token issuance, burns, treasury transfers, migration activity and changes to allocation terms. The owner of the supply file should update the wallet register, calculation and public tokenomics as part of the same review—not as separate tasks with different dates. Keep a change log that records the event, source, calculation impact and person who approved the update.

For a recurring check, compare the current evidence against the previous snapshot. Investigate material differences rather than assuming they reflect normal activity. Confirm that address labels still describe the wallet’s current role, and that any newly created contract or migrated balance has not been omitted or counted twice.

This maintenance process also helps prepare for profile changes beyond supply. If you are reviewing broader data consistency, use the listing and verification hub or read how CoinGecko listing works. A supply record should remain consistent with the project’s public disclosures, not only with one platform profile.

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

The project controls the quality of its evidence and the accuracy of its proposed calculation, but CoinMarketCap controls its assessment, displayed figure and timing of any profile change. Reviewers may request clarification or additional support, so prepare to explain the methodology rather than treating submission as automatic acceptance.

MediaStrategy uses a named supply reconciliation review: we check the calculation against the wallet register, identify unsupported classifications, and confirm that the document set and public figures tell one consistent story. The output is a structured evidence file and a submission-ready explanation, with open questions marked for the project to resolve. This is useful when responsibility for tokenomics, treasury records and community communications sits across different teams.

To start, send MediaStrategy the token contract and chain, your latest supply calculation, allocation and vesting documents, and any earlier CoinMarketCap correspondence. We will map the evidence, flag gaps and agree the scope of the review before preparing the handoff.

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 snapshot and methodologyChoose a clear as-of date and write down what the project counts as circulating. Identify the events or allocation categories that need explanation.
2. Collect primary recordsGather contract and explorer links, vesting terms, allocation documents, wallet labels and any migration or burn evidence.
3. Reconcile every relevant balanceBuild a wallet-level worksheet, calculate included and excluded amounts separately, and resolve mismatches against the stated supply base.
4. Run a second-person reviewAsk someone who did not prepare the worksheet to reproduce the total from its sources and check that the public documents agree.
5. Submit and maintain the fileUse CoinMarketCap’s current official route, retain the exact submitted version and log later changes to balances or methodology.