Ethereum: define the boundary
Separate network deployments, capital migration, and valuation changes before interpreting an ecosystem total.
DeFi Meter Lab / Topic tag
Units, windows, and definitions first.
These guides examine the choices behind a useful metric: what is included, when it was observed, and which denominator makes the calculation meaningful. Follow them from the core framework through ecosystem boundaries, TVL accounting, and repeatable daily notes. Keep raw observations alongside derived changes.
When a source, scope, or category policy changes, reconcile the difference before joining the values into one continuous series. Clear labels are part of the analysis, not decoration. Begin with a balance-versus-flow distinction and then check valuation conventions. Ask whether the number describes one pool, a deployment, or a provider-defined aggregate. Preserve missing observations as missing rather than silently replacing them with zero. The guides below provide worked examples that make these choices visible without pretending to publish live figures or standardized market scores.
Separate network deployments, capital migration, and valuation changes before interpreting an ecosystem total.
Build a four-lens research framework that separates liquidity, activity, market context, and unresolved risk.
Understand balance-versus-flow measures, price effects, fee allocation, and the limits of annualized figures.
Build a repeatable read-only routine that checks freshness, preserves context, and separates observations from explanations.