DefiLlama and DappRadar listing: prepare evidence for each track

Which evidence belongs in each listing track?

The first review produces 2 separate evidence maps: one for DefiLlama TVL and one for DappRadar dApp information. This split keeps protocol facts distinct from details visitors use to understand an application.

For DefiLlama, we organize the protocol identity, relevant networks, contract references, and project-provided TVL context. Your team supplies the sources behind each claim. For DappRadar, we focus on the dApp name and a clear product description. We also record supported networks and a working application link. Shared facts, such as the official project name, remain consistent across both packs.

A project with protocol infrastructure and a user-facing interface may need both tracks. A project seeking a directory profile for its application may only need the DappRadar track. We confirm the intended scope before preparing materials. This avoids combining unlike details into one generic submission.

The wider listings and verification scope can help coordinate other project profiles. For a market-access goal, review DEX listing and liquidity setup separately; these listing requests do not cover that work.

What source records make a submission easier to verify?

A source register connects each project claim to a public destination your team can check. We start with 6 information groups and flag missing or conflicting items before drafting the submission materials.

• Identity: official project name, product name, and approved description.
• Product access: website and direct link to the live application, where relevant.
• Network scope: supported networks and the contracts or explorer pages tied to them.
• Product evidence: public documentation explaining the protocol or application.
• TVL context: the project’s explanation of relevant figures and their sources.
• Ownership: a contact who can confirm technical and editorial details.

Keep claims within what your sources show. If a metric or product detail has changed, record its source. Confirm the current version with your team. We do not fill gaps by inference. Instead, we return a list of questions for the right project owner to resolve.

A token or contract detail may need a different review track. See circulating supply verification for supply records, or contract migration and rebranding updates when project identity or contract references have changed.

How do DefiLlama and DappRadar materials differ?

The track comparison records a different primary object for each request: protocol TVL context for DefiLlama, and a usable dApp profile for DappRadar. The facts can overlap. The evidence and description should match the destination.

We keep 1 shared fact register alongside 2 track-specific evidence packs. That gives product, engineering, and communications owners a common reference. It also avoids making both submissions read alike. For each claim, the register can record the wording, source URL, owner, and last checked status.

Before approval, ask the relevant owner to open every link and confirm its destination. Then compare the public project name and product description across the website, documentation, and submission text. If tracker coverage is also in scope, review listings on other crypto trackers and decide which records need their own source pack.

What records will your team receive from the engagement?

The handover contains a readiness summary, approved submission materials, and a status record. Each item is tied to a specific track. Your team can see what is ready and what still needs a project decision.

The working file uses 5 fields for each evidence item: claim, source, track, owner, and status. We adjust the file to the project’s scope. The status record notes the materials coordinated and platform responses shared with us. It also records open questions and the next action assigned to your team. It is a practical reference for future updates, not a claim about platform outcomes.

The engagement can include:

• A source review that flags missing or inconsistent project facts.
• Separate DefiLlama and DappRadar submission drafts, as applicable.
• An approval checkpoint before the materials are used.
• Coordination of the agreed request and a written follow-up record.

Your team retains control of factual claims and final approval. If a token profile also needs attention, CoinGecko listing support and CoinMarketCap listing support are separate scopes. We can use a shared fact register, then adapt evidence for each destination.

How does the evidence move from intake to submission?

The work record follows 5 checkpoints, from source intake through follow-up. Each checkpoint leaves a clear artifact for review. Your team can resolve questions before materials move forward.

1. Intake: You share the official website, application link, network details, references, and project contact.
2. Track selection: We record whether the scope covers DefiLlama TVL, DappRadar dApp listing, or both.
3. Source review: We compare supplied facts with linked public sources. We list gaps for your team.
4. Approval: We prepare the track-specific text and evidence pack for your review before coordination.
5. Follow-up: We maintain a written status record of actions, responses, and outstanding items.

We confirm the schedule after seeing the source set, number of tracks, and approval needs. A named contact helps route technical questions to the right owner. This supports timely internal decisions. Our how we work page explains how approvals and responsibilities are handled across engagements.

Keep the approved description, source links, and contract references together after handover. When a fact changes, your team can identify the affected record. Then provide the current official source for review.

Which decisions remain outside the project’s evidence file?

A complete evidence file documents your claims; it does not decide how a platform evaluates them. DefiLlama and DappRadar control their own eligibility reviews, categorization, publication, timing, and profile visibility. GeoMarketing Experts cannot promise acceptance or continued display. We commit to the agreed preparation, coordination, and reporting work.

Before approving a request, check that every factual statement has a source. Confirm that every link leads to an official project destination. Make sure the named contact can answer questions about product details or network references. Keep the final approved pack internally, including the status record. Your team can then respond consistently if details change.

If a contract, product route, or project name changes after coordination, send the updated source and identify the affected track. We can compare it with the approved materials and agree whether follow-up fits the current scope. For other profile corrections, DEXTools and DEXScreener profile updates address a different set of records.

When should you align other project profiles with these requests?

A shared identity file is most useful when several profiles rely on the same project name, product description, or official links. Align those facts first. Then adapt the evidence to each destination instead of reusing one submission unchanged.

Coordinate related profile work when the project’s public identity is stable. The owners of product, protocol, and communications details can review the source register. If those facts are still changing, begin with the DefiLlama and DappRadar readiness review. That gives your team a record of unresolved items before it prepares other submissions.

For a broader tracker plan, start from listings and verification and select only the records relevant to your project. Keep a single approved source for the official name, product summary, networks, and links. Then assign an owner to maintain that source as the project changes.

To begin, send GeoMarketing Experts your project website, application link, relevant networks, contract or explorer references, and the track you want assessed. We will review those materials and return the gaps and proposed scope. We will wait for your approval before coordinating the request.

How it works

1. Send the source setShare your website, application link, networks, contract or explorer references, and project contact.
2. Select the listing trackConfirm whether the request covers DefiLlama TVL, DappRadar dApp information, or both.
3. Review claims and sourcesWe compare the supplied facts with public links and flag gaps for your team.
4. Approve the evidence packYour team reviews the track-specific description and source records before coordination.
5. Receive the status recordWe document coordinated materials, responses shared with us, open questions, and next actions.