A September 15 BIS working paper finds that measures of stablecoin, crypto and DeFi activity can vary substantially with data treatment. A headline number for transactions or total value locked therefore needs a definition and a reproducible source.

What happened and what we know

Total value locked can count deposited assets while borrowed or bridged versions circulate elsewhere. Data providers may treat internal transfers, bots and duplicate addresses differently. For individual borrowers, aggregate protocol size is not a substitute for a position-level health factor and collateral buffer.

Why it matters for the market

In lending, borrowed funds and collateral can be counted in several places. On Aave, a borrower’s health factor below one makes the position eligible for liquidation. Neither a high aggregate deposit number nor a token rally removes that individual risk.

One announcement is rarely enough to explain an asset’s full price move. The timing of data, the scope of the source and the difference between observed activity and a projected effect all matter. In this article, the scenarios below describe conditions to test, not promised outcomes.

Deeper context and limits

The BIS result is a warning about definitions, not a claim that all on-chain data are useless. A dashboard that counts transfers as payments may overstate economic exchange if it includes exchange reshuffling or bridge messages. Another provider may exclude these and report a lower figure. Both can be internally consistent under different methods, so the methodology belongs beside the number.

At user level, protocols add risks that a broad market total cannot capture. Lending depends on collateral valuation and liquidators; swaps depend on pool depth and slippage; bridges introduce additional contracts and operators. A sophisticated user should test a small transaction, verify the correct deployment, and understand how to exit if a market becomes stressed. A high TVL is not insurance.

Bull, bear and neutral cases

Confirmation and invalidation

Check methodology and contract addresses, then monitor utilization, liquidation parameters and realized losses. Invalidate a safety claim when it relies only on TVL.

Before using a protocol, check contract address, audit scope, oracle assumptions, liquidation threshold and bridge exposure. Compare like-for-like metrics across dates rather than relying on one dashboard snapshot.

Reader checklist

• Verify the correct protocol deployment and chain.
• Model a collateral price fall and interest accrual.
• Inspect oracle and bridge dependencies.

Published 26 September 2026. This is a dated report, not a live price feed or personal investment advice. Source documents may be revised after publication.