Defipulse TVL reflected eligible deposits after asset filtering

Eligible addresses connected deposits to the total

Qualifying contract addresses formed the link between a protocol's deposited assets and its measured capital. Defipulse reviewed addresses when listing a protocol, identifying those holding assets involved in economic activity. The address set established where measurement began. Asset-level filters then determined which holdings contributed value. An asset could exist in a tracked contract and still fail an inclusion rule. That exclusion did not require a missing deposit or an incorrect blockchain balance.

A contract's holdings and a protocol's filtered total can describe different collections of assets. Comparing them requires accounting for the address set and eligibility rules.

Economic activity supplied the inclusion test

Deposits qualified through their economic use, which could include lending, liquidity provision, asset management or insurance. Merely placing tokens in a contract did not establish that use. Governance and liquidity-mining locks did not qualify simply because they restricted access to tokens. Holdings with no qualifying economic activity fell outside the calculation.

Issuer exclusions separated deposits from protocol-created assets

Automatic issuer exclusions removed assets flagged during review as minted by the protocol or a closely related protocol. This rule addressed an asset's origin separately from its location. Moving such an asset into a qualifying address did not erase its issuer classification. A quoted market price also did not establish that the asset met the inclusion rules. Keeping those valuations separate prevented a protocol's own issuance from substituting for qualifying deposited capital. The rule did not assign excluded assets a universal market value of zero; it assigned them no contribution within this measurement.

What did the liquidity-to-FDV cutoff measure?

The historical illiquidity rule excluded assets whose liquidity divided by fully diluted valuation fell below 0.0015. Fully diluted valuation, or FDV, relates a token's quoted price to its full potential supply. The ratio compared liquidity with that wider valuation. Expressing both inputs in the same currency made the comparison dimensionless; converting 0.0015 to a percentage gives 0.15%.

A low ratio indicated little liquidity relative to the valuation used in the denominator. The filter limited the contribution of those highly illiquid assets. Its threshold did not specify a trade size, an executable sale price or a withdrawal timetable. Passing an eligibility test could support inclusion in a capital statistic without establishing how a particular market transaction would execute.

Prices changed dollar totals without changing token quantities

TVL equals the sum of eligible token quantities multiplied by their respective dollar prices. The eligibility condition belongs in that relationship: valuing every visible holding first and treating the sum as TVL would bypass the filters.

Price movements and changes in token quantities affect different parts of the calculation. An increase in dollar TVL could occur while qualifying quantities stayed unchanged. Withdrawals could also coincide with higher prices, leaving their effect partly obscured in the combined dollar figure. A chart's direction alone therefore did not identify net deposits.

Factory monitoring connected new pools to coverage

Monitoring a protocol's factory contracts brought newly created addresses into the qualifying address set. For a decentralized exchange, this connected new pool creation with deposit tracking. Discovery established where assets could enter the measurement; the asset filters still governed their contribution. A larger tracked address set could expand coverage without changing the meaning of asset eligibility.

Global TVL removed claims on already counted collateral

Global aggregation excluded derivative assets when their underlying collateral already contributed to another protocol's TVL. This adjustment addressed overlapping economic claims across protocols. A representation of deposited assets could appear in a second financial application while the underlying holdings remained in the first. Adding both valuations without an adjustment would count the same backing more than once.

The exclusions covered debt tokens whose collateral counted toward lending-platform TVL, liquidity-provider (LP) tokens whose underlying assets counted toward decentralized-exchange TVL and vault tokens whose backing counted toward vault-platform TVL. This was a global aggregation rule, so a token's treatment in an individual protocol did not automatically establish its treatment in the global figure.

Snapshot dates fixed the meaning of historical totals

A historical total described the eligible assets and valuation inputs associated with its measurement time. Adapter-based integrations recorded timestamps and block context for balance retrieval. They also supported historical points, allowing earlier balances to be reconstructed when maintaining a data series. Retrieving or recalculating an older point did not turn that point into a measure of today's deposits.

The former main website now displays a domain-registration page. Older chart figures retain their original time scope. They describe dated measurements, not live readings of deposits or liquidity. Each value's measurement period supplies the time context for its prices, holdings and coverage, even when the historical record remains accessible.

Coverage changes qualified protocol comparisons

Comparisons depended on the contracts, chains and assets each measurement included, as well as the time of valuation. A protocol's name did not imply that every deployment appeared in a particular total. The historical platform FAQ described Ethereum-mainnet-only tracking. Legacy adapter code included configurations for other chains, but their presence did not establish inclusion in published totals. Comparing a chain-specific record with a broader estimate would mix measurement boundaries. This could explain a difference between reported totals even when both tracked the balances within their own scopes correctly.

Changes in deployed contracts also required corresponding maintenance of adapter-based integrations. Missing a later deployment could leave relevant holdings outside an older address set. Conversely, reconstructing earlier data could extend the history of an existing series. Either situation affected the interpretation of a comparison. Consistent definitions helped distinguish changes in measured capital from changes in what the measurement covered.

Capital measurements answered a different question from wallet activity

TVL described the value of qualifying deposits, while wallet activity described interactions with the protocol. Defipulse's Growth Internals used wallet addresses to examine acquisition and retention over time. That adjacent measure addressed participation, which the dollar total alone could not establish. Counting capital and counting interacting addresses used different units and could reveal different patterns.

The same distinction separates deposited value from trading volume or earned returns. A stock of assets does not specify how often those assets traded or what holders earned during a period. For a historical capital comparison, the filtered series supplied the relevant measure within its recorded scope. For present participation or returns, appropriately dated activity or performance measurements answered those different questions.

View image file