DefiLlama and DappRadar listing: a named lead for each track

Two destinations, distinct listing arrangements

DefiLlama and DappRadar serve different listing purposes, so we prepare their materials separately. The distinction is easiest to see by identifying the entity and information each request concerns.

A project may need one track or both. The arrangement begins by confirming the protocol, product, and networks in scope; it does not assume that a token, protocol, and application are the same entity. If you are weighing other destinations as well, the listings and verification overview offers a broader view. This keeps the initial decision focused on what your team actually wants represented.

A composed evidence file before any submission

Useful listing materials make each project statement easy to trace to an appropriate public source. Before drafting, we gather the project name, official links, relevant networks, and references that help explain the protocol or dApp.

Your team remains the authority on technical facts. We organize the information and flag unclear points rather than filling gaps with assumptions. For a TVL request, the team should be able to explain which protocol components the requested representation concerns. For a dApp profile, the product name, description, and destination links should all point to the same application.

A practical starting file can include documentation, public product pages, deployment or contract references, and any earlier correspondence with either platform. One person on your side should be available to confirm technical details. Materials are kept private within the agreed coordination, and drafts are not submitted before your factual approval. Where adjacent directory work is needed, listings on other crypto trackers can be considered separately from these two requests.

How should the DefiLlama and DappRadar tracks be prepared?

Each track needs a description matched to its purpose. We first establish the project entity, then arrange the supporting information around the specific listing request.

DefiLlama TVL information

The preparation focuses on how your team describes the protocol and the TVL scope it wants represented. We help organize the explanation and relevant references so the materials are coherent and can be checked against public information. If the scope includes several components, your team should identify which belong in the requested representation before drafts are finalized.

DappRadar dApp information

Here, the focus is the application: what it does, which official links identify it, and the relevant network context. If the project has multiple products or deployments, the request should name the one intended for this profile. A single description should not imply that the listing covers every product automatically.

The separation also makes review easier for your own team. You can approve the protocol's TVL explanation independently from the dApp's public description. If your needs also include market access, centralized exchange listing support is a separate arrangement with different materials.

The materials your team receives

The handoff is designed to show what is ready, what needs your confirmation, and what has been submitted. At Premium Promotions, one named account lead coordinates the agreed work and keeps project questions with the appropriate people on your team.

• Readiness checklist: project identity, scope, official links, and open questions.
• TVL information set: organized DefiLlama materials and supporting references.
• dApp information set: separate DappRadar profile details and destination links.
• Approved drafts: descriptions shared with your team before they are used.
• Status record: submission details, platform responses, and follow-up items.

The exact package reflects whether one or both tracks are in scope. Your written factual sign-off is the point at which approved descriptions may proceed. If a clarification arrives, the account lead turns it into a clear request for the person best placed to answer. If a public profile appears, we compare visible information with the approved material and note any discrepancy for follow-up.

A measured handoff and clear boundaries

Nothing is submitted until your team has seen and approved the factual draft.

The account lead maintains a concise record of the materials sent, the status received, and any question that needs your input. Your team can see the difference between preparation, submission, a platform response, and a publicly visible profile. That distinction keeps reporting clear and avoids describing an unresolved request as a completed listing.

DefiLlama decides whether supplied information supports its TVL presentation, while DappRadar controls its own dApp review and profile display. Acceptance, review timing, ranking, and continued display remain their decisions; our report covers the work completed and public details we can verify.

Before kickoff, agree who confirms technical facts and who approves descriptions. A short internal route for those decisions helps keep the preparation composed, particularly when multiple people own product, protocol, and communications information.

A private route from scope to submission

The arrangement is most straightforward when the project entity and intended track are named at the outset. We confirm whether the request concerns DefiLlama, DappRadar, or both, then align the evidence checklist and approval route to that choice.

The working sequence is simple:

1. 01 — Confirm the scope: identify the protocol, dApp, and relevant networks.
2. 02 — Gather the evidence: share official links, documentation, and technical references.
3. 03 — Prepare drafts: receive separate materials for factual review and sign-off.
4. 04 — Coordinate submission: the account lead records status and routes questions to your team.
5. 05 — Check what is visible: where a profile becomes public, compare it with the approved information.

If you also need exchange or DEX visibility, keep those objectives distinct; DEX listing and liquidity setup covers a different preparation. For an initial conversation, which protocol and dApp should we place in scope, so your named contact can confirm the tracks and outline the next steps within 2 working days?

How it works

1. 01 — Confirm the listing scopeIdentify the protocol for the DefiLlama TVL request and the product for the DappRadar dApp request. The account lead confirms which entities and networks are in scope.
2. 02 — Gather project evidenceShare official links, documentation, relevant contract or deployment references, and a contact who can confirm technical details. We note missing or inconsistent information.
3. 03 — Prepare separate draftsWe organize TVL information and dApp profile information for their respective purposes. Drafts go to your team for factual review and written sign-off.
4. 04 — Coordinate submission and follow-upAfter approval, we coordinate the agreed submissions and record status, responses, and questions requiring your input.
5. 05 — Check visible profilesIf a listing becomes public, we compare visible details with the approved information and record discrepancies for appropriate follow-up.