How the PONS burn total is calculated
PONS has no burn function, so a PONS burn is a transfer to the dead address, from which no one can ever spend it. The total adds up the PONS in every finalized transfer into that address on Robinhood Chain since the token was created.
Most of this PONS was bought on the market and then burned. Pons, the launchpad behind the token, says in its documentation that it uses 80% of its protocol fees for these buybacks, and that this share is not fixed yet. The tracker does not rely on that policy: it counts what reaches the dead address, whoever sent it.
PONS runs on Robinhood Chain, but Pons’s site says that Pons is not affiliated with Robinhood Markets, Inc. Its MiCA white paper of October 2026, published by Pons Labs LLC of Delaware, says a community member launched the token and the platform adopted it later.
Which PONS burns are counted
Burned (dead address)
Burned is the sum of the PONS in finalized Transfer logs of the PONS contract (0x39dBED3a…3C4571) into 0x…dEaD, whoever sent them.
In the launch week, 13 to 19 July 2026, 195.42 million PONS reached the dead address in 134 transfers. Three wallets sent 98.28 million of it in a few large transfers, among them one of exactly 39,000,000 PONS on 13 July, the day the token was created. A fourth wallet (0xda4b…3968) sent the other 97.12 million in 103 transfers, starting that evening.
That wallet went on burning until 2 September 2026: 178.59 million PONS in 1,532 transfers in all. Since 2 September 2026 the burns have come from a contract (0x5795…c324) in many small transfers a day, about 150 a day in mid-November 2026. Pons’s documentation describes an automated buyback, but it names neither the contract nor the wallet before it.
The burning wallets received their PONS from trading contracts, mostly the PONS trading pool, which fits buying on the market. The tracker has not traced the money behind those purchases, and it does not check the 80% share. The contract can be upgraded, so how it works can change.
Burned PONS is not destroyed: the contract still reports a total supply of 1,000,000,000, and the burned PONS sits at the dead address.
0x…dEaD is the standard burn address. No one is known to hold its key, and its PONS balance has always equalled the PONS sent to it, so none has ever left.
The history from creation block 8,963,150 is a fixed set of Robinhood Chain logs up to a cutoff, read from Robinhood’s public node, and their sum equals the address’s on-chain balance.
Each update reads new logs up to the chain’s latest finalized block, so the figures run about a quarter of an hour behind the chain. It then adds the transfers that are not finalized yet, compares the result with the dead address’s balance at the newest block, and stops without moving on if the two differ.
The other dead-address trackers read the balance at the finalized block itself. That is not possible here: Robinhood’s public node keeps balances for only about ten minutes, less than a block takes to become final.
What the record covers
Coverage starts when PONS was created, at Robinhood Chain block 8,963,150 on 13 July 2026. The supply baseline is the fixed 1,000,000,000 PONS minted then. Every update checks that the contract still reports that supply and stops if it does not.
What is not counted
- Zero-value transfers, which move nothing.
- PONS held by the PONS token contract itself, 16,432.44 PONS on 16 November 2026. Nothing reviewed proves the contract can never move it.
- PONS held at any other address, including the buyback contract and the wallets that burn, until it reaches the dead address.
- PONS that has been bought back but not yet burned.
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. |
