How the CAKE net supply drop and burn totals are calculated
CAKE’s emission builds up at 44 CAKE per BNB Smart Chain block and is minted in weekly lumps, and most of it is burned within a week. So this tracker leads with how much CAKE’s supply has shrunk rather than how much has been burned.
Net supply is read at the block of each weekly transfer from PancakeSwap’s burn Safe to the dead address. Before the first such transfer, on 15 September 2021, it is read at the last block of each UTC day. Every day holds the latest reading.
The net supply drop is the highest reading, 392,073,932.81 CAKE right after the burn of 11 September 2023, minus the latest reading. Its share is that drop ÷ 392,073,932.81.
The homepage, category and dashboard rankings use the same net figures for CAKE. For any period they show the change between the readings held at its start and its end, with its sign, so a period in which more CAKE was minted than burned is negative.
The two lines below are gross: every CAKE ever sent to the dead address or locked for good.
Which CAKE burns are counted
Burned (dead address)
Burned is the sum of the CAKE in finalized Transfer logs of the CAKE contract (0x0E09FaBB…e81cE82) into 0x…dEaD since CAKE was created, whoever sent them.
Since 15 September 2021 almost all of it has come from PancakeSwap’s burn Safe (0xcEba6028…770a4a0e), a multisig wallet that needs 3 of its 7 owners to sign. It sends one transfer to the dead address about once a week. Before 15 September 2021, 102 other addresses sent 221,429,168.36 CAKE to the dead address.
Most of each weekly burn is CAKE minted that week. CAKE’s emission builds up at 44 CAKE per BNB Smart Chain block and is minted in weekly lumps by MasterChef v1, the only contract that can mint CAKE. The part that farms do not use is sent to the burn Safe. MasterChef v2 sets that part; it was 99.7% when the tracker read it on 30 September 2026, and PancakeSwap’s governance can change it.
For example, between the burns of 21 and 28 September 2026, 59,099,392 CAKE was minted and the burn Safe burned 59,427,617 CAKE. The newly minted CAKE was about 99% of that burn, and the net supply fell by 328,463.83 CAKE.
0x…dEaD is the standard burn address. No one is known to hold its key, and its CAKE balance has always equalled the CAKE sent to it, so none has ever left.
The history from CAKE’s creation at BNB Smart Chain block 693,963 (22 September 2020) is a fixed set of logs up to a cutoff, read from an authenticated NodeReal archive node. Their sum equals the address’s on-chain balance at the cutoff (block 124,944,124, 30 September 2026). The set holds all 265 transfers from the burn Safe that PancakeSwap lists, from 15 September 2021 to 28 September 2026.
Each update reads new logs from the same provider and adds them to a running total. It stops without moving on if that total differs from the dead address’s balance, or if CAKE’s total supply has fallen.
Permanently locked
Locked is the sum of the CAKE in finalized Transfer logs of the CAKE contract into three addresses:
| Address | CAKE held at the cutoff |
|---|---|
| The CAKE token contract itself | 156,166.56 |
| 0x…0001 | 2,080.63 |
| 0x…0002 | 43.64 |
The CAKE contract has no function that can move its own balance. 0x…0001 and 0x…0002 are the addresses of built-in functions (precompiles), which have no code that can move tokens, and no one is known to hold a key for either. Each has always held exactly the CAKE sent to it, and each is checked against its on-chain balance on every update.
What the record covers
Coverage starts when CAKE was created, at BNB Smart Chain block 693,963 on 22 September 2020. CAKE has no burn function and its total supply never falls: it is every CAKE ever minted.
On the burn calendar, a day without a CAKE burn shows as 0 once an update has checked both lines’ balances past the end of that day. No date or size of the next burn is estimated.
How each net supply reading is checked
The peak is read right after a weekly burn because CAKE is minted in weekly lumps. A reading at any other time would include CAKE minted and waiting to be burned, and would swing by up to about 60 million CAKE within a week.
A reading can still include some of that CAKE when PancakeSwap’s weekly burnCake call has not run before the burn, or when CAKE is minted later in the burn’s own block. The next reading measures the level again.
Each new reading stops the update for review:
- if it moves more than 10,000,000 CAKE,
- if the burn Safe still holds more than 1,000,000 CAKE after the burn, or
- if PancakeSwap’s weekly burnCake call last ran more than 36 hours before the burn.
The update also stops if the dead address gains more than 1,000,000 CAKE on a day without a burn from the burn Safe, or if no burn arrives for 10 days.
Every reading in the history was checked against these rules: one was flagged (18 April 2022, the day MasterChef v2 started) and kept after review, and none was dropped.
How this differs from PancakeSwap’s figures
PancakeSwap’s own peak for the same week, 391,560,247.39 CAKE, is lower. It counts the claim-contract transfer below as burned and does not subtract the 123,722.50 CAKE then at the locked addresses.
PancakeSwap counts two transfers as burned that never reached a burn address, so its burn total is 5,931,409.03 CAKE higher than this tracker’s Burned (dead address) line. The two transfers are:
- 637,407.92 CAKE sent from the burn Safe to a claim contract on 10 May 2022 (transaction 0x38a99000…9d15), and
- 5,294,001.10 CAKE sent to PancakeSwap’s team Safe on 21 April 2025 for the StakeDAO and CakePie lockers when veCAKE was retired (0x39e81c1d…e115).
Both stay in the net supply here. PancakeSwap says an equal amount is still locked in its old CAKE Pool; that is not proven on chain, so nothing is added for it.
PancakeSwap also publishes a weekly supply figure. Allowing for those two transfers and the locked addresses, it matches this tracker’s reading to within 1 CAKE in 198 of the 264 weeks compared. Most larger differences are in the CAKE counted as minted: in 18 weeks PancakeSwap counts 1.06 to 13.31 million CAKE more than CAKE’s total supply held at that week’s burn, always a whole multiple of the 44 CAKE of emission per block, and the next week agrees again. PancakeSwap does not say when it takes each week’s figure, so a reading taken some hours after the burn, which would explain this, is not verified.
Since January 2026 PancakeSwap’s governance has capped CAKE’s supply as PancakeSwap counts it at 400,000,000 CAKE, but no contract enforces the cap.
What is not counted
- CAKE in the burn Safe, which its signers can move.
- CAKE locked in the bridge contract for CAKE on other chains, and that bridged CAKE itself.
- Addresses that only look like burn addresses, such as 0xdEAD…42069.
- The two transfers PancakeSwap counts as burned, described above.
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. |
| Net supply drop since the peak | The peak reading minus the latest reading. Net supply = total supply − the CAKE at the dead address, the CAKE contract, 0x…0001 and 0x…0002, read at the block of each weekly burn; every UTC day holds the latest reading. The peak is the highest reading. |
| Share of the peak | Net supply drop ÷ the peak net supply × 100. In the rankings a period's figure is the reading held at the end of the day before the period minus the reading on its last day (for All, the peak minus the latest reading), ÷ the peak × 100; it is negative when more CAKE was minted than burned. |
| Minted and burned in the last week | Between the last two readings: burned = the rise of the CAKE held by the four addresses above; minted = the rise of CAKE's total supply; the net supply falls by burned minus minted. |
| 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. |
