DefiLlama and DappRadar listings, made easier to prepare

Two platform profiles, one clear starting point

Picture a developer who writes docs but not posts. The evening before an AMA, they want listing information ready without a scramble for links. We would help sort the facts first, then prepare the platform materials separately.

A DefiLlama and DappRadar listing serves two different purposes. One concerns protocol TVL information, and the other presents a dApp profile. We can plan both together while keeping each request and its supporting material distinct.

This is a useful fit when your product is live and your public information is ready for review. It can also help after a product, chain, or official link changes. If you're comparing directory options, our listings and verification overview can help map the work. We can also discuss other tracker profiles through listings on crypto trackers.

Before we begin, we ask for your official project URL and a short description. We also need relevant chain and contract details. Please include the sources your team wants considered.

What should your team gather for each platform?

A strong start is a small set of current facts that your team can check and support. We sort the intake into 3 groups: project identity, product details, and evidence. That makes it easier to spot missing information before we prepare the requests.

For the DefiLlama TVL request

Share the protocol description, relevant chain and contract information, and sources that explain the TVL information you want presented. Tell us what each source represents. If a number is preliminary or still being checked, mark it clearly. That way, nobody presents it as settled. Token supply work is separate. When needed, we can discuss circulating supply verification.

For the DappRadar profile

Send the official product or app URL, the preferred project name, a plain description, and relevant chain details. Add official links that help someone understand or use the dApp. For example, say the app URL is changing shortly before the request. We would ask which link is current. We would wait for your confirmation rather than prepare a profile around a stale address.

Choose one contact who can confirm facts and approve the final text. Your team remains the source for project claims. We organize and check the materials you supply.

How the listing work moves forward

The work moves from a clear request to checked materials, then to agreed follow-up. We keep the two platform tasks distinct, even when they share the same project contact.

1. Agree what you need. Tell us whether you want a DefiLlama TVL request, a DappRadar profile, or both. We confirm what is included and identify the person who will approve facts.
2. Collect the sources. We gather your official URLs, descriptions, chain details, and supporting material. We note questions instead of filling gaps ourselves.
3. Review and approve. We make 2 review passes. First, we check consistency between claims and sources. Then your team reviews the facts. You keep control of project accounts and final copy.
4. Coordinate and report. We follow the agreed submission or update route. We record what was sent, any reply, and the next action.

If your plans also include a DEX profile, that is a separate task from tracker listings. See DEX listing and liquidity setup. A CoinMarketCap listing is another distinct platform request, not an extension of either profile. We agree any additional work with you before expanding the engagement.

The useful pieces your team can keep

You receive the agreed preparation and coordination for the selected platform tasks. The exact items depend on whether you're preparing a new profile, handling an update, or asking us to work on both platforms.

We keep the status note to 4 points: materials received, checks completed, actions taken, and the next step. That gives your team a simple handoff record instead of scattered messages. It also makes clear which copy you approved. Any questions still needing a project-side answer remain visible.

Before work starts, we agree whether the request covers one platform or both. If the project needs a change to its name, contract, or brand details, we can consider that separately. See contract migration and rebranding updates.

After submission, each platform has its own say

A prepared request gives each platform clear project information to review. DefiLlama and DappRadar decide whether and how submitted details are accepted, displayed, or maintained. Their review, display choices, and timing are not under our control. We commit to the preparation, coordination, and reporting we agree with you.

To keep the request easy to check, share sources that match the claims you want included. Tell us if a product page is changing, a figure is preliminary, or a contract detail still needs confirmation. We can help present confirmed information clearly. We also keep open questions visible for your team.

The next step is simple. Send the official project URL, your preferred short description, and relevant chain details. Also send the sources behind the TVL or dApp information. We’ll review what you have and confirm whether one or both platforms belong in the plan. Then we’ll come back with the practical work to agree.

How it works

1. Choose the platform tasksTell us whether you need a DefiLlama TVL request, a DappRadar profile, or both. We agree the work and name the person who can approve project facts.
2. Share official sourcesSend project URLs, descriptions, relevant chain and contract details, and sources for the information you want considered.
3. Check the prepared materialsWe compare details with the sources, raise factual questions, and give your team the materials to review before submission.
4. Coordinate and keep a recordWe follow the agreed submission or update route, then write down actions taken, replies received, and remaining questions.