DefiLlama and DappRadar listings for a DeFi project: two requests, one prepared pack

What the two-site listing service covers

Quick test: Can you point to your contracts, a TVL source and a public doc in 3 links? If not, gather them first.

It covers preparation and coordination for two distinct platform requests: a TVL listing on DefiLlama and a dApp listing on DappRadar. The work is useful for a DeFi team that wants its project information presented clearly and needs an accountable person to organize the submission work.

The two requests should not be treated as interchangeable. DefiLlama is relevant to the project's TVL presentation; DappRadar is relevant to presenting the application as a dApp. We map the project’s product, network, public links, and available evidence to the information each request calls for, then flag missing or conflicting details before anything is sent.

This is a fit when your project is live or has a clearly described product and you can provide accurate, public-facing information. If your priority is a token profile on price trackers, an exchange listing, or visibility placements, those are different plans. Our listings and verification overview can help pick the right route, while other crypto tracker listings cover a separate category of platforms.

The practical outcome is a submission process your team can follow and verify, not a promise of acceptance. You keep control of project claims and access; we help turn the material you approve into a coherent request.

What to prepare before requesting a listing

A useful submission starts with a consistent project record. Before outreach, gather the information your team can verify and publish; gaps are easier to address before submission than in a follow-up exchange.

Prepare a compact folder containing:

• The project name, concise description, product status, and official website.
• The relevant network and links to the live application or protocol interface.
• Public documentation and official social or community channels.
• The project’s explanation of how TVL should be understood, with sources the team can stand behind.
• Any relevant contract or explorer links, plus the person authorized to answer technical questions.

For TVL-related information, be ready to explain the project’s structure and provide traceable references for the figures or components you submit. We do not invent or revise figures to make an application look stronger. If a figure, contract, network, or product description differs between your website and documentation, resolve the inconsistency or explain it before submission. Projects handling token supply questions can review our separate circulating supply verification support.

For DappRadar, make sure the application can be described plainly: what it does, who uses it, and how a visitor can reach it. The goal is not to add promotional language, but to make the product legible to someone reviewing the public materials without inside context. We note unresolved items and agree with you on whether to proceed, clarify, or pause.

How do the two requests differ?

The DefiLlama request centers on presenting a DeFi project and its TVL-related information; the DappRadar request centers on presenting the dApp itself. We build one shared source of project facts, then tailor the relevant details for each platform instead of sending an identical, generic pitch twice.

This distinction matters when a protocol has several interfaces, products, or networks. Decide which product is the subject of each request and state the relationship between them. If a single brand name covers multiple applications, document that structure so a reviewer can understand what the listing represents.

Our team can review the public materials, organize the submission information, and coordinate follow-up with the project contact. You approve the wording and evidence before anything is submitted. If your project also needs a decentralized exchange or liquidity setup rather than a directory listing, see DEX listing and liquidity setup; it addresses a different operational goal.

Your 6-point DefiLlama and DappRadar checklist

Check these 6 points before you send a request. One reviewed pack serves both sites, and reviewing it first avoids two rounds of corrections with two different teams over the following weeks. Print the list, tick each line with a pen, and keep it next to the brief so everyone works from the same page.

1. Gather contract addresses on every chain.
2. Link docs and a TVL data source.
3. Write a 3-line description.
4. Prepare logo files.
5. Check how the project appears today.
6. Name one contact for both teams.

Terms in one line

TVL (in plain words: total value locked, the value of assets deposited in a protocol).

Pack means the set of facts and links sent with a listing request.

How the listing work is coordinated

Rule of thumb: Check how the project is described on both sites. A mismatch looks sloppy to readers.

We start by confirming what you want listed and what evidence is ready, then keep the two platform requests separate where their information needs differ. A project lead at MarketingExtra coordinates the work with your designated contact, so questions about product facts and approvals have a clear owner.

The workflow is practical:

1. Plan the request. Confirm the protocol, dApp, networks, desired platform coverage, and project contact.
2. Review the source material. Compare the website, documentation, application links, and submitted project details; list discrepancies and missing evidence.
3. Prepare platform-specific information. Draft the relevant TVL and dApp descriptions from facts you approve, keeping claims traceable to public sources.
4. Confirm and submit. You review the final materials; we coordinate the agreed requests and retain a record of what was sent.
5. Track the response. We share platform replies or visible status changes, identify requested clarifications, and coordinate next steps with you.

The project team should assign one person who can approve public claims and obtain technical answers. That makes review more efficient and prevents different versions of the product description from circulating. Timing is discussed after the initial review, based on readiness and plan; we do not treat a submission date as a platform decision date.

You receive a written summary of the materials reviewed, submitted information, open questions, and follow-up actions. For a broader overview of our approach, see how we work.

What lies outside our control

We control the quality and coordination of the agreed work, but each platform controls whether it accepts, changes, displays, or declines a listing. DefiLlama’s treatment of submitted TVL information and DappRadar’s review or presentation of a dApp are platform decisions; neither acceptance nor a particular display outcome can be promised.

That is why we keep the work verifiable. We can ensure that the information we prepare matches the facts and evidence you approve, that the agreed requests are coordinated, and that you receive a record of follow-up. We cannot make platform decisions on your behalf or represent that a listing is approved before the platform confirms it.

Before starting, agree internally on who can substantiate each claim, whether the relevant application is accessible, and how quickly your team can respond to clarification requests. If there are known product changes, network additions, or data discrepancies, disclose them during kickoff. A concise explanation backed by current public information is more useful than leaving a reviewer to reconcile conflicting project pages.

When should a project request both?

Request both when you can clearly identify the DeFi protocol whose TVL information is relevant and the dApp you want presented, and when each has accurate public materials. If only one side is ready, begin with the request that matches the available product and evidence; the second can be planned when its information is complete.

For a focused kickoff, send MarketingExtra the project website, documentation, application link, relevant network details, and a short note on whether you want DefiLlama, DappRadar, or both. Include any existing platform pages and explain what you want reviewed or updated. Do not send credentials unless they are specifically needed and agreed through a secure process.

Send 3 things: your project docs, your contract addresses and the chains you use. With those, we assemble the pack and confirm the cost in writing before any request is sent.

How it works

1. Confirm the listing planIdentify the protocol, dApp, network details, and platforms in plan. Assign one project contact who can approve claims and answer technical questions.
2. Review project materialsWe check public links and supplied information for missing evidence or inconsistencies, then return a clear list of items to resolve.
3. Prepare the requestsWe organize platform-specific information using facts and supporting material approved by your team.
4. Approve and coordinate submissionYou review the final information before we coordinate the agreed requests and record what was sent.
5. Track follow-upWe share replies or visible status changes, note requested clarifications, and agree with you on the next action.