CoinMarketCap circulating supply: build a traceable wallet evidence file

What does a CoinMarketCap supply figure need to explain?

A dated supply calculation shows the figure, its source data, and the treatment assigned to relevant balances. It should distinguish issued supply from the amount your project proposes as circulating. Those values are not interchangeable, and labels alone do not explain the difference.

Start with 3 definitions in the project file:

• Issued supply: tokens created under the token’s design, based on a stated source and calculation time.
• Proposed circulating amount: balances the project classifies as available, following its written inclusion rules.
• Excluded balances: holdings treated as unavailable, each linked to a reason and supporting record.

Then compare the proposed figure with the public tokenomics, explorer data, and allocation records. They should describe the same token and the same point in time. If they do not, identify the mismatch before preparing a submission. A useful table records the source figure, the adjustments, and the resulting calculation. This helps a reviewer trace the arithmetic without relying on internal explanations.

The project can document its reasoning, but should not present its classification as CoinMarketCap’s settled treatment. Keep supply evidence separate from a listing application. The CoinMarketCap listing guide covers that distinct submission task.

Which wallet records make the calculation auditable?

A wallet schedule connects each balance to an address, a label, and a decision. A spreadsheet becomes useful when a second person can check its entries against the supporting sources.

Use one row for each relevant address or contract. Include these 6 fields:

Mark uncertain labels as unresolved. Do not infer a wallet’s purpose from an address name or a private team note. For a project-controlled wallet, include a short explanation of control and intended use. For a restricted allocation, attach the record describing the restriction and its conditions.

Record the calculation date and preserve the original snapshot. That makes it possible to distinguish a later balance change from an earlier submission. Where tokens exist on multiple networks, identify each chain and contract separately. Do not combine representations until the project has documented how they relate. The resulting schedule should let a reviewer trace the address, observed balance, classification, and evidence without searching through unrelated files.

How can you test the supply arithmetic before submission?

A reconciliation table makes each adjustment visible between the source supply value and the proposed circulating amount. The arithmetic should be reproducible from the wallet schedule, not dependent on an unexplained summary number.

First, record the source value and when it was checked. Then total the balances your method includes and the balances it excludes. Compare those totals with the reported supply. If they do not reconcile, write down the reason rather than hiding the difference in a note.

Check these 4 points before approving the working figure:

• Coverage: Are all relevant addresses and contracts represented?
• Treatment: Does each inclusion or exclusion have a stated reason?
• Timing: Were balances and supporting records checked at a consistent point?
• Adjustments: Are rounding, migrations, or bridged representations explained?

Keep unresolved items separate from confirmed entries. If a restriction depends on a vesting agreement or an operational condition, point to that evidence. If the condition is not documented, do not treat the classification as established. Use the same labels in the calculation, tokenomics, and submission summary. A reviewer should be able to move from the final figure back through each adjustment to its source. For a separate evidence review, see circulating supply verification.

What belongs in the CoinMarketCap supply evidence pack?

A compact evidence pack presents the proposed figure first, then gives the records needed to check it. Organize the materials so the calculation can be reviewed without guessing which file supports each claim.

Use this order:

1. Summary: token name, ticker, chain, contract address, calculation date, and proposed figure.
2. Method note: source supply value, inclusion rules, exclusion rules, and calculation steps.
3. Wallet schedule: addresses, balances, labels, treatments, and source links.
4. Allocation records: tokenomics and relevant team, investor, treasury, ecosystem, or community allocations.
5. Restriction evidence: vesting terms, lock records, burn evidence, or other documents supporting exclusions.
6. Open items: unclear classifications, missing records, and the person responsible for resolving them.

Check that names, addresses, and figures match across the summary and attachments. Give every file a clear name and retain its source and check date. A spreadsheet without explorer links is difficult to verify. An explorer link without a reason for exclusion does not establish the project’s classification.

This is a practical evidence structure, not a claim that CoinMarketCap uses a fixed checklist. Review the platform’s current submission instructions before sending materials. Keep confidential agreements restricted, and include only the details needed to explain the relevant balance. For comparison, the CoinGecko listing guide describes a separate provider’s listing process; confirm its current requirements independently.

How should a project check the submission file?

A final review compares the submission summary, wallet schedule, and source documents as one dated record. The aim is to find contradictions before the materials leave the project team.

Assign one person to prepare the file and another to check it. The second reviewer should verify the contract address, open each source link, recalculate the totals, and compare labels across documents. They should flag any address that lacks a source or has a treatment that conflicts with the project’s own records.

Use this short handoff checklist:

• Confirm the token and network named in every document.
• Open each explorer and document link from the working file.
• Recalculate the included and excluded balances independently.
• Match the summary figure to the calculation date and method.
• Mark unresolved items instead of presenting them as confirmed.

Submit through CoinMarketCap’s current channel and retain the exact files sent. Keep any confirmation with that version. If a reviewer requests clarification, answer against the same dated schedule and document any correction in a new version. A clearly organized handoff also makes ownership visible: the project knows who prepared the calculation and who checked its evidence. If the task is actually a profile correction, keep it separate from the supply file and use the relevant platform instructions.

When should the wallet schedule be recalculated?

A changed balance, restriction, or token representation can make an earlier supply schedule incomplete. Revisit the calculation when an event affects the amount or classification your project reports.

Review the file after a mint, vesting release, migration, burn, or movement between project-controlled wallets. Check whether the event changes issued supply, the proposed circulating amount, or only the label assigned to an existing balance. Record the transaction or contract evidence, then produce a new dated version. Preserve the previous calculation rather than overwriting it.

A practical update routine has 4 checks:

• Compare the current address list with the last saved schedule.
• Review changed balances and new addresses against allocation records.
• Recalculate with the stated rules, or document a method change.
• Align tokenomics and public explanations when they use the same figure.

Maintain a change log with the event, source, affected addresses, calculation version, and file owner. This gives the team a clear record of why a figure changed. It also helps prevent an old number from appearing in a new submission after the supporting balances have moved. For a project comparing providers, CoinGecko listing guidance is a separate reference, not a substitute for checking the current CoinMarketCap process.

Where does CoinMarketCap make the final supply decision?

The evidence pack records the project’s calculation and the sources behind its proposed treatment. CoinMarketCap controls how it reviews submitted information, classifies supply, and displays any resulting figure; a project cannot set that decision or its publication timing.

Make unclear evidence visible before submission. If a wallet’s role depends on an agreement, lock condition, or operational control, explain the condition and attach the supporting record. If the project cannot substantiate a classification yet, mark it unresolved. Do not describe an assumption as a confirmed fact.

Supply work also differs from visibility activity. A trending placement does not substantiate a circulating-supply calculation, and a supply file is not a listing application. If you are planning both tasks, keep the records and goals separate. The CoinMarketCap trending guide covers that distinct topic.

For a useful first review, send the token’s chain and contract address, the latest tokenomics and vesting records, and the current wallet schedule. GeoMarketing Experts can check the arithmetic against those sources and return a specific list of missing records or unclear classifications. You can then resolve those gaps before submitting the dated file.

How it works

1. Set the calculation scopeRecord the token, chain, contract address, calculation date, and rules for classifying balances.
2. Gather source documentsCollect explorer links, tokenomics, allocation records, vesting terms, and evidence for exclusions.
3. Build the wallet scheduleLabel each relevant address, record its balance, and link the evidence for its treatment.
4. Reconcile and reviewRecalculate included and excluded totals, open each source, and flag unresolved classifications.
5. Submit and preserveUse CoinMarketCap’s current channel and retain the exact dated materials sent.