How to verify circulating supply on CoinMarketCap

What does circulating supply mean on CoinMarketCap?

Circulating supply is the amount a data provider treats as available to the public market. Your project’s job is to show how that figure was calculated and why each included or excluded balance belongs in its category.

Do not treat total supply, maximum supply, and circulating supply as interchangeable labels. A token can be issued but subject to a lock, vesting schedule, or other restriction. Conversely, a project-controlled wallet is not automatically excluded: document the balance and explain its status rather than relying on the wallet owner’s label.

Start with one agreed definition and apply it consistently across your tokenomics page, supply spreadsheet, and submission. If a reader cannot reproduce the result from those materials, the figure needs more work before it is sent. This distinction also matters when readers compare market capitalization, which uses price and circulating supply, with a valuation based on a larger supply figure.

How do you calculate a supportable circulating-supply figure?

Build the figure from token balances and documented exclusions. Keep the arithmetic visible so a reviewer can follow the path from chain data to the number you report.

1. Identify the token contract, network, and relevant token standard.
2. Establish the issued balance at a stated block or review date.
3. List each balance proposed for exclusion, with its wallet and rationale.
4. Subtract only the exclusions supported by records and your stated definition.
5. Reconcile the result with the total-supply figure and explain any difference.

A useful working sheet has one row per wallet or contract. Include the address, balance source, category, whether the balance is locked or otherwise restricted, the relevant release condition, and a link or filename for evidence. Separate factual observations from project interpretation: the address balance is an observation; the claim that tokens are unavailable is a conclusion that needs supporting terms or controls.

Record the block or date used for each chain lookup. If supply changes through minting, burning, unlocks, or migration, note the event and update the calculation rather than silently replacing the prior figure. A reviewer should be able to recalculate the total without asking the team to explain spreadsheet formulas.

Which documents and wallet records should you prepare?

Prepare evidence that connects each supply category to a verifiable record. The aim is a compact dossier in which every exclusion has an address, a reason, and supporting documentation.

Use explorer records for on-chain balances and transactions. Add the governing documents that explain restrictions or allocation status; a spreadsheet alone does not establish that a balance is unavailable. For a multisignature or treasury wallet, identify its purpose and decision process in plain language. For a vesting contract, show the contract and the terms that determine when tokens can be released.

Create an evidence index that pairs each row in the calculation with a document or transaction reference. Remove unrelated personal data from files where possible, but preserve enough context to verify the claim. If a document is not public, label it clearly and confirm that the team is authorized to share it for review.

How should you prepare a CoinMarketCap supply update?

Submit one consistent explanation rather than a collection of disconnected files. The package should tell the reviewer what changed, how the number was derived, and where to verify the evidence.

Use this submission checklist:

• State the token name, symbol, network, and contract address.
• Give the proposed circulating and total supply figures, each with a reference date or block.
• Attach the calculation sheet and define each included or excluded category.
• Provide wallet addresses, relevant transaction or contract references, and supporting records.
• Explain material differences from previously published figures, if applicable.
• Check that the project website and token information use the same figures and terminology.

Keep the cover note short. Lead with the requested correction or update, then point to the relevant sheet rows and evidence filenames. Avoid claims such as “locked” without saying what enforces the restriction and when it can end. If the figure changes over time, describe the update trigger, such as an unlock or migration, and identify which records will need refreshing.

For the broader listing workflow, see how to get listed on CoinMarketCap. If the project needs a hands-on dossier review, AEOTech checks the calculation against the wallet schedule and flags unsupported exclusions before the materials are prepared for submission.

What should you check before sending the supply dossier?

Run a reconciliation review before submitting. The calculation, supporting records, and public-facing token information should describe the same supply picture.

Check that addresses are copied correctly and belong to the stated network. Confirm that contract balances are not counted twice through both a wallet entry and an allocation summary. If a vesting schedule has elapsed in part, calculate the remaining restricted balance rather than treating the original allocation as wholly locked. For migrations, make clear whether holders can still access the old token and how the new supply is reconciled.

Ask a team member who did not build the spreadsheet to follow a sample row from balance evidence to the final total. If they need an oral explanation to understand why a balance is excluded, add that explanation and evidence to the dossier. For a separate profile or metadata correction, see CoinMarketCap profile remediation.

What can CoinMarketCap decide during supply review?

Your team controls the accuracy and clarity of its calculation; CoinMarketCap controls its review and the figures shown on its platform. Prepare evidence for the specific question at hand and treat the final displayed value as a platform decision.

CoinMarketCap may assess whether your definitions and records support the proposed figure, and the project cannot dictate the review outcome, the platform’s treatment of a wallet, or when an update appears. Do not describe a submission as verified until the platform’s public data reflects the change.

Make the work auditable regardless of the outcome. Save the submitted version, the evidence index, and any follow-up materials together. If the platform asks for clarification, answer the precise point raised and update the calculation only when the underlying evidence or definition warrants it. Avoid changing figures across project channels while a review is in progress unless you can explain the change and keep the records aligned.

For projects that need a structured check before submission, the circulating supply verification service focuses on the calculation, wallet classification, and evidence trail. The review is a preparation step; it does not replace the platform’s own assessment.

How do you keep circulating supply accurate after review?

Maintain a change log and revisit the calculation whenever an event changes token availability. A past submission is a snapshot, not a substitute for ongoing records.

Track the events that can affect your figure:

• Scheduled vesting releases or newly imposed restrictions.
• Treasury transfers that change the status or location of a balance.
• Token minting, burning, or contract migration.
• Governance decisions that change control over allocated tokens.
• Corrections to a prior wallet label, balance, or calculation method.

For each event, record the transaction or decision, its effective date, the affected addresses, and the resulting calculation change. Preserve the previous version so the team can explain why a figure changed. Assign one owner to maintain the wallet list and another reviewer to check the arithmetic before figures are reused in public materials.

If the project is also preparing an update for CoinGecko, keep a shared source dataset but prepare platform-specific explanations and submission materials. See how to get listed on CoinGecko for that separate process. Send AEOTech your token contract, current supply sheet, wallet categories, and available restriction records; we will begin with a named dossier review and return a list of calculation gaps and evidence to resolve.

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. Map the tokenConfirm the network, contract, supply definitions, and calculation date. Gather the current public token materials.
2. Classify balancesBuild a wallet schedule and mark each balance as included or proposed for exclusion, with a reason.
3. Attach evidencePair each material wallet classification with chain records, contract terms, governance records, or allocation documents.
4. Reconcile the figuresCheck the arithmetic, dates, migration history, and consistency between the calculation and public materials.
5. Prepare and track the updateSubmit a concise explanation with an indexed evidence package, then retain the version and respond to any clarification request.