DefiLlama and DappRadar listing service

What does a DefiLlama and DappRadar listing cover?

The service prepares two distinct listing requests: a TVL listing for DefiLlama and a dApp listing for DappRadar. Each requires its own evidence and clear project details.

The work is useful when a project wants its DeFi protocol or application represented in these directories and has public information ready to review. It is also useful when the project has several products or chains and needs to decide what belongs in each request. We map each requested listing to a specific product, then check that names, URLs and descriptions agree across the materials. For a broader view of directory options, see Listings and verification. If the project needs other tracker profiles as well, listings on other crypto trackers can be scoped separately.

What should be ready before requesting a listing?

A listing request is easier to prepare when the project can point reviewers to stable, public information. Start with the product and evidence checklist below.

• Confirm the exact protocol or dApp name and the official project website.
• Gather direct links to the product, relevant public dashboards and supporting documentation.
• Write a concise description that explains what the product does without mixing it with token promotion.
• Check that social and contact links are current and controlled by the project team.
• Note any chain, product-name or URL changes that could make older materials inconsistent.

For a DefiLlama TVL request, organize the sources that show the protocol’s relevant data and how a reviewer can inspect them. For DappRadar, prepare direct access to the application and enough context to identify its function. We flag missing or conflicting details in the kickoff checklist rather than leaving the team to discover them mid-submission. If supply data also needs review for other profiles, coordinate that work through circulating supply verification.

What materials and support are included?

The deliverable is a submission-ready package for the agreed platforms, plus a record of what was sent and what remains open. Scope is confirmed against your project assets before work begins.

We do not use one generic description for both platforms. The DefiLlama materials are framed around the protocol and its TVL-related evidence; the DappRadar materials identify the application and its user-facing purpose. You provide accurate project facts and access to the public resources. We organize those facts, identify gaps, prepare the copy and support the agreed submission work. If an existing profile needs a technical or presentation update instead of a new listing, we can assess whether DEX listing and liquidity setup is relevant; it is a separate scope, not an automatic part of this package.

How do we prepare and track each platform request?

The workflow is a short sequence: establish the listing target, check its evidence, prepare separate submissions, then log the follow-up. The project has one point of contact at AEOTech for asset questions and status updates.

1. Kickoff checklist: confirm the project name, product, target platform and official links.
2. Evidence review: compare the supplied descriptions and public sources; send one consolidated list of gaps.
3. Package preparation: draft platform-specific copy and organize the relevant URLs and supporting information.
4. Submission support: submit or support the submission using the agreed account and process.
5. Status report: record submission details, platform responses and any requested changes.

The expected schedule is set after the asset review. A project with accessible data and consistent naming can move directly into package preparation; missing links or unclear product boundaries need to be resolved first. The report separates completed work from items waiting on the project or platform, so the team can see the next action without guessing. For adjacent directory work, compare the scope with our CoinMarketCap listing service or CoinGecko listing service.

Which listing decisions remain with DefiLlama and DappRadar?

The project controls the accuracy and accessibility of its submission; each platform controls its own review and published presentation.

DefiLlama may decline or change a TVL presentation; DappRadar controls whether and how a submitted dApp appears, and displayed data depends on what its public interface can read. We can promise the agreed research, submission package and follow-up, not acceptance, a particular display position or the timing of a platform decision.

Before sending materials, use this check:

• Open every project URL in a logged-out browser and confirm it reaches the intended page.
• Make sure the name and product description match across the website, application and submitted copy.
• Verify that any data source or dashboard cited is publicly accessible and clearly connected to the protocol.
• Keep a copy of the submitted text and links so future updates can be compared against the original request.

This preparation reduces avoidable back-and-forth and gives your team a clear record if a platform asks for clarification. Keep a project contact available to confirm factual details promptly.

When should you combine these listings with other work?

Combine the requests when the same project facts, product links and review contact apply to both platforms. Keep them separate when the TVL target and the dApp target refer to different products or need different evidence.

A shared asset inventory helps prevent inconsistent project names and stale links across listings. It does not mean that the same copy should be pasted into every directory: adapt the description to the listing’s purpose and the evidence available. If you are planning a broader directory program, start with Listings and verification and prioritize the profiles that matter to your users. Send AEOTech the project website, target product, relevant public data links and the preferred contact person. We will return a readiness checklist and confirm the exact listing scope before preparing the package.

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. Confirm the listing targetsTell us which protocol or dApp should appear on each platform. We confirm whether the two requests refer to the same product.
2. Share public project materialsProvide the website, application links, relevant data sources and current descriptions. We flag missing or inconsistent items in one checklist.
3. Prepare platform-specific packagesWe organize the TVL evidence and dApp profile information separately, then share the proposed materials for factual review.
4. Support submission and follow-upWe handle the agreed submission work and log platform communications, open questions and next actions.
5. Review the status reportYou receive a record of what was prepared and submitted, together with any outstanding items for the project team.