Network research6 min read
Ethereum: define the boundary
Separate network deployments, capital migration, and valuation changes before interpreting an ecosystem total.
Research field guide / Ethereum
Ethereum DeFi Meter
Define the network. Respect the boundary.
An Ethereum DeFi Meter needs a boundary around its totals. Mainnet, a specific layer-two network, and a protocol’s combined deployments are different research scopes. Use this guide to separate location, valuation, and related claims before describing a change in capital or activity. No live ecosystem totals are presented here.
The question to ask
Is this a new inflow, a transfer, or a valuation change?
Separate deployments from an ecosystem label
Ethereum’s layer-two overview describes networks with different technologies and maturity levels. Use the network and deployment identifiers in your records instead of assuming that a familiar interface describes one system. Compare similar economic functions before interpreting differences between deployments.
Follow the capital before calculating growth
In a fictional two-network example, moving $100,000 from one network to another increases the destination’s balance but leaves the combined balance unchanged. A simultaneous asset-price change can alter dollar totals without adding units. Explain migration and repricing separately, keeping the valuation convention visible.
Count related claims deliberately
A record of application-level balances and a record of non-overlapping underlying capital are different measurements. State which you intend to construct before adding values. Keep receipts, represented assets, and underlying reserves identifiable. When a source changes its coverage, reconcile the difference before joining the observations into a growth series.
Primary reference: Ethereum: layer-two networks and their differences.
Your research checklist
Capture the fields that matter.
Keep identifiers, assumptions, and missing evidence next to the observation.
01
Deployment
Network and contract identifiers
One protocol name can cover multiple research objects.
02
Inclusions
Categories, related claims, and aggregation rules
Different counting policies can produce different valid totals.
03
Capital movement
Quantities, valuations, and transfer scope
Movement within a boundary is not growth of that whole boundary.
04
Dependencies
Network, asset, contract, and exit process
An ecosystem label is not a uniform technical guarantee.
Practical questions
Know the limits
of the reading.
Can layer-two totals simply be added to mainnet?
Only under an explicit inclusion policy appropriate to the question. Inspect related claims, overlaps, and coverage rather than assuming every displayed value is independent capital.
Does a lower transaction fee establish a better overall outcome?
No. A complete scenario needs the same workflow, size, and assumptions, including entry and exit steps and the unresolved dependencies of the exact system.
Continue your research
Related field notes
Foundations6 min read
TVL is not volume. Fees are not yield.
Understand balance-versus-flow measures, price effects, fee allocation, and the limits of annualized figures.
Risk & yield7 min read
Read the yield. Count the costs.
Translate a headline rate into a holding-period scenario with visible compounding, reward valuation, and cost assumptions.