
DeFi metrics that mean something
Avoid misleading DeFi dashboards by defining metric boundaries, valuation inputs, liquidity context, and protocol dependencies.
Read the guideCRYPTOCURRENCY DEFI
Define the measurement before drawing the chart. Keep protocol balances, liquidity, volume, and yield assumptions separate.

A lending market, an exchange pool, and a vault need different data models. Begin by describing the entities and flows the application intends to observe. Do not force every protocol into one generic balance field simply because the interface uses a shared card component.
The accompanying field note links to Ethereum.org’s conceptual DeFi overview. The measurement framework on this site is an editorial proposal for read-only research, not a safety assessment or a claim that all protocols share the same accounting structure.
Write down which assets and contracts contribute to your chosen total value locked calculation. Preserve quantities separately from price inputs. Document how the method treats representations, receipt tokens, borrowed assets, and relationships with other systems where relevant.
A change in reference prices should be distinguishable from a change in underlying quantities. Test both with synthetic data. Without that separation, a chart can describe a price-driven movement as if capital entered or left a protocol.
Do not turn a large balance into a promise about an arbitrary trade outcome. A liquidity-oriented estimate needs a market, size, direction, state reference, and method. Label assumptions and preserve unknowns.
Likewise, keep trading volume attached to its interval, market set, units, and deduplication rule. An activity figure alone does not establish independent demand or predict future returns.
Separate gross from net figures, annualized estimates from realized outcomes, and temporary components from longer observation windows. Do not bury assumptions inside an unexplained percentage. The staking route provides a detailed framework for rewards, fees, compounding, and valuation effects.
Activity metrics do not certify smart-contract safety. Record dependencies and reviewed documents with their actual scope. Distinguish not reviewed from not applicable. A missing warning should not become a positive endorsement.
For indexed observations, preserve state context and source age. The Ethereum log guide explains stable event identities and recoverable imports. Use the full DeFi field note below to connect those records to transparent metric definitions.