How to Verify Circulating Supply on CoinMarketCap

What does CoinMarketCap need you to verify?

Circulating supply is the quantity of tokens your project presents as currently circulating, supported by a clear explanation of what is and is not counted. Your task is not just to provide a headline figure: it is to show how that figure follows from token records, allocation terms, and balances that can be checked.

Start by writing down the calculation in plain language. Identify the total amount issued, then list each balance or allocation you exclude and the reason it is not treated as circulating. For example, a locked treasury allocation should have a wallet or contract reference and a document describing its restrictions. Do not label a balance “locked” without evidence that explains who controls it and what prevents or limits movement.

A useful working file has one row per relevant wallet or allocation, with fields for:

• Wallet or contract address and the associated token balance.
• Allocation owner or purpose, such as treasury, team, or vesting.
• Whether the balance is included in the circulating figure.
• The evidence supporting that treatment and its date.

This creates a review trail, not just a number. If the token has several chains or contract addresses, make the scope explicit so a reviewer can follow which records belong in the calculation.

Which documents make the circulating supply calculation credible?

A credible supply package connects the number to both on-chain records and the project’s documented token terms. Gather evidence that lets a reviewer move from each stated allocation to its address, balance, and treatment in the calculation.

Prepare the following where they apply to your token:

• Token contract address and relevant explorer records showing balances or token movements.
• Tokenomics or allocation materials that describe the intended distribution.
• Vesting schedules, lock agreements, or contract details supporting an exclusion.
• A wallet register identifying project-controlled, treasury, team, investor, and community allocations.
• A dated calculation sheet showing how you arrived at the proposed circulating supply.
• A short explanation of burns, migrations, bridges, or other supply changes, with supporting records.

Use consistent names across the files. If a wallet appears as “team reserve” in one document and “ecosystem” in another, resolve the mismatch before submission. Where a document is confidential, prepare a version that can be shared for review without exposing unnecessary personal or commercial details; do not remove the information needed to support the claim.

The document set should answer two questions quickly: where can the balance be checked, and why does your methodology include or exclude it? For the wider platform application context, see our guide to getting listed on CoinMarketCap.

How do you reconcile wallet balances with token allocations?

Reconcile each allocation against observable balances before you submit. A tokenomics chart describes intended distribution; it does not, by itself, show where tokens sit now or whether a claimed restriction is still in effect.

Create an address register and compare it with the latest records available on the relevant explorer. For each address, note the token amount, its project purpose, the source document, and whether it is counted. Then check for gaps: addresses mentioned in the allocation materials but missing from the register, balances with no assigned purpose, or allocations whose vesting terms have changed. Keep the original evidence alongside the working calculation so the reasoning remains reviewable.

For multiple networks, state which contracts and balances are included, and explain how you avoid counting the same economic supply twice when assets are represented across networks. If a migration has occurred, preserve the relationship between the old and new token records and document how the change affects the figure. Do not silently replace an earlier calculation; retain the prior version and note what changed.

A strong reconciliation is readable by someone outside the token team. Use labels that match the documents, link each address to its source, and write down any judgment call rather than leaving it implicit. If you also need help with a profile-level correction, compare the scope with CoinMarketCap community verification.

How should you prepare the CoinMarketCap submission?

Prepare a concise submission that states the requested supply figure, summarizes the method, and points to evidence for every material inclusion or exclusion. Before sending anything, check CoinMarketCap’s current submission fields and instructions; platform requirements can change, so use the live guidance rather than an old saved checklist.

Keep the explanation easy to scan. Lead with the calculation and its scope, then attach or reference the supporting records in the same order as your wallet register. Make sure the token name, contract address, network, and supply terminology are consistent across the form and evidence package. Assign one project contact who can answer follow-up questions and locate source documents without rebuilding the file from scratch.

Before submission, run a final review:

• Does the stated figure match the calculation sheet?
• Can each excluded balance be traced to a wallet and a documented reason?
• Are the supporting records readable and current enough to explain the claim?
• Does the explanation distinguish issued supply from the portion counted as circulating?
• Is there a clear contact for questions or requested corrections?

If the project is preparing a broader platform presence, the listings and verification overview helps separate supply evidence from other profile tasks. Keep this request focused: attach what supports the supply calculation, not unrelated promotional material.

What should you update when the supply figure changes?

Update the calculation whenever a token event changes the balances or the basis for an inclusion or exclusion. A supply figure should remain connected to the project’s latest records, not just the assumptions made at launch.

Set an internal owner for supply records and define a simple update trigger. Relevant events may include a vesting release, treasury transfer, token burn, contract migration, or a revised restriction. When one occurs, preserve the previous calculation, record the event and its date, refresh the affected address balances, and state how the event changes the proposed circulating amount. Then update any public project material that repeats the old figure so readers do not find conflicting explanations.

Keep a compact change log with the prior figure, revised figure, reason, evidence reference, and person who reviewed the change. This is especially useful when the update touches several wallets or when the underlying allocation documents have also changed. Do not revise only the headline number while leaving the supporting schedule untouched.

For projects that also need to correct other listing details, CoinMarketCap listing guidance covers the broader application context. If the project is present on another data platform, compare its requirements separately; CoinGecko listing guidance is a separate process, not a substitute for CoinMarketCap’s review.

What can your team control in CoinMarketCap’s review?

Your team controls the clarity, consistency, and traceability of the evidence it submits. You can make the calculation easy to reproduce, name a responsive contact, and correct gaps in the project’s own records before asking the platform to review them.

A practical quality check is to give the package to a colleague who did not prepare it. Ask them to find the evidence for an excluded balance, explain the calculation in their own words, and identify any record that appears outdated or contradictory. If they cannot complete those tasks without a verbal briefing, improve the labels or add the missing source document. This review catches confusing terminology and hidden assumptions before they slow down a submission.

For hands-on preparation, BrandBoost Guru uses a supply-evidence review: we map the calculation to wallet records, flag unsupported exclusions, and organize the submission materials into a traceable package. The deliverable is a clearer file your team can use in its platform request and maintain after a supply change.

CoinMarketCap determines whether the evidence satisfies its review and how its displayed supply is handled, so a project cannot promise acceptance or a particular display outcome. The controllable commitment is the accuracy and completeness of the materials your team submits.

When is outside help useful for supply verification?

Outside help is most useful when the supply figure is difficult to reproduce, supporting records use inconsistent labels, or several people need to assemble evidence across wallets and contracts. It is less useful when the calculation is already documented, current, and easy for an independent reviewer to follow.

Before starting, collect the latest calculation sheet, token allocation materials, relevant wallet and contract records, and any previous submission correspondence. Identify what the team wants checked: arithmetic, wallet classification, document consistency, or preparation of a clean submission package. That scope lets an advisor focus on verification work rather than rewriting unrelated project materials.

BrandBoost Guru begins with a document-readiness review and returns a gap list tied to the evidence provided. The team then resolves unclear classifications, aligns the calculation with the supporting records, and prepares the final package for your designated submitter. For a related profile correction, review listing profile remediation; for an overview of other verification work, see circulating supply verification.

To get started, send the token contract details, your current supply calculation, and the documents supporting exclusions. We will review the evidence set, identify what is missing, and agree the preparation scope before work begins.

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 calculationWrite down the supply figure, its scope, and the rules your project uses to classify balances as circulating or excluded.
2. Build the address registerMap relevant wallets and contracts to allocations, balances, source documents, and the treatment used in the calculation.
3. Reconcile and resolve gapsCompare the register with available records, then investigate mismatches, unassigned balances, or outdated restrictions.
4. Prepare the evidence packageArrange the calculation and supporting documents in a consistent order, and assign a contact who can answer follow-up questions.
5. Submit and maintainFollow CoinMarketCap’s current instructions, retain a copy of the submitted materials, and refresh the record when supply events change the calculation.