CoinGecko or CoinMarketCap: what changes in the application?
1 shared fact sheet can support both applications. Each platform still needs its own form and record.
| Option | What can stay shared | What to check separately |
|---|---|---|
| CoinGecko | Project name, ticker and public facts | Current form, requested fields and follow-up |
| CoinMarketCap | Contract, market and supply sources | Its own request route and review status |
| Both platforms | One source document for verified facts | Separate submissions and platform-specific answers |
A shared document cuts down on mismatched project details. It does not make one platform’s submission valid for the other. Check the fields in each current request route. Then adapt your answers to that form. Keep each confirmation and reply in its own record.
For the second platform’s process, see the CoinMarketCap listing guide. Keep listing preparation separate from visibility campaigns. CoinGecko trending covers a different task.
6 checks before the CoinGecko form
6 checks make the application easier to verify. Gather the facts first. Then compare them against the current official guidance and form.
- Identity: match the project name and ticker across public pages.
- Network: state the token network and link to the relevant explorer record, where applicable.
- Contract: verify the address shown on project pages and market listings.
- Markets: collect direct links to live venues and relevant trading pairs.
- Supply: label each figure and note its public source or calculation.
- Channels: check that the project’s public channels are current and accessible.
- Sources: confirm every URL opens without a login and points to the right asset.
Put these items in one working document.
- Token versions: label the active version if your project has multiple versions, a migration or a bridged asset.
- Unknown fields: mark any detail for your team to resolve. Do not fill it with a guess.
- Application support: the CoinGecko listing service can help organize the request record.
- Related preparation: the listing and verification hub covers related preparation.
5 steps from readiness check to follow-up
5 project-side steps take you from preparation to a saved follow-up record. Each window is a work phase. It is not a promised platform turnaround.
- Read current guidance — Window: before preparation. Note the fields and conditions that apply to your asset.
- Assemble evidence — Window: before the form. Collect direct links for identity, contract, markets, supply and channels.
- Reconcile details — Window: before submission. Compare names, tickers, networks, addresses and supply labels across sources.
- Submit and save — Window: at submission. Use the current official route. Save your answers and record the submission details.
- Monitor and respond — Window: after submission. Watch the contact channel used. Answer a specific follow-up with relevant evidence.
Keep one person responsible for the final answers. If a key fact changes after submission, record it. Examples include the active contract or a market link. Use the official route to send a concise correction. Avoid sending repeated copies that add no evidence.
How do you make CoinGecko supply figures traceable?
3 supply labels need clear definitions: circulating, total and maximum supply, where those figures apply. Give each figure a source. Explain how your team calculated it, if applicable.
Start with a short supply note. List the label, value, source and method. Link to a public contract or other evidence where possible. If circulating supply is calculated, describe the calculation and exclusions in plain language. Use the same definitions on your website and in the application.
Check whether treasury or vesting wallets affect your figures. Also check locked allocations, burns, bridged versions and contract migrations. Explain any detail that changes what a reader sees. Do not present a supply number without saying what it represents.
Before submission, compare the note against the explorer record and project pages. Check any supplied market information as well. Flag differences for your team to resolve. For help organizing public supply evidence, review the supply verification service. Confirm each cited source supports the specific figure.
CoinGecko controls review and profile status
1 platform controls the listing decision, review schedule and any warning shown on a profile. An application helper can organize evidence. It cannot determine CoinGecko’s decision or set its review window.
If the profile has a warning, first identify the information or policy issue it refers to. Compare the affected profile details with your public sources. Then gather evidence that addresses that exact point. Changing promotional wording without fixing a data mismatch leaves the central question unanswered.
Use a short correction record:
- Warning text: save the wording and the affected profile field.
- Source: link the public page or contract record that supports the correction.
- Change: note what changed and when your team updated its own materials.
- Reply: send only the evidence relevant to the platform’s question.
Keep a copy of correspondence and submitted changes. For visibility after a listing, assess the separate CoinGecko trending guide. A listing request and a trending campaign are not the same application.
3 records to prepare with DigitalMedia1
3 records give your team a clean handoff: the project fact sheet, evidence links and a saved submission copy. DigitalMedia1 can review those materials for mismatches. We can flag details that need your confirmation and help organize answers against the current form.
| What you get | When | How we log it |
|---|---|---|
| Fact sheet with project and token details | Before the form | One checked version for team approval |
| Evidence list for markets, supply and channels | During preparation | Direct links beside the facts they support |
| Submission and follow-up record | At and after submission | Saved answers, request details and replies |
Your team confirms project facts and approves the final submission. That separation keeps the record useful if a field changes or the platform asks for clarification. It also helps prevent an outdated link from being reused in a later request.
Send the project website, contract address and market links to the CoinGecko listing service. We’ll review the records and flag the first gaps. Then we’ll map the next form step.
How it works
- Check current guidanceWindow: before preparation. Note the current fields and conditions that apply to your asset.
- Collect public evidenceWindow: before the form. Gather the website, contract and explorer details, market links, supply sources and active channels.
- Reconcile project factsWindow: before submission. Compare names, tickers, networks, contracts, markets and supply definitions across sources.
- Submit and saveWindow: at submission. Complete the current official form with direct links. Save the answers and request details.
- Monitor follow-upWindow: after submission. Watch the contact channel used. Answer any specific request with relevant evidence.
Frequently asked questions
Which project details does CoinGecko ask applicants to provide?
6 preparation checks cover project identity, network, contract, markets, supply and current channels. Verify the current CoinGecko guidance and form for requirements that apply to your asset. Treat the checklist as a way to prepare evidence, not as a replacement for the platform’s criteria.
Where is the current CoinGecko listing form?
1 official support route is the place to find CoinGecko’s current instructions and request form. Use the platform’s support site rather than a copied form or an old link from a chat. Save your submitted answers and source links so your team can reply consistently if asked.
How long does a CoinGecko listing review take?
1 review window is set by CoinGecko. Do not schedule a launch around an assumed decision date. Your team can control preparation and how quickly it answers a request for clarification. Keep a record of the submission and leave your launch plan flexible until the platform responds.
How should I verify supply on CoinGecko?
3 supply labels—circulating, total and maximum—need definitions and sources where they apply. Link each figure to public evidence. Explain any calculation in plain language. Compare the labels and values across your website, explorer information and application before submitting.
What should I do if CoinGecko shows a warning?
1 warning record should capture the displayed text, affected field and supporting source. Identify the underlying data or policy issue before sending a correction. Then use CoinGecko’s official route and provide evidence that addresses the specific point. A wording change alone may not resolve a profile issue.
Can one CoinGecko request cover CoinMarketCap too?
2 platforms mean 2 separate request routes and review records. Reuse a fact sheet to keep project details aligned. Check each current form and answer its requested fields. A CoinGecko submission does not apply to CoinMarketCap; see the CoinMarketCap listing guide for that process.
How is help with a CoinGecko application quoted?
3 things shape the quote: the platform task, the preparation needed and the review of your records. You get a fixed written quote within 2 working days, before you pay. Send the project website and current materials first so the quote reflects the work you actually need.
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…