Your DeFiLlama TVL and Your Actual Liquidity Score Are Different Numbers. Here's Why Both Are Correct.
DeFiLlama TVL and protocol dashboard numbers measure different things. Neither answers the question founders actually need: can your token absorb sell pressure? Here's what the gap means and how to check your actual liquidity health.
Last week, @0xmortan posted a thread that got sustained replies on CT.
The finding: a $549M gap between Aave's TVL on Megaeth as reported by DeFiLlama ($120M) and the number shown on Aave's own dashboard ($669M). The thread surfaced an old confusion in a sharp, specific way. Comments split between "DeFiLlama is wrong" and "no, the protocol is wrong."
Both camps missed the point. Neither number is wrong. They measure different things by design.
And more importantly: neither one answers the question founders actually need answered.
Why DeFiLlama's Number Is Different From Your Protocol Dashboard
DeFiLlama calculates TVL as deposits minus borrows, plus equity held in protocol contracts. This is a technical, standardized definition. It reflects net capital deployed in a protocol, not gross inflows.
The design choice is intentional. DeFiLlama's job is cross-protocol comparison at scale. A consistent formula across thousands of protocols makes the rankings meaningful. If every protocol reported on its own terms, the TVL leaderboard would be noise.
Protocol dashboards take a different approach. Most report total deposits or gross financial balances. That's the number that makes sense for a board presentation, a fundraising update, or a tokenholder report. It reflects how much capital has flowed in, not how much sits net of borrowing activity.
Neither approach is a bug.
| Source | What it measures | Best used for |
|---|---|---|
| DeFiLlama TVL | Net deposits minus borrows plus protocol equity | Cross-protocol comparison, market-wide TVL aggregation |
| Protocol dashboard | Gross deposits or financial balances | Internal reporting, investor updates, tokenholder communication |
| THS Liquidity score | Pool depth vs. FDV, slippage, LP lock status, whale LP | Assessing whether liquidity holds under sell pressure |
The Aave/Megaeth gap wasn't a data error. It was two valid methodologies producing two different outputs for two different audiences.
The Question Neither Number Answers
Here's the problem. Both numbers are real, both are useful — but neither answers the question a founder or investor actually needs answered.
The question is: "If 10% of my token's circulating supply hits the market tomorrow, what happens to my price?"
DeFiLlama's net TVL figure doesn't answer this. The protocol's gross deposit number doesn't answer this. Neither tool was designed to.
The answer comes from pool-level data. How deep is the liquidity at different price points? What happens to slippage as order size increases from 0.5% to 2% of circulating supply? How much of the LP is held by a single address that can withdraw tomorrow with no penalty?
TVL tells you the size of the pool. Liquidity health tells you whether the pool holds under pressure. Those are different questions.
How THS Scores Liquidity Health
Token Health Scan's Liquidity dimension is built to answer the sell-pressure question directly. It pulls pool-level data from Moralis and GeckoTerminal, then scores across four sub-signals.
Pool depth vs. FDV. Is there enough liquidity in the pools to support realistic trading volumes relative to the token's fully diluted valuation? A token with $50M FDV and $200K in pool depth faces brutal slippage on any meaningful sell event, even one that looks small as a percentage of FDV.
LP lock status. Is the liquidity locked, or can it be withdrawn? Unlocked LP concentrated in a few addresses is a fundamentally different risk profile than distributed, time-locked LP. The depth number looks the same on a chart. The risk profile is completely different.
Slippage under sell pressure. I model slippage at standard sell sizes — 0.5% to 2% of circulating supply — from pool depth data. This is the number that tells you what actually happens during a bad day, not just a calm-market average.
Whale LP concentration. The same concentration problem that affects token holder distribution shows up in LP. If one address controls 60% of a pool, that address is a single point of failure for your protocol's market stability.
| Sub-signal | What it flags | Score impact |
|---|---|---|
| Pool depth vs. FDV | Insufficient liquidity relative to market cap | Negative |
| LP lock status | Unlocked LP from few addresses | Negative |
| Slippage (modeled) | High slippage on 0.5–2% circulating supply sell | Negative |
| Whale LP % | Single address controls >50% of LP | Critical flag |
The Liquidity score outputs 0–100. Below 40, at least one critical flag is active. Above 70, the pool structure passes standard depth and concentration checks.
The Aave Case. What THS Would Look At.
In the @0xmortan example, DeFiLlama showed $120M and Aave's dashboard showed $669M for Megaeth. Both are correct calculations under their respective methodologies.
A THS Liquidity scan wouldn't resolve the $549M gap. That's not its job. What it would look at is different.
I'd run the pool depth check: how much liquidity actually sits at each price point in Aave's active pools on Megaeth. I'd check LP lock status for the top LP addresses. I'd model slippage at realistic trade sizes for the protocol's token. I'd flag any address controlling a large share of LP with no time-lock.
The output isn't a TVL number. It's a score from 0 to 100 that tells you whether the liquidity in those pools will hold when it needs to.
DeFiLlama's $120M net TVL and a strong Liquidity score can coexist. A high gross deposit number and a weak Liquidity score can coexist. They measure different things.
Why This Gap Matters for Protocol Founders
I've seen this confusion surface in three specific situations where the TVL vs. liquidity health distinction causes real problems.
Campaign launches. You run a growth campaign. Token volume spikes. Your pool depth wasn't sized for that volume. Slippage craters on the buy side. New users get punished on entry. The campaign that was supposed to drive adoption damages trust instead. A pre-campaign Liquidity check would catch thin pool depth before launch, not after.
Exchange listing conversations. You tell a prospective CEX or market maker that your DeFiLlama TVL is $X. They pull on-chain pool depth and see a different number. The deal stalls, or the listing happens on worse terms. The TVL figure wasn't fabricated — it just measured something different from what they needed to see.
Investor updates. You report TVL growth to investors using your protocol dashboard numbers. They're tracking the DeFiLlama figure. The numbers tell different stories. The credibility gap that opens isn't about the data — it's about not flagging the methodology difference upfront.
In each case, the fix is simple: know which metric you're quoting and what it doesn't measure.
Check Your Token's Liquidity Score Before Your Next Campaign
Your DeFiLlama TVL tells one story. Your Liquidity score tells another.
Run a free scan at tokenhealthscan.com. The Liquidity dimension scores pool depth vs. FDV, LP lock status, modeled slippage, and whale LP concentration in 60 seconds. Free. No login required.
If your pool structure has a single-address LP concentration risk or thin depth relative to your FDV, the score will surface it before your campaign does.
Frequently Asked Questions
Why is my DeFiLlama TVL different from my protocol's own dashboard?
DeFiLlama calculates TVL as total deposits minus borrows plus equity held in protocol contracts. Most protocol dashboards report gross deposits or total financial balances, which don't subtract borrowing activity. Both calculations are correct. They answer different questions. The gap between them is a methodology difference, not a data error.
What is a token liquidity health score?
A token liquidity health score measures how well a token's on-chain liquidity will hold under realistic sell pressure. It's distinct from TVL. Where TVL measures the total value in a pool, a liquidity health score examines pool depth relative to FDV, LP lock status, modeled slippage at standard trade sizes, and whale LP concentration. Token Health Scan outputs a 0–100 Liquidity score that reflects all four signals.
How does Token Health Scan measure liquidity?
THS pulls pool-level data from Moralis and GeckoTerminal and scores four sub-signals: pool depth vs. FDV, LP lock status for the largest LP addresses, slippage modeled at 0.5–2% of circulating supply, and single-address LP concentration. Each sub-signal contributes to a 0–100 Liquidity score. A score below 40 means at least one critical flag is active.
Why does LP concentration matter for token health?
A single address controlling a large share of a liquidity pool is a single point of failure. If that address withdraws — for any reason, at any time — the pool depth drops sharply and slippage on all subsequent trades spikes. LP concentration risk doesn't show up in TVL figures. It shows up in on-chain pool composition data, which is what THS's Liquidity dimension reads directly.