What does CoinGecko supply verification involve?
CoinGecko supply verification means presenting a traceable explanation of the supply figure associated with your project. The central task is not simply to state a number: it is to show how you arrived at it and what records support the treatment of tokens that are locked, reserved, burned, or otherwise excluded from the figure you report.
Start by writing down your project’s definitions. Distinguish circulating supply from total supply and maximum supply where those concepts apply to your token. State the figure and the date or block context used for your calculation, then describe the calculation in plain language. Do not assume that a familiar label means your project and a data platform are using identical criteria.
A good packet lets someone follow a short chain of evidence:
- Which token and network are being discussed?
- What is the source value for the calculation?
- Which balances are included or excluded, and why?
- What public records support each adjustment?
This clarity matters beyond a single profile update. Consistent supply information helps readers compare project sources and gives search systems a more coherent account of the token. It does not, by itself, determine how CoinGecko or an AI answer presents the project.
Which documents should you prepare to verify circulating supply?
Prepare a compact evidence packet that connects your supply calculation to records a reviewer can inspect. The exact material depends on how your token is issued and managed, so treat this as a preparation checklist rather than a claim that every item is required by CoinGecko.
| Record | What it should clarify |
|---|---|
| Token and network details | The asset, chain, and relevant contract address |
| Supply calculation | The source figure, calculation date, and included balances |
| Wallet or contract references | Which addresses hold project, treasury, vesting, or reserve tokens |
| Lock or vesting evidence | The applicable schedule and a public source where available |
| Burn evidence | The transaction or address record supporting a stated burn |
| Project explanation | Who controls relevant allocations and how they are treated |
Use a short index at the top of the packet, with a link or filename beside each claim. If an allocation is managed off-chain, explain that clearly and attach the records you can disclose to substantiate it. If a document contains confidential details, do not expose sensitive material in a public link; ask what submission route is appropriate.
Keep the evidence readable and consistent. A reviewer should not have to infer which wallet belongs to which allocation or reconcile several conflicting supply figures. For help with the broader circulating supply verification service, organize these records before discussing scope.
How do you reconcile on-chain balances with the reported figure?
Reconcile the figure by starting with the token’s observable supply data, then documenting every adjustment that changes the number you intend to report. The objective is an auditable explanation, not a spreadsheet that merely repeats the final value.
Build a working table with one row per relevant allocation. Include the address or record, its role, the balance or amount used, whether it is included, and the reason. Where an adjustment depends on a lock, vesting arrangement, treasury designation, or burn, point to the evidence that supports that treatment. Keep the calculation method visible so another person can reproduce it from the listed inputs.
Before sending anything, check these common sources of confusion:
- A project wallet is described as locked without a supporting schedule or contract reference.
- A burned amount is counted twice, or the evidence does not match the token contract.
- The website, announcement, and submission packet show different supply figures.
- An allocation is excluded without explaining its status or control.
If you have migrated contracts or multiple token versions, identify which contract the calculation covers and explain how prior balances are treated. For adjacent profile data, the explorer token information and logo update service addresses a separate update task; it does not replace supply evidence. Keep the supply calculation and profile assets as distinct workstreams.
How should you prepare a CoinGecko supply verification request?
Prepare the request so the reviewer can identify the token, understand the calculation, and open the supporting records without chasing missing context. First, check CoinGecko’s current official instructions, because the submission route and requested details can change. The CoinGecko Support Center is the appropriate starting point for current guidance.
Then assemble a concise cover note. State the project name, token ticker, network, contract address, the supply figure you are asking to have reviewed, and a plain-language summary of the calculation. Add a numbered evidence index and make sure every link works without requiring access to a private account. If the official form asks for fields in a particular format, follow that format rather than relying on a custom document alone.
Before submission, run a consistency check:
- Compare the packet against the public project site and token references.
- Confirm each address belongs to the stated network and allocation.
- Make sure dates, units, and token decimals are used consistently.
- Remove unsupported claims and label estimates as estimates.
Save a copy of the final packet and the communication record. This gives your team a reliable reference if a question requires clarification or a revised document. For a related listing workflow, see the guide to CoinGecko listing preparation; listing materials and supply evidence may overlap, but they answer different review questions.
What can delay a CoinGecko supply review?
The most useful quality check is whether a person unfamiliar with your project can trace each reported figure to its source and understand each exclusion without guessing. Review the packet from that person’s perspective before sending it.
Look for gaps between the calculation and the evidence. If a wallet is described as a vesting wallet, provide the schedule or public reference that supports the description. If the project uses a multisig or custodian, explain its role without implying that the label alone proves a balance is unavailable. Where information is not public, say what you can substantiate and use the official channel to ask how to provide any additional material.
CoinGecko controls its review, the interpretation of evidence, profile updates, and when or whether displayed supply data changes; a complete packet cannot compel a particular decision or timing. Your team can control the accuracy, clarity, and provenance of the information it submits, so prioritize those elements over presentation polish.
After sending the request, monitor the relevant project contact channels and respond with targeted evidence if asked. Avoid sending a new, conflicting figure in a follow-up: identify what changed, provide the supporting record, and explain the revised calculation. A focused correction is easier to assess than a second packet with no change log.
How does supply verification support a project’s search presence?
A well-documented supply figure gives readers a consistent reference point across the project’s own materials and third-party profiles. That consistency can support clearer search results and AI-generated answers, but it is the quality and agreement of the underlying sources—not a verification request alone—that make the information useful.
Create a simple source record for the team. Note the approved supply definition, the calculation date, the evidence location, and who is responsible for updates. When tokenomics or allocations change, revise the calculation and the public explanation together. Do not leave an old figure on one page while publishing a new one elsewhere.
Use the same discipline for related project details: official token names, network, contract references, and links should agree wherever the project maintains them. A CoinGecko supply verification guide for CoinMarketCap can help teams compare preparation needs across platforms without assuming their review processes are identical. If you also need to update a wallet-facing token asset, review the wallet logo and token-list inclusion service separately.
If you want support, send AIPromote the token and network details, your current calculation, and the evidence index. We begin with an AI Presence Scan to spot inconsistencies in the project’s public supply references, then map the records into a clear Source Plan for the verification work.
Frequently asked questions
What documents do I need to verify circulating supply on CoinGecko?
Prepare a supply calculation, token and network details, relevant contract or wallet references, and evidence for any exclusions such as burns, locks, or vesting. The appropriate records vary by project structure. Check CoinGecko’s current official instructions before submitting, and label each item so the calculation can be followed.
Does a locked token allocation count as circulating supply?
Do not assume the answer from the label “locked” alone. Explain the allocation, how it is controlled, what schedule or contract applies, and how your project treats it in its stated calculation. Include evidence that supports the treatment, then follow the platform’s current review guidance.
Can CoinGecko guarantee that it will accept my supply calculation?
No. CoinGecko makes the review decision and determines how submitted evidence is interpreted and reflected on its profile. Your team can improve the request by providing a consistent calculation, traceable sources, and clear explanations, but those steps do not determine the platform’s decision.
Should I submit supply verification and a CoinGecko listing request together?
They are related but distinct tasks. Listing materials establish project and asset information, while supply evidence explains how a particular figure is calculated. Check the current instructions for each request and keep the documents aligned so that project details do not conflict.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…