Methodology โ how Burniqo counts burns
What counts as burned
An asset counts as burned when it is held by one of the two canonical burn addresses:
0x0000000000000000000000000000000000000000 and 0x000000000000000000000000000000000000dEaD.
No private key exists for these addresses, so anything sent there is permanently out of circulation.
How totals are computed
For every tracked token contract, the cumulative burned amount is the token balance of the two burn addresses, read from the chain by our own indexer (via Etherscan API V2, the Routescan API and the chains' public nodes) every few minutes. The same method is used for each chain's native coin. Totals are per token โ amounts of different tokens are never added together; the headline USD figure sums each token's own USD value.
What is NOT counted
- Protocol burns that are not transfers โ e.g. Ethereum's EIP-1559 base-fee burn destroys ETH without sending it to an address. Other trackers quote ~4.4M ETH for that mechanism. We exclude it so that every figure here is a balance or a transfer you can verify yourself on an explorer.
- Contract burns on untracked contracts โ we only track the contracts listed on the dashboard. The list grows over time; nothing is estimated or seeded.
- Tokens without a market price show "โ" for USD rather than a made-up $0.00.
Recent burns feed
The feed lists the latest transfers to the burn addresses for tracked tokens and native coins. Every hash links to the chain's explorer so you can verify it yourself.
Why numbers differ from other trackers
Trackers disagree because they use different definitions (some include EIP-1559, some count burn-contract calls, some estimate). Our rule is simple: if our indexer cannot read it from the chain, it does not appear here.