CoinMarketCap circulating supply: 7 checks before you submit

7 checks before a CoinMarketCap supply submission

1 dated snapshot gives every balance the same reference point. Run these 7 checks before sending a circulating-supply request or update.

• Snapshot date: record the date and the supply figure you want reviewed.
• Supply basis: state what figure you start from, such as issued supply.
• Wallet map: list relevant addresses and contracts separately.
• Allocation labels: connect each balance to its stated purpose.
• Restriction evidence: attach lock terms, vesting records or other supporting material.
• Arithmetic: show how the included and excluded balances produce your requested figure.
• Public match: compare the result with tokenomics and other public disclosures.

Use consistent units throughout. Check token decimals, address duplication and category overlap.

A treasury label alone does not explain why a balance is excluded. Connect it to an address and a record. If a balance is not publicly labeled, state what the public source confirms. Also state what relies on project documentation.

For an initial profile request, pair this calculation with the CoinMarketCap listing guide. For an existing profile, identify the current displayed figure. Explain what changed. Keep the supply calculation distinct from the wider listing request.

What should a circulating-supply number show?

3 parts make a useful supply figure: a stated basis, a traceable calculation and evidence for exclusions. Keep each part clear enough for someone outside the project to follow.

The figure is not interchangeable with total supply or maximum supply. Issued tokens may face a lock, vesting schedule or other restriction. Show those categories separately. Then explain how you treated each one in the requested circulating figure.

• Basis: name the supply figure used to begin the calculation.
• Treatment: state which balances you include and exclude.
• Evidence: cite the wallet, contract, schedule or disclosure behind each entry.
• Result: show the arithmetic and the calculation date.

Use consistent terms across the calculation and public tokenomics. If one document calls a balance “treasury” and another calls it “available,” explain the difference before submitting. A reviewer should not need private project context to understand how a category was classified.

CoinMarketCap makes its own assessment of submitted information. Present a dated, internally consistent account. Do not describe an assumption as a platform decision. For broader submission context, read the listings and verification guide.

4 evidence groups to attach to the calculation

4 evidence groups connect your headline figure to balances and allocation terms. Put each record beside the calculation entry it supports. Avoid sending an unlabeled document bundle.

Build one master table with an address or contract, balance, category, circulating status, source and notes. If several wallets belong to one category, list them separately. Show the category total. That makes duplicate entries and unexplained differences easier to spot.

Use links that open without access to a private workspace. Some balances or labels may not be publicly verifiable. Identify the supporting project record and name that limitation. Do not present a project document as an independently visible on-chain fact.

For a separate file review, see the circulating supply verification service.

How do you reconcile wallets with the requested figure?

4 passes make a reproducible calculation: capture, classify, calculate and compare. Another reader should be able to follow every balance from source to result.

1. Capture: choose one snapshot date and list the relevant balances.
2. Classify: assign each wallet or contract to a named allocation category.
3. Calculate: show the starting figure, each exclusion and the final requested amount.
4. Compare: check the result against tokenomics and other public statements.

Then inspect the table for repeated addresses, inconsistent units and overlapping categories. The same wallet may appear in a treasury list and a vesting schedule. Explain how you avoid counting it twice.

Keep a short note for any difference between the wallet balance and the amount assigned in project documents. Mark the calculation date prominently. If a previous figure exists, include a concise explanation of what changed and why.

A dated change note helps separate a new balance from an unexplained correction. For a related platform submission, reuse the same source records for a CoinGecko listing review. Follow CoinGecko’s own instructions.

A 5-part run-of-show for the supply file

5 parts take the file from raw balances to a clear submission. CoinMarketCap’s current instructions determine where and how you send it. Check them before preparing the final package.

1. Set the reference: record the snapshot date, token identity and supply basis.
2. Build the wallet table: add each address, balance, allocation and source.
3. Attach exclusion records: match each restricted balance to its supporting material.
4. Reconcile public statements: compare the result with current tokenomics and disclosures.
5. Package the request: put the summary first, then the table and linked evidence.

Name files so their purpose and date are easy to identify. Keep a copy of the exact version submitted, along with relevant correspondence.

If CoinMarketCap requests clarification, answer against the same dated calculation. Revise it only when the underlying records require a change.

For a file check from DigitalMedia1, expect a reply within 1 working day. A written quote follows within 2 working days, before any payment. You get a clear review proposal before deciding whether to proceed.

What does CoinMarketCap decide after submission?

CoinMarketCap decides whether your evidence fits its methodology. It also decides what figure, if any, it displays. A complete package cannot require the platform to accept a requested value or change its profile.

Before sending, verify that the request, calculation date, public tokenomics and supporting records agree. If CoinMarketCap asks for clarification, answer with the relevant wallet entry and source. Avoid a broad restatement of the project’s position. Keep the submitted version so your team can track exactly which evidence was reviewed.

Compare 3 items side by side: the requested figure, the master-table arithmetic and the number on your public tokenomics page. Resolve any mismatch. Or label it clearly with its date and reason.

For a cross-platform comparison, remember that a CoinGecko supply review is separate. One service’s assessment does not establish the other’s decision.

Send DigitalMedia1 the token identifier, dated calculation, wallet and allocation table, and links to public disclosures. We check the arithmetic and evidence trail. Then we return a focused list of items to clarify before you submit.

How it works

1. Set one snapshot dateRecord the date and the supply basis for the requested figure. Use that same reference across the calculation and supporting records.
2. List wallets and allocationsEnter relevant addresses and contracts separately. Link every balance to its allocation category and circulating status.
3. Support every exclusionAttach a lock record, vesting schedule or other source for each excluded balance. State where project documentation is the only evidence.
4. Reconcile the resultShow the arithmetic and check for duplicate addresses. Compare the result with public tokenomics.
5. Submit and retain a copyFollow CoinMarketCap’s current instructions. Save the exact dated file and use it to answer any follow-up.