What source-aware performance tracking means

A return is only as interpretable as its source

Two identical percentages can carry very different confidence. One may come from a complete exchange ledger; the other may be copied from a promotional dashboard. Source-aware tracking preserves that difference instead of flattening every number into one table.

Primary, reproducible sources

Public blockchains, dedicated account APIs, and protocol APIs can often be queried repeatedly. They support transaction-level or snapshot-level histories and make automated monitoring possible.

Document and approval sources

Broker exports, statements, and approved ledgers can be high quality even when they are not continuously accessible. DataPEDIA records their coverage window and refresh process.

Screenshot and owner-attested sources

These can responsibly fill a gap when no direct feed exists, but their limitation must be permanent and visible. They should never be relabeled as API-derived history.

Completeness matters as much as authenticity

A real transaction list can still omit transfers, open positions, fees, or earlier history. DataPEDIA evaluates what the source covers, not merely whether the source is genuine.

Why this improves comparisons

Users can distinguish independently observed performance from reported performance, understand why a metric is unavailable, and decide whether the remaining evidence is sufficient for their own research.