Tracker listing is where a token stops being a contract address and becomes something people can search for. It is also the step projects most often attempt too early, get rejected without explanation, and then repeat with the same material.
The trackers do not publish their thresholds and will not tell you why a submission failed. What follows is the order that avoids the predictable rejections.
1. Do not submit until there is trade history
The trackers exist to report market data. A token with a pool created yesterday and four transactions has no market data to report, and the submission is declined on that basis alone.
Give the pool time to accumulate genuine trading across multiple days and multiple wallets. A burst of volume from a handful of addresses is worse than no volume, because it reads as manufactured and the reviewer has seen it a thousand times.
2. Make the explorer page do the work
Verify the contract source, add the token logo through the explorer’s own process, and make sure name, symbol and decimals resolve correctly. Reviewers open the explorer first, and a page that answers their questions without an email exchange gets processed faster.
If the token exists on several chains, do this on each of them. A submission that lists three chains and has one verified contract raises the exact question you do not want asked.
3. Fix the supply figures before anyone asks
Total supply, circulating supply and the addresses excluded from circulation are the numbers most likely to stall a submission. Trackers publish circulating supply and are held responsible for it, so they are conservative about accepting a figure they cannot verify.
Prepare a public page that lists every excluded address with what it holds and why: team allocation, treasury, locked rounds, burn address. If the exclusions are not checkable on chain, expect the higher figure to be published instead, and expect that to surprise your community.
4. Have the channels a reviewer expects to find
A website that explains what the token does, a public community room with actual activity, and a social account posting more than announcements. These are checked, and an abandoned channel is worse than a missing one because it suggests the project stopped.
Press coverage is not a formal requirement, and it does answer the question a reviewer is implicitly asking, which is whether anyone outside the project has noticed it. Where the coverage lands and which outlets carry a followed link is documented on our crypto PR page.
5. Submit once, completely
Partial submissions are not held open pending more information. They are declined, and resubmitting too soon after a rejection is itself a negative signal on some trackers.
Assemble everything first: contract addresses per chain, pool or market links, the supply breakdown with excluded addresses, the website, the channels, a description that says what the thing does rather than what it will disrupt.
6. Expect silence, and do not chase it
Review queues are long and the trackers do not provide status updates. Repeated follow-ups through multiple channels are the most reliable way to be deprioritised.
If a submission is declined, the useful response is to identify which of the above was thin, fix it, wait, and submit again with something materially different. Submitting the same package again produces the same result.
7. Maintain the listing after it appears
A listing is not a permanent state. Trackers flag and eventually delist assets whose volume collapses, whose contracts go quiet, or whose supply data stops matching the chain.
Update circulating supply as vesting unlocks land, add new chain deployments as they happen, and keep the linked channels alive. Most delisting warnings arrive because nobody updated anything for a year.
What the trackers will not do
- Explain a rejection. There is no appeal and no feedback.
- Accept an unverifiable circulating supply. If exclusions are not checkable on chain, the higher figure is published.
- Treat manufactured volume as volume. Concentrated trading from few addresses is a documented rejection reason.
- Guarantee timing. Queues vary and no paid route changes the underlying requirements.
The full set of trackers and exchanges worth submitting to, with what each one requires, is on our exchange and tracker listing page, and the liquidity work that has to happen first is covered in our token listing sequence.