SERIOUS ABOUT BUILDING IN WEB3?
If you're working on something real — let's talk.
Published On Dec 08, 2025
Updated On Dec 08, 2025
Whether you’re building a DEX, a yield aggregator, a liquid staking platform, or any product contributing to DeFi liquidity, getting listed on DeFiLlama is how your data becomes visible, verifiable, and comparable across ecosystems.
However, for many teams, the listing process can feel complex at first. You need to meet specific technical requirements, follow a defined submission workflow, and ensure your data structure is compatible with how DeFiLlama reads and aggregates on-chain metrics.
Missing even one detail can delay approval or cause your data to display incorrectly.
In this blog, we break down everything you need to know about how DeFiLlama listings work, the steps to get your project listed, and how to maintain accuracy and visibility after approval.
Let’s get started.
A DeFiLlama listing helps your project stand out in a crowded ecosystem by making your liquidity, usage, and performance publicly measurable.
A verified listing amplifies visibility, automates analytics, and builds trust across ecosystems. Here is what is explained below:
DeFiLlama organizes protocols into sector and chain dashboards, from Top DEXs on Arbitrum to Lending Protocols on Base.
Being listed means your project surfaces in leaderboards, historical charts, and ecosystem analytics viewed by millions of users monthly.
DeFiLlama is the upstream data source for dashboards, explorers, and yield platforms.
A clean adapter ensures your data flows automatically into these tools, multiplying reach with zero additional work.
Each listed protocol submits an adapter, a small script that computes TVL and balances directly from your contracts.
Because these scripts are open-source, your data is verifiable, not self-reported.
Once merged, DeFiLlama refreshes your TVL data automatically, pulling directly from your contracts.
No extra dashboards, no manual updates, just reliable, real-time transparency.
A DeFiLlama listing isn’t about optics; it’s about infrastructure. It ensures your data is visible, standardized, and trusted so that users discover you and how DAOs measure your growth.
Visibility brings credibility, but only when data is accurate. The best way to build that trust is by setting up your listing correctly from the start.
Here’s how to do it step by step.
Listing your protocol on DeFiLlama is a technical but straightforward process when followed step-by-step.
Each submission helps standardize your protocol on-chain data so that it becomes visible, verifiable, and comparable across the ecosystem.
The following workflow is adapted from the official DeFiLlama listing guide:
Start by visiting the DefiLlama Adapters GitHub repo and clicking the “Fork” button in the top-right corner.
This creates your own copy of the repository, allowing you to add your protocol’s code without affecting the main branch.
Ensure your team’s GitHub account is linked to your protocol’s official organization to make verification smoother later.
Inside your forked repository, navigate to the /projects directory and create a new folder named after your protocol, all lowercase and hyphenated
For example, /projects/my-protocol.
This folder will hold your adapter file, which tells DeFiLlama how to calculate your protocol’s TVL, staking balances, and other key metrics.
Next, you’ll add your adapter script to the core logic DeFiLlama uses to pull and compute your data.
There are two main types of adapters:
Each adapter must include:
Before submitting, test your adapter to confirm it returns accurate values.
Run the following commands in your local environment:
Compare the output with your protocol’s internal analytics or on-chain values.
Accurate results at this stage prevent rejections or data drift later.
Once your adapter is tested, submit a Pull Request (PR) from your fork to the main DeFiLlama Adapters repository.
In your PR description, include:
Check the box that says “Allow edits by maintainers.” This enables the DeFiLlama team to make small fixes during review.
Once approved, your adapter is merged, and your project typically appears on the DeFiLlama dashboard within 24 hours.
If your protocol already exists on DeFiLlama and you’re adding a new version or product (for example, v2 vaults or staking modules), simply create a new adapter in the same folder and submit another PR.
The DeFiLlama maintainers will handle linking these under a parent listing, ensuring your total TVL and historical charts remain unified.
Once your project is listed, the work doesn’t end there. Maintaining visibility means keeping your adapter and data pipeline healthy.
Once your adapter is live, your data becomes part of DeFi’s public analytics layer. Keep it credible by building ongoing checks and discipline.
These updates should be monitored regularly, as doing so helps you catch issues early and detect TVL discrepancies if your protocol gets an upgrade.
That’s how accuracy moves from a checklist to a competitive advantage, the foundation of lasting trust in DeFi.
A verified DeFiLlama listing transforms your protocol’s activity into a transparent signal of integrity.
Getting listed is the start of visibility; maintaining accuracy is how you keep it.
Every adapter you publish is part of your protocol’s reputation, and every accurate metric reinforces your legitimacy in the open financial stack.
From adapter integration to analytics pipelines, Lampros Tech helps DeFi teams get listings right and keep them right.
Explore our Data Analytics Services and make your protocol listed and ensure it stays visible, verifiable, and trusted across ecosystems.
To list your project, you need to fork the official DeFiLlama Adapters repository, create a project folder, write your adapter script (SDK or Fetch), test it locally, and submit a pull request (PR) to the main repo for review and approval.
You’ll need accurate contract addresses, token mappings (to Coingecko or chain IDs), and a verified adapter that correctly calculates Total Value Locked (TVL).
After your pull request is merged, your project typically appears on the DeFiLlama dashboard within 24 hours.
Update your adapter whenever you deploy new vaults or contract versions, and regularly monitor SDK updates or schema changes. This ensures your public TVL data remains consistent.
TVL discrepancies often occur when new pools are not added, proxy logic changes are missed, or version migrations duplicate data. Regular monitoring helps detect and fix these early.
