DefiLlama Listing and DappRadar Listing for DeFi Projects

What does a DefiLlama listing and DappRadar listing give you?

A DefiLlama listing helps present a DeFi protocol in the context of its TVL, while DappRadar lists a decentralized application profile. These are two separate directories with different purposes: they should not be seen as a single application or identical verification. We help prepare a project for both listings and align the information.

The service suits teams with an already working product and public materials needed for verification. Before starting, it is useful to determine what exactly you want to list: a protocol with asset lock data, an application with a user scenario, or both. If the project is only preparing for launch, first gather working links, network and contract details, and a clear product description.

Before we begin, we clarify:

• which networks and contracts belong to the project;
• where users can open the application and test its functions;
• which public sources confirm the provided information;
• whether the name, description, and links match on the website and profiles.

If you need to plan broader listings, see the listings and verification section. We separately agree on which directory is suitable for your product, rather than submitting the same description without adaptation.

How do the data for DefiLlama and DappRadar differ?

For DefiLlama, the key preparatory question is how to correctly describe the protocol's TVL and link it to verifiable on-chain data. For DappRadar, it is important to present the application itself: its purpose, available features, and how to interact with the product. Therefore, one universal questionnaire does not replace two separate material sets.

For a TVL application, gather contract addresses, supported network details, and a description of which assets are counted. Note architectural features if they could cause data misinterpretation. Verify that the documentation aligns with the actual protocol operation. Do not include metrics that cannot be explained or confirmed by public sources.

For a dApp card, prepare a brief description of the user task, a link to the working product, the official website, and current project channels. Ensure the application opens, main pages are accessible, and the name and visuals match official resources. For related issues, such as contract and liquidity preparation, DEX listing and liquidity setup may be helpful.

Both applications benefit from a clear match between the claimed product and what can be independently verified. If there are discrepancies in name, network, or links, it is better to resolve them before submission rather than explain after a clarification request.

What is included in listing preparation?

As part of the service, you receive prepared materials and a clear action plan for DefiLlama and DappRadar. The scope is agreed based on the project's state: if core data is already collected, work focuses on verification and formatting; if there are gaps, we first identify what the team needs to provide or fix.

The work may include:

• initial assessment of project readiness and selected directories;
• verification of names, descriptions, links, networks, and contract addresses;
• separate preparation of TVL information and dApp description;
• a list of missing confirmations and comments on materials;
• formatting and submitting applications according to an agreed scenario;
• communication support and help with responses to clarifications.

We do not replace the team on matters requiring internal product knowledge or technical solutions. For example, only developers can confirm a contract's purpose and explain metric calculation specifics. Our task is to request this information in the right form, verify its consistency, and present it so the reviewing party can understand it more easily.

If you also need to organize token information in other directories, that is a separate area: see CoinGecko listing or CoinMarketCap listing. These listings do not replace a DefiLlama or DappRadar submission.

How does the DefiLlama and DappRadar submission process work?

Work begins with project analysis, not by sending the same form to different directories. First, we determine the appropriate listing object and gather source links, then identify which information can be confirmed and where explanations are needed. After material approval, we submit applications and help the team handle possible requests.

Typically, the process looks like this:

• You provide the website, description, application links, network and contract details.
• We check completeness and note contradictions or missing sources.
• The team clarifies technical details and confirms final wording.
• We adapt materials for each directory and support the submission.
• After the platform responds, we review requests and agree on next steps.

The preparation timeline depends on how quickly the team answers questions and how complete the initial data is. The platform sets the review time, so it cannot be considered part of our controlled schedule. To avoid delays on your side, appoint a contact person who knows the product structure and can confirm contract details.

We communicate via an agreed channel and provide status updates per stage: which materials are ready, what awaits the team's response, and which actions have been completed. Before starting, we define the work scope and completion criteria for our part.

What depends on platform review?

We control the quality of preparation and the execution of agreed actions, but we do not make decisions for DefiLlama or DappRadar. Each platform independently decides whether the project meets its rules and data, whether sufficient information is provided for listing, and what changes to make to the directory. Review, inclusion, TVL display, ranking, or subsequent card updates cannot be promised by the agency.

For DefiLlama, correct interpretation of TVL data and the ability to link the description to available sources are particularly important. For DappRadar, the application's suitability and the provided information for its directory are checked. Even a careful application may require additional explanations or edits. If the platform does not accept the materials, we analyze the reason and suggest which project or documentation changes the team should consider.

Before submission, conduct an internal check:

• the application is accessible via the official link and its purpose is clear;
• contracts and networks are listed without omissions or ambiguities;
• the description does not contradict the product's actual functions;
• claimed information can be confirmed by documentation or on-chain data;
• the team contact is ready to respond promptly to clarifications.

If contracts or the project name have changed, prepare an explanation of the connection between previous and current data in advance. Questions about token information verification may relate to a separate task — circulating supply verification.

What to combine with directory listing?

Listing is more useful when planned as part of a clear user journey: from project discovery to application access and verification of core information. Before submission, ensure the website, documentation, and community channels explain the same product proposition. If a visitor from the directory does not find clear instructions or current links, mere presence in the directory does not solve the conversion problem.

Choose related tasks based on the actual gap. If correct representation in token directories is missing, consider listings on other crypto trackers. If the project is heading for centralized trading, separately explore centralized exchange listing: it has a different process and set of requirements. For systematic material preparation, start with the general listings and verification section.

It is not necessary to launch all directions simultaneously. First, close critical inconsistencies in product information and technical sources. Then decide which directories truly match the project model and audience. This order helps the team answer specific questions and avoid spreading resources on listings that do not support the current goal.

Prices

Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.

How it works

1. Project assessmentYou provide key links and describe what you want to list. We determine whether the request is suitable for DefiLlama, DappRadar, or both directories.
2. Source data verificationWe cross-check networks, contracts, description, links, and product availability. We provide the team with a list of clarifications and missing materials.
3. Application preparationWe prepare separate information sets for the TVL protocol and dApp. You confirm technical details and final wording.
4. Submission and supportWe submit the agreed materials and help handle platform requests. Afterward, we explain the status and possible next steps.