A clearer evidence trail for CoinMarketCap circulating supply

Put the supply story into one dated record

A useful CoinMarketCap supply explanation starts with one dated calculation. It connects the proposed figure to balances, decisions, and records, instead of asking a reviewer to assemble the story from scattered files.

Choose a format your team can keep current. A spreadsheet is handy for arithmetic; a short note explains the choices behind it. You can use both, as long as the same date and figures appear in each.

Keep the first view simple: token name, contract, network, reference date, and proposed circulating supply. Then show how the total is built from categories. That lets someone follow the calculation before reading every supporting file.

For the wider profile process, see how to get listed on CoinMarketCap. If you want a second pair of eyes on the calculation and records, our circulating supply verification service covers that preparation.

Give the records a human starting point

Picture an NFT artist with a small following, between a testnet and a mainnet. They’re preparing a token supply explanation while contract details and allocation records are still being gathered. We’d first pin down which network and contract the proposed figure describes.

That small first check prevents an easy mix-up: a record from one network may not explain a balance shown on another. Next, we’d list the allocation categories in plain words, then match each category to the best available evidence. The result is a story a reader can follow, not a pile of technical links.

Start with what your team knows. Record the token contract and network, the date of the calculation, and the amount issued at that point. Then identify public holdings, locked allocations, treasury balances, burns, or other changes that affect your proposed figure. Don’t label a balance “locked” without noting where the restriction is recorded and what its terms say.

If some information is not public, mark that clearly. Add a suitable record or explanation rather than presenting an unsupported claim as settled. CoinGecko has a separate profile process; our guide to getting listed on CoinGecko can help your team keep those platform materials distinct.

Which records help someone follow each balance?

The clearest evidence set pairs each important ledger row with a record that supports it. One document rarely explains the whole supply figure, so organize the file around the categories in your calculation.

Start with the token record

Include the contract address, network, and relevant explorer pages. Add a dated calculation that shows the arithmetic. If the token has migrated or uses multiple contracts, explain how the records relate and how you avoid counting the same units twice.

Add records for allocations and changes

Use the documents that match your token’s setup. For example, allocation materials can describe the planned categories, while a vesting or lockup record can explain conditions attached to a balance. Treasury or multisig addresses need a short note about their purpose. For a burn, mint, transfer, or migration, include the relevant transaction record and explain its effect on the calculation.

A practical evidence index might include:

• Ledger row or category name.
• Amount and reference date.
• Why the balance is included or excluded.
• Link or file that supports the explanation.

Treat this as a preparation list, not a claim that every item is required for every submission. Check CoinMarketCap’s current instructions before you send anything. Keep private records clearly identified, and include an appropriate extract or corroborating source when possible.

Use two passes to catch gaps before you submit

Two deliberate passes make the file easier to trust: one for the numbers, and another for the way the evidence reads. Give each pass a clear job, so small inconsistencies don’t hide inside a long document.

1. Set the reference point. Write down the contract, network, and date attached to the proposed figure. Use the same reference point throughout the ledger.
2. Map the balances. List each category and state whether it is included or excluded. Add the record that supports its treatment.
3. Recheck the arithmetic. Recalculate from the listed categories. Look for balances counted twice or changes that have not reached the ledger.
4. Compare public materials. Check the website and token documents for conflicting dates, terms, or figures. Update or explain any difference before submission.
5. Read it as someone new. Follow each total back to its source. Clarify rows that require guesswork, then keep a copy of the final file.

Say the project has a scheduled release and a recent treasury transfer. We’d check each event against its own record, then make sure the ledger reflects the right date and balance. That review doesn’t decide how a platform classifies the tokens; it helps your team explain the calculation it is proposing.

For a separate platform comparison, our guide to CoinGecko and CoinMarketCap listings covers why the two profile processes should be handled individually.

Leave CoinMarketCap’s review decision where it belongs

A careful evidence file helps explain your proposed supply figure, but CoinMarketCap decides how it interprets the records and whether its profile changes. Your team controls the calculation and supporting material, not the platform’s assessment or update timing.

That boundary is a reason to be precise, not a reason to overstate what the records prove. Describe the date and method you used. If a balance has a restriction, point to the record and explain the restriction in plain language. If an item is uncertain, say what is missing instead of hiding the gap behind a broad label.

Before sending the file, check the current CoinMarketCap instructions and make sure the links lead to the relevant pages. Keep your calculation, evidence index, and any later clarification together. If the platform asks about one category, you can answer from the record instead of rebuilding the full explanation.

Our listings and verification guides cover related profile preparation. They’re useful when your team is also preparing other token records and wants the definitions to stay consistent.

Keep the calculation ready for the next change

A supply ledger stays useful when someone updates it as token records change. Assign one person to note events that may affect the figure, such as a token release, burn, new issuance, or contract migration. Keep the supporting transaction or document beside the update.

When the figure changes, write down what happened, when it happened, which balance was affected, and how the arithmetic changed. Keep the earlier version too. That gives your team a simple history to refer to if a profile figure or a public document needs explaining later.

Check the ledger against the project’s public token materials before preparing an update. CoinGecko and CoinMarketCap are separate providers, so maintain one underlying source ledger but prepare platform-specific explanations. You can read more about how CoinMarketCap listing works and how CoinGecko listing works.

If you’d like us to check your file, send Brand Community the contract address and current calculation. Include allocation and lockup records, plus links to relevant transactions. We’ll compare the figures with the cited evidence and return a clear list of any gaps for your team to address.

How it works

1. Choose a reference pointRecord the contract, network, and date for the proposed figure. Keep that date consistent across the calculation and evidence.
2. List each balance categoryShow what is included or excluded and why. Link each important row to a source.
3. Recheck the arithmeticCompare the ledger with contract and wallet records. Account for burns, token releases, or migrations.
4. Compare the public explanationCheck the submission against the project website and token documents. Clarify differences before sending.
5. Keep the final recordSave the submitted calculation, evidence links, and any later clarification together.