How to read DeFiLlama for TON: an analyst's guide 2026

DeFiLlama has become the de-facto shared vocabulary for DeFi. When someone says “TVL of Aave”, “TVL of Lido”, or “TVL of Tonstakers”, they almost always mean the number DeFiLlama displays, not the figure from the protocol’s own dashboard. That is convenient for cross-chain comparisons but creates the illusion that the figure is precise. On TON the illusion is especially risky, because DeFiLlama’s methodology was designed around Ethereum-style contracts, and TON lives in a different paradigm — jettons, wrappers, asynchronous messages, no shared ERC-20 interface. This article is a practical guide to reading the TON pages of DeFiLlama without illusions.

TL;DR

• DeFiLlama gives the best cross-chain TVL comparability out there, but its “everything in dollars from one source” methodology drops important TON details: jetton wrappers, native vs bridged USDT, liquid-staking double-counting.
• Core dashboards: defillama.com/chain/Ton, the same page filtered by category (DEX, Liquid Staking, Lending), /stablecoins/Ton, and each protocol’s page.
• TVL is not liquidity. A high TVL with low volume on a DEX often signals a decorative pool. On staking that pattern is normal.
• DeFiLlama lags weeks behind new launches and does not always net stablecoin flows across bridges cleanly.
• Cross-checking is mandatory: TonStat for on-chain activity, RootData for venture rounds, the protocol’s own dashboard to verify the headline number.

What the TON section on DeFiLlama actually shows

The entry point is defillama.com/chain/Ton. It is an aggregate TVL chart for the whole chain with breakdowns by protocol, category, and history. Under the hood DeFiLlama maintains a list of adapters — fetch.js-style files in their open-source repo — that read on-chain balances and convert them to dollars via DeFiLlama’s own price feeds. Every adapter is hand-written by a maintainer and reviewed by the DeFiLlama team.

On TON that pipeline works differently than on Ethereum. On EVM chains you call balanceOf(contract) on an ERC-20 — a standardised interface. On TON each jetton has its own root contract, and the balance for a given owner lives in a separate jetton-wallet contract whose address is computed deterministically from the (jetton_root, owner) pair. The DeFiLlama adapter has to know specific addresses and resolve jetton-wallets correctly. A single addressing mistake either zeroes out the TVL or doubles it.

The second wrinkle: TON protocols often wrap native TON into jTON (jetton-wrapped TON) for compatibility with their internal DEX or DeFi tooling. From the user side it is “still TON”, but on-chain it is a distinct jetton with its own master capitalisation. DeFiLlama deduplicates known wrappers, yet new forks and smaller protocols slip through the dedup net regularly.

The dashboards worth bookmarking

A working minimum:

• /chain/Ton — chain-level TVL, history, breakdown by protocol. First stop for “what is happening in TON DeFi right now”.
• /chain/Ton filtered by Liquid Staking — three or four large players (Tonstakers, BEMO, Hipo) hold the bulk of TON liquid-staking TVL. Useful when you want to understand where TON that nobody trades goes.
• /chain/Ton filtered by Dexes — the DEX landscape. Turn on the Volume (24h, 7d) columns immediately, they expose parked pools.
• /stablecoins/Ton — the dollar liquidity structure. How much USDT-jetton vs bridged USDT (via TAC and other bridges), how much USDC, what local stablecoins exist.
• /raises with chain=TON filter — the venture lens. Patchy on TON, but occasionally surfaces deals that did not hit the news cycle.
• Per-protocol page — for example /protocol/tonstakers. Detailed graphs, forks, dashboard links and audit references live here. The Forks tab is underused and often the fastest way to map code lineage.

A separate page defillama.com/dexs/Ton shows the Volume vs TVL ratio and dominance among STON.fi, DeDust, and smaller venues. It reveals how concentrated TON spot trading is — historically close to a duopoly.

What counts in TON TVL, and why it is harder than Ethereum

Canonical Ethereum TVL is straightforward: the dollar sum of every token held by a protocol’s contracts. Aave v3 USDC holds 800M USDC, USDC price = $1, TVL = $800M. Done.

On TON things branch. Take staking via Tonstakers. A user sends TON to the pool contract and gets stTON in return. The pool routes TON to validators through ElectionContract. DeFiLlama needs to:

1. Find every TON locked with validators via this pool.
2. Not double-count stTON separately — it is a claim on the pool, not an independent asset.
3. When stTON shows up as liquidity on STON.fi, the STON.fi pool should see stTON as an asset but not multiply it by the TON price — that would double-count.

Deduplication requires each protocol’s adapter to classify incoming assets correctly (tokensInUsd vs tvl). DeFiLlama uses an isLSD flag (liquid staking derivative) so derivatives like stTON do not roll back into the chain-level TVL. The flag is set manually. If a new liquid-staking team does not file the proper adapter, their derivative will be treated as a regular asset.

A second example: USDT on TON exists in two forms. USDT-jetton — the native Tether jetton with gasless transfers — and bridged USDT, for example via TAC from Ethereum. They are two different jetton roots with separate capitalisations. DeFiLlama honestly shows both on the stablecoin page, but they can be conflated inside DEX pools tagged generically as “TON/USDT” without specifying which USDT.

A third: wrapped TON (wTON). Some DEX pools work with wTON jetton instead of native TON for their internal plumbing. If DeFiLlama’s adapter does not know that wTON equals TON, it either omits it or prices it wrong.

Workflow: comparing three liquid-staking protocols

Suppose the task is to compare BEMO, Tonstakers and Hipo on APY-adjusted TVL — to figure out whether the TVL was “bought” via an unsustainable APY and how utilised each protocol actually is.

The steps:

1. Open defillama.com/chain/Ton and filter by Liquid Staking. Pull the current protocol list and their TVLs. As of writing all three sit in the top of TON DeFi; the exact numbers shift hourly.

2. Open each protocol’s page (/protocol/tonstakers, /protocol/bemo, /protocol/hipo). Record current TVL, 30d trajectory, any drawdowns, and whether there is a link to the native dashboard.

3. Reconcile DeFiLlama TVL with the native dashboard. A 5-10% gap is normal. A 30% gap means one source is wrong, usually because DeFiLlama is pricing the derivative jetton with a stale feed.

4. Find APY on the native dashboards. DeFiLlama does not surface staking APY uniformly for TON protocols — it is outside their base model. Go to the protocol sites.

5. Sanity-check the APY. Base validator yield on TON tracks the network’s annualised emission and staking ratio (current values on TonStat). If a protocol promises noticeably more, identify the delta source: reinvested commission, additional jetton incentives, or subsidised APY paid to attract TVL.

6. Volume divided by supply for the derivative jetton. On each protocol page, jump to Pools, or look up stTON, tsTON, bemoTON on STON.fi and DeDust DEX pages. Compute 24h volume divided by outstanding supply. If for a large protocol the ratio is under 0.5%, the derivative’s secondary liquidity is worse than its TVL suggests.

7. Forks and code lineage. The Forks tab on each DeFiLlama protocol page tells you whether the protocol forked someone else’s code. That points to the original audit and a longer security history. Self-written staking on TON is rarer than the marketing implies.

After running this loop you do not just have “TVL = X”, you have a profile: real TVL plus or minus DeFiLlama’s error, APY realism, derivative liquidity, code provenance. That is a very different basis for deciding where to park TON. For a deeper dive into the staking layer see the TON validator data guide.

Where DeFiLlama lies or lags

Three recurring failure modes.

New protocols. A protocol only lands on DeFiLlama after a pull request to their open-source repo, with a TypeScript adapter that reads balances over TON RPC. For a TON team the lag from launch to listing is routinely 2-6 weeks. During that window the real TVL may be material while DeFiLlama still shows zero. Cross-checking via the team’s own dashboard or TonStat is mandatory for anything launched in the last quarter.

Forks without their own adapter. When a team forks STON.fi or DeDust and does not file a separate listing, their TVL either gets ignored entirely or occasionally rolls into the parent via the shared adapter — depending on how the parent’s adapter was written.

Stablecoin netting. The /stablecoins/Ton page shows the supply of each stablecoin. Supply does not net cross-bridge flow perfectly: when USDT exits TON back to Ethereum via TAC, the burn on the TON jetton side should reduce supply. In practice there is a several-hour lag between the burn and the DeFiLlama refresh, during which the number is inflated. For accurate dollar-flow accounting, the bridge dashboards are the source of truth.

A fourth, subtler case is derivatives on derivatives. When stTON gets posted as collateral in a lending protocol that issues its own derivative (something like lstTON), the dedup chain becomes two layers deep. DeFiLlama handles this for the very top protocols, but the long tail is unreliable.

Cross-check sources

DeFiLlama is a great first source and a poor only source. For confirmation and expansion:

• TonStat.com — TON-native metrics: active wallets, jetton flows, holders per jetton, NFT activity. The things DeFiLlama does not model at all. See the TON on-chain metrics guide for how to read them properly.
• Re:Doubt — security-flavoured analytics, suspicious transaction monitoring, anti-phishing address labels. Particularly useful for vetting a contract address before interacting.
• RootData — venture rounds, team composition, investor lists. Covers TON significantly more completely than DeFiLlama Raises.
• CoinGecko / CMC — prices, market cap, exchange liquidity. DeFiLlama uses its own price feeds, which sometimes drift 1-3% from CoinGecko. Noise for most uses; meaningful if you are building serious strategies.
• The protocol’s own dashboard — the court of last resort for a specific TVL number. Tonstakers, BEMO, Hipo, STON.fi, DeDust all run real-time dashboards refreshed on every block.

For tracking large flows and wallets that fly under the macro radar, keep the TON whale-watching guide and the token vesting and unlock reading guide close at hand. DeFiLlama does not account for vesting tokens, yet those are the ones that map future sell pressure.

Conclusion

DeFiLlama for TON is a convenient cross-chain dictionary and a poor single source of truth. The numbers on its pages should be read as the best approximation available within one coordinate system, not as ground truth. The trick is understanding what gets counted in TVL, where the dedup lines run, which protocols are new and therefore likely undercounted, which stablecoins and wrappers risk being double-counted. With that filter applied, DeFiLlama becomes a powerful tool for comparing TON against other chains and for fast screening to decide where to look next. Without it, it is just a pretty chart that is easy to mistake for reality.