DataHow DataPEDIA calculates source-aware ROI
A plain-language explanation of DataPEDIA’s non-compounded ROI, periodic return series, capital-flow treatment, and evidence labels.
The headline number is deliberately simple
DataPEDIA’s source-aware ROI uses the project’s documented non-compounded basis. Most periodic histories add publishable returns. If three monthly returns are +4%, −2%, and +3%, the displayed period-series ROI is +5%, not the +4.94% compounded result.
Fixed-basis accounts
Where total account equity and external cash flows are observable, DataPEDIA may use cash-flow-adjusted total P&L divided by external deposits. This keeps deposits and withdrawals out of performance and does not compound periodic returns.
Why not compound?
Compounding assumes profits remain invested on the same basis. Real accounts often add or remove capital, distribute rewards, resize positions, or measure income against a fixed cost. The documented non-compounded basis avoids implying reinvestment that may not have happened.
The denominator still matters
Returns may use realized account cash, time-weighted capital, total account equity, a fixed equipment cost, token balance growth, or a simulated starting balance. Each project page names the method. The common ROI column supports discovery, but the methodology determines whether two results are economically comparable.
Capital flows are not performance
Deposits and withdrawals are separated whenever possible. If a source does not expose complete capital movement, DataPEDIA may use a segmented return method, display balance growth separately, or withhold the affected value.
Source-aware means the evidence stays attached
An API-derived month and an owner-attested month can belong to one continuous history, but they are not treated as identical evidence. DataPEDIA preserves that boundary and explains any transition.