How burn data is counted

The leaderboard reads confirmed token transfer logs and protocol burn records from supported networks. EVM and Solana projects appear under the review and listing rules below. The ranking shows eligible projects with a token logo, a recent reliable price, at least $100 in valued burns during the selected period and at least $100,000 in current market cap; tokenized equities and leveraged wrappers are excluded. Projects with a measured holder-address count below 100 are also excluded. Unavailable counts remain unknown and do not cause exclusion. Reviewed projects may include other approved burn addresses. All displayed projects require a logo. This is a tracked-token leaderboard, not a census of every burn on a network.

Onchain evidence

For ERC-20 tokens, we read Transfer(address,address,uint256) logs emitted by the token contract where the recipient is an approved sink. Transfers to the zero and dead addresses are marked separately; transfers from the zero address are excluded as mints. Neither event alone proves a totalSupply() decrease for every token. Events are identified by chain, token contract, transaction hash and log index. WSS follows live logs; a limited public RPC scan fills the first 24 hours and detected connection gaps. Confirmed block hashes and removed-log notices handle reorganizations.

USD value and market cap

Token amounts come from chain logs and onchain token decimals. Reviewed projects use historical UTC-day prices when available. Automatically listed tokens use a recent DEX Screener price as an estimate for observed transfers. Market cap is generally a current DEX quote. LUCA uses a recent CoinMarketCap quote matched to its exact contract after its DEX market cap proved inaccurate. Ratios above 50% are withheld until checked. Automatically discovered tokens without a reliable price or token decimals remain in the raw records but are omitted from the ranking. These estimates are external data, not chain facts.

Holder addresses

Ethereum and Robinhood Chain holder counts come from Blockscout token counters; BNB Smart Chain counts come from GoPlus token security data. Counts are cached for one day. A holding address may be a contract or an exchange, so this measures addresses with balances, not unique people. Raw burn records remain available when a project is omitted from the ranking.

Solana mint tracking

Submitted Solana mints are checked against the SPL Token or Token-2022 program, then followed by a finalized log subscription for that mint. We read successful transactions and count only parsed Burn or BurnChecked instructions for the same mint. This is live tracking from subscription time, without historical backfill. A Solana project appears only after owner approval, with a DEX token logo, a price and at least 100 measured holder addresses. USD values use a recent DEX price at the time each burn is observed. Connection interruptions leave coverage marked partial.

Hyperliquid HYPE

Hyperliquid's official fee documentation says the Assistance Fund automatically buys HYPE on HyperCore and that its HYPE is burned by the protocol. We read the fund's HYPE spot fills from the official Info API, deduplicate by trade ID, and value each purchase using its executed price. These are protocol buybacks treated as burns under Hyperliquid's published rules, not transfers to an EVM burn address or an independently observed decrease in totalSupply(). Individual records show the trade ID and any available transaction hash. Collection starts with the latest 24 hours and continues live; longer periods remain partial until enough observations accumulate.

Hyperliquid HIP-1 tokens

For PURR and HFUN, we compare successive totalSupply readings from Hyperliquid's official tokenDetails Info API. Only a decrease is counted; increases and unchanged supply are ignored. Hyperliquid's HIP-1 rules explain that non-deployer spot fee portions and some spot dust are burned. Value uses the token's mark price at the later reading. Evidence shows the before and after supply and links to the token explorer. The observation time is not an exact burn transaction time, so we do not invent a transaction hash. Collection begins with the first successful snapshot; prior history is not backfilled.

Coverage and submissions

The 24h, 7d and 30d windows are calculated from locally stored events. Longer windows mature over time; results remain marked partial while a scan or gap repair is incomplete. Ethereum, BNB Smart Chain and Robinhood Chain have EVM discovery. Solana uses submitted mint subscriptions and starts counting only after submission. Automatic EVM discovery covers ERC-20 transfers to the zero and dEaD addresses, excluding mints. A DEX listing does not prove a decrease in token supply or project legitimacy. Projects can submit a token address using the form on the leaderboard or the public project API. Submissions enter the owner review queue before public listing.

Read-only interfaces: GET /api/v1/burn-leaderboard?period=24h|7d|30d, GET /api/v1/burn-projects, and GET /api/v1/burn-events?networkId=ethereum&tokenAddress=0x…&period=30d. Submit with POST /api/v1/burn-project-submissions.