How to verify circulating supply on CoinMarketCap

What does circulating supply mean on CoinMarketCap?

Circulating supply is the amount of a token that a data provider treats as available to the public market under its methodology. It is not automatically the same as the total number issued, the maximum supply, or the balance visible at a token contract address.

Start by defining the figure you are asking CoinMarketCap to review. The basic reconciliation is: circulating supply = total supply − tokens that are not circulating under your stated methodology. That subtraction is only useful if the project can explain what is included in the excluded amount. A vesting allocation, an inaccessible contract balance and a treasury reserve can each require different evidence.

Before calculating, make a short scope note that records:

• The token and network being reviewed, including the contract address.
• The date and time of the balance snapshot.
• The supply figure and unit used in the calculation.
• The categories treated as non-circulating and why.

Use this definition consistently in the project’s tokenomics, explorer references and submission materials. For the wider listing context, see how to get listed on CoinMarketCap. A clear definition gives reviewers and readers a way to trace your number back to identifiable records.

How do you calculate and reconcile the figure?

Calculate circulating supply by starting with a traceable total and subtracting balances that your documented methodology classifies as unavailable to the market. The key is not just the final arithmetic: each input should point to a source that another person can inspect.

Create a worksheet with one row per relevant allocation or wallet. Record the wallet or contract address, balance at the snapshot time, allocation category, relevant lock or vesting terms, and whether you include or exclude it. Then total included and excluded balances separately. Keep the snapshot date visible; if balances change later, the calculation should be reproducible for each version.

Check the result against the token contract and explorer records. If your token has multiple chains, migrations, wrapped representations or bridge contracts, explain how those balances are treated so the same tokens are not counted twice. If a balance cannot be attributed confidently, mark it for investigation instead of silently assigning it to a category.

A useful final check is to compare the worksheet against the project’s published tokenomics and any supply figure already shown on data platforms. For more on the related listing workflow, use CoinGecko listing guidance; the calculation should remain internally consistent even when providers use different review processes.

Which documents should you prepare for supply verification?

Prepare a compact evidence pack that connects every material supply claim to a document or on-chain record. These materials make the calculation easier to review and help your team answer follow-up questions without rebuilding the analysis.

Gather the records that apply to your token:

• Token contract address, network details and explorer links.
• Tokenomics or allocation document showing categories and amounts.
• Vesting schedules, lock agreements or contract references for restricted allocations.
• A wallet register that identifies treasury, team, investor, ecosystem and other relevant addresses.
• On-chain balance evidence captured at the same time as the worksheet.
• Explanations for burned, locked, reserved or otherwise excluded balances, with supporting references.
• A dated statement from the project explaining the calculation and any assumptions.

Do not describe a wallet as locked merely because the project intends not to move its funds. Support that treatment with the applicable contract, schedule or other evidence, and distinguish a technical restriction from an internal policy. If a document is confidential, provide a shareable summary and identify what evidence can be supplied privately through the relevant review route. Keep filenames, dates and terminology aligned with the worksheet so each claim is easy to locate.

How should you classify treasury, vesting and locked wallets?

Classify wallets by the evidence for their status and availability, not by the label your team prefers. A wallet register turns the supply calculation into an auditable explanation rather than a collection of unsupported assumptions.

For each address, record who controls it, what allocation it represents, whether a contract restricts transfers, and what event could make the balance transferable. Where vesting applies, connect the address to the schedule and state whether any portion has already unlocked. For a treasury wallet, explain its purpose and whether the balance is committed, reserved or available for deployment. Apply the same rule to comparable allocations; inconsistent treatment can make a plausible total difficult to assess.

A practical classification table can include these columns:

If the project has migrated tokens or operates across networks, add a reconciliation note that explains the relationship between addresses and representations. For a separate verification workflow, see circulating supply verification.

How do you prepare a consistent CoinMarketCap submission?

Prepare the submission as one coherent account of the token’s supply: a stated figure, a dated calculation and evidence that supports the inclusion and exclusion decisions. Before sending materials through CoinMarketCap’s current project or listing process, check that the project profile and supporting documents use the same contract, network and token terminology.

Assign one person to own the final version. That person should compare the worksheet with the tokenomics page, project website and any prior public supply statements. Resolve discrepancies before submission, or explain them directly with the reason and effective date. Avoid sending multiple unexplained totals, such as one figure for an announcement and another for the review pack.

Use this pre-submission checklist:

• Confirm the contract address and network match across every file.
• Recalculate totals from the recorded wallet balances.
• Check that each excluded category has a clear basis and evidence.
• Date the worksheet and identify the source of each balance.
• Ensure public tokenomics language matches the calculation.
• Keep a copy of the final pack and note later changes.

For teams handling both provider records, CoinGecko vs CoinMarketCap listing is a useful comparison. Treat each provider’s request and status separately, and keep a change log so future updates can be tied to a specific event.

What can affect CoinMarketCap’s supply review?

A complete evidence pack improves clarity, but CoinMarketCap determines how it reviews and classifies supply information on its own platform. Its assessment, accepted evidence, displayed figure and review timing are outside the project’s control; no document set can promise a particular classification or approval. The controllable commitment is to submit accurate, internally consistent materials and respond with relevant evidence if the review process requests it.

Common issues worth resolving before submission include a mismatch between the token contract and project profile, wallet balances that do not reconcile to the stated total, a vesting schedule without a corresponding address, and a locked label unsupported by a restriction or record. A review may also require clarification when a project’s wording leaves open whether a balance is transferable or who controls it.

If the figure is questioned, respond to the precise issue rather than sending the entire pack again without explanation. Point to the row in the worksheet, identify the relevant address or contract, and attach the evidence that addresses the question. If the underlying facts have changed, recalculate from a new snapshot and label the revised version clearly. This approach preserves an audit trail and helps your team keep public supply statements accurate while the platform completes its own assessment.

When should you update the supply calculation?

Update the calculation whenever a material token event changes a balance or its classification. A supply worksheet is a dated record, not a permanent statement: vesting unlocks, treasury transfers, burns, migrations and contract changes can make an earlier snapshot incomplete.

Set an internal review trigger for each event that may affect supply. The responsible team member should confirm the affected addresses, capture current balances, apply the existing classification rules and record the reason for any change. If the methodology itself changes, preserve the old version and explain the new treatment rather than overwriting the prior calculation. That history helps the project answer questions about why a displayed figure differs from an earlier public statement.

Keep the same source-of-truth worksheet for updates and link every new figure to its snapshot date. Then review the project’s tokenomics page, listing profile and other public descriptions together so one update does not leave conflicting numbers elsewhere. If a cross-chain move or token migration is involved, document both the tokens removed from the old representation and those issued in the new one. For a related profile update workflow, 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. Confirm the token and snapshotRecord the contract, network and balance snapshot date. Identify any migration or additional token representations that need to be reconciled.
2. Build the wallet registerList relevant addresses, balances, allocation categories and control or restriction evidence. Flag unresolved classifications instead of assuming an answer.
3. Calculate included and excluded balancesApply one stated methodology across comparable allocations, then show how the final circulating figure follows from the recorded inputs.
4. Assemble supporting documentsAttach tokenomics, vesting or lock records, explorer references and a concise explanation that ties each exclusion to evidence.
5. Reconcile and submitCompare the pack with public project materials, correct inconsistencies, and use CoinMarketCap’s current submission route for the relevant request.