Source hierarchy
We use native blockchain data and official provider APIs. Another analytics site may inspire a useful feature, but its totals are not used as our source.
Event verification
Every burn mechanism has a documented adapter. An event must match the configured token contract, mechanism, destination or protocol rule, and chain confirmation requirements before it enters normalized storage.
Normalization
Raw provider records are converted into one schema containing asset, mechanism, amount, timestamp, transaction reference, block height, source provider, and verification state.
Source labels
- Live: derived from a connected chain or official provider.
- Fixture: database-backed test records used to validate the pipeline.
- Prototype: illustrative interface data that must not be interpreted as current.
Corrections
Source changes, reorg handling, duplicate events, and classification corrections are logged. Material editorial corrections are noted on the affected article.