How the PURR burn total is calculated
PURR’s burned total has two lines, shown separately: one launch burn of 400,000,000 PURR on 16 April 2024, when spot trading in PURR opened on Hyperliquid, and the trading fees paid in PURR, which HyperCore destroys.
Most of the total is the launch burn: 98.7% of it on 3 October 2026.
Both lines come from Hyperliquid’s own PURR supply on HyperCore. Total burned = 1,000,000,000 PURR (maxSupply) − totalSupply. The launch burn is a fixed 400,000,000 PURR of that, and the HyperCore fee burns are the rest.
Which PURR burns are counted
Launch burn
The launch burn is 400,000,000 PURR, counted once as an opening balance dated 16 April 2024. That is 40% of PURR’s 1,000,000,000 supply. It had first been set aside as HIP-2 liquidity for the PURR/USDC order book (Hyperliquidity, the automatic market making that Hyperliquid runs on a new token’s order book), and Hyperliquid burned it instead when spot trading opened.
The source is Hyperliquid’s own announcement on X on 16 April 2024 (x.com/HyperliquidX/status/1780079468918587507): 40% of the supply first allocated to HIP-2 would be burned instead. Hyperliquid published no transaction or exact time for the burn, so it is dated to that day.
Hyperliquid’s own figures agree with it. maxSupply − totalSupply is above 400,000,000 PURR in every reading the tracker takes, and PURR’s linked HyperEVM contract (0x9b498c3c…1872b44e) has a total supply of exactly 600,000,000 PURR, the supply left after the burn.
The tracker reads PURR’s supply every hour for this line, and both PURR lines stop if maxSupply − totalSupply is ever below 400,000,000 PURR. Each UTC day that passes this check is recorded as 0.
HyperCore fee burns
Under Hyperliquid’s HIP-1 token standard, the trading fees paid in a spot token go to the token’s deployer at the deployer’s fee share, and the rest is burned. PURR’s deployer fee share is 0, so every trading fee paid in PURR on the PURR/USDC order book is burned. Buyers pay their fee in PURR, the token they receive. Sellers pay theirs in USDC, which is not burned. So only the fees paid in PURR burn PURR, not every trading fee.
The line has three parts:
- From 3 October 2026: each UTC day adds the change in that figure from the day’s first reading to the first reading after the next midnight. The tracker reads about every five minutes.
- From 26 May 2025 through 2 October 2026: each day is the trading fees paid in PURR on the PURR/USDC order book, added up from Hyperliquid’s official trade archive, with maker rebates paid in PURR subtracted.
- From PURR’s launch through 25 May 2025: everything burned is one 2,927,950.28804 PURR opening balance. It is the fee burns at the first reading of 3 October 2026 (5,203,487.10958 PURR) minus the 2,275,536.82154 PURR of archive days.
The fee burn follows trading in PURR. From 26 May 2025 to 18 November 2026 it averaged about 4,500 PURR a day, but on half of those days less than 3,000 PURR was burned, and on the busiest, 23 August 2026, more than 45,000. The 7-day and 30-day figures at the top of the page give the current pace.
Each reading is one request to the official HyperEVM RPC. It calls Hyperliquid’s tokenInfo, tokenSupply and spotBalance read precompiles for PURR (HyperCore token 1). Every read in the request has to see the same HyperCore block, or the request is repeated. A reading is rejected unless the token is PURR with 5 decimals, maxSupply is exactly 1,000,000,000, and circulating supply + non-circulating balances + future emissions add up to totalSupply exactly. Both boundary responses, with their HyperCore blocks, are stored with every daily figure.
The archive days come from 11,892 hourly files of Hyperliquid’s own node data, which record every trade with its fee and the token the fee was paid in. They were checked against the supply readings twice. From 15:45 UTC on 1 October to 18:15 UTC on 2 October 2026 the archive fees add up to 9,522.88444 PURR and the supply fell by 9,523.62813 PURR. From then to the first reading of 3 October they add up to 2,672.83271 PURR against 2,673.13951 PURR.
The archive explains the measured burn to within 0.02% and lacks 53 of about 493 million blocks. The opening balance carries the difference, so the total stays exact.
What the record covers
Coverage starts when PURR launched on 16 April 2024. The supply baseline is a fixed 1,000,000,000 PURR: PURR’s maxSupply on HyperCore, which is set when a HIP-1 token is created and cannot grow. The burned share is total burned ÷ 1,000,000,000.
The launch burn and the fee burns from launch through 25 May 2025 are opening balances. They count in the all-time total, the burned supply and the cumulative chart, but not in today’s, 7-day, 30-day or other dated figures.
Fee burns are counted day by day from 26 May 2025, because Hyperliquid’s archive records no trading fees before then. The last archive day, 2 October 2026, runs to the first supply reading of 3 October (00:14 UTC), where the daily readings take over. HyperCore amounts for the current UTC day are added when the day closes, so the 7-day and 30-day figures add the last 7 or 30 closed days, not the current one.
Why no PURR is counted twice
No PURR is counted twice. The fee-burn line subtracts the 400,000,000 PURR launch burn from maxSupply − totalSupply, so the two lines add up to exactly maxSupply − totalSupply.
What is not counted
- The PURR at the HyperCore zero and dead addresses (about 11.31 PURR on 1 October 2026), which is still part of totalSupply.
- Trading fees paid in PURR on order books where PURR is the quote token. They go to Hyperliquid’s Assistance Fund and are not burned.
- Any trading fees paid in USDC.
- PURR moved between HyperCore and HyperEVM, which is a transfer, not a burn. The HyperEVM zero and dead addresses held no PURR on 1 October 2026.
How the figures on this page are calculated
Every tracker works out its figures the same way. Days are UTC calendar days.
| Figure | How it is calculated |
|---|---|
| Total burned | Every accepted daily amount of every mechanism, from the date that mechanism’s coverage starts. A record counts only once it is final: a finalized burn record, or a finalized daily figure from the chain’s official data provider. Duplicates and records held back for review stay out. |
| Today, 7-day and 30-day burn | Burns are added up by UTC calendar day. Today is the current UTC day. The 7-day and 30-day figures add the current day and the 6 or 29 days before it. On a tracker with a line read once per UTC day, which adds nothing to the current day until it closes (the HyperCore lines of HYPE and PURR), they add the last 7 or 30 closed days instead, and the card names the last one. A day with no record adds zero, and opening balances are left out. |
| Latest burn | The newest burn record, or the newest UTC day with a burn when that day is later (for lines kept as daily totals). A transfer into a burn address worth less than $1 at the latest price, and a day whose burns are worth less than $1, are passed over as dust; they still count in every total. Fee burns are never dust, however small. |
| Daily and moving averages | The 7-day and 30-day averages on the cards divide those totals by 7 and 30. The average lines on the charts are plain averages of the last 7, 30, 90 or 365 daily rows, or of as many as there are. |
| Daily USD estimate | The day’s burn × the last CoinGecko USD price stored on that same UTC day. It is shown with ≈ and rounded. It is left out when no price was stored that day, and on cumulative-chart points that include an opening balance, because that balance built up before the date shown. It is a reference value: not the price at the time of each burn, not a volume-weighted price, and not sale proceeds or an exact trade value. The figure for the current UTC day can still change as burns and prices arrive. |
| Burned supply | Total burned ÷ the all-time peak supply × 100. That baseline is not the latest circulating supply, and it comes from a different source than the market data. |
| Mechanism and contributor shares | A mechanism’s amount ÷ the total burn on record, or a known contributor’s amount ÷ that total. Burns with no known sender stay in the total and are not assigned to anyone. |
| Cumulative chart | For the range you select, the chart starts at the all-time total minus the days in the range, then adds each UTC day back in order. The change over the range is the last value minus the first. |
| Burn calendar | A cell is the sum of all mechanisms for that day. Its colour ranks the day against the others, by relative size or by percentile, and never changes the amount. A day with no record is blank, which means unknown. The exception is a tracker whose every mechanism proves the day, in one of two ways. Either the mechanism holds every transfer into its burn addresses, or their exact balances, from the start of its coverage, checks them against the on-chain balances on each update, and has checked past the end of that UTC day. Or its history is complete and closed, because the chain or program that burned can burn no more. On those trackers a day with no burn shows as 0. |
| Time to burn another 10% | (Latest reported total supply × 10%) ÷ the selected daily burn pace ÷ 365.25, in years. It is a straight-line scenario, not a forecast: it assumes supply policy, issuance, activity and burn rate all stay as they are. |
