Many Token Burns Don't Shrink Supply. ZPZ Put the Rules in Code

A burn on its own tells you very little. If new tokens enter faster than old ones are destroyed, if burned room can be minted again, or if nobody can tie the burn to a transaction, supply does not shrink, whatever the headline says. ZPZ cannot promise that supply goes down either. What it does is write the rules into the contract: what pays for a burn, where burning must stop, what can never be undone, and what gets published every quarter.

ZPZ is launching, so its burns are not running yet. Every rule below is how the contracts are designed, as the whitepaper describes them. Run the simulator above to see two of them hold.

Why burns are under fire

Buyback and burn programs are everywhere in crypto, and the pushback is getting louder. The criticism is fair, and it comes down to one line of arithmetic:

Net change in supply = tokens minted or released, minus tokens burned.

A headline usually reports only the second number. When the first is bigger, supply grows while the burns make news. And a burn figure is only as good as the rules around it: where the money came from, whether the burned room can be refilled, and whether anyone can check it happened.

So instead of asking "does this token burn?", ask where the burn can leak. We found six places, and scored ZPZ on each one, including the one we cannot close.

Six places a burn can leak

1. Burned room gets minted again. Held in code.

ZPZ's cap of 10,000,000,000 counts every token ever minted, not only the ones alive today. That count only goes up. A burn lowers live supply and never makes room to mint more. Section 5.1.

2. Buybacks that fill badly. Held in code.

The buyback contract enforces transaction deadlines, minimum output, slippage and oracle safeguards, and a non-zero purchase result. If it buys more ZPZ than fits above the floor, the surplus is kept and disclosed through an event rather than burned past the line. Section 3.2.1.

3. Burns nobody can check. Held in code, then reported.

When the buyback contract is funded, the transfer, the amount received, the settlement asset and the quarter are emitted as on-chain events. The quarterly report then ties it all together, as listed further down.

4. A padded fee base. Published policy.

The buyback is funded by 10% of eligible ecosystem transaction fees: fees actually retained from completed use of published ecosystem services, after refunds, chargebacks, taxes and pass-through costs. Token price, treasury performance and other financial results do not change that base.

5. Rules that change quietly. Published policy, with on-chain events.

The 70/20/10 fee split is the initial setting. The owner can change it, as long as the parts total 100%, and every change is recorded on-chain where anyone can see it. Quarterly timing is an operational commitment, not something the contract enforces. We would rather say that than let you assume otherwise.

6. New supply outruns burns. Still open.

ZPZ is minted in phases (presale, liquidity, the staking pool, vesting) up to the 10,000,000,000 cap, so live supply can rise while those phases run. No burn rule changes that, and we will not pretend it does. What the rules fix is the ceiling above and the floor below.

The rule that holds the floor

Every protocol burn, whether a platform burn of spent ZPZ or a buyback burn, has to pass one check in the token contract: once live supply has reached 5,000,000,000, the whole burn must fit above that floor. Three things follow from that rule, and the simulator lets you test each one:

• All or nothing. A request that would cross the floor reverts in full. The contract never burns "as much as fits" and quietly drops the rest.
• At the floor, nothing burns. When live supply equals 5,000,000,000, the capacity is zero and every protocol burn is rejected.
• The buyback burns only what fits. It burns purchased ZPZ only within the capacity left above the floor and keeps any surplus, so it does not send requests that would fail.

A burn either fits above the floor in full, or it does not happen.

The floor has no ordinary setting that an admin can change. Moving it would take a contract upgrade and a published whitepaper amendment. Section 5.2 has the full wording.

What every quarterly report must show

A burn you cannot check is just a claim. The whitepaper lists what each quarterly report identifies:

1. The eligible ecosystem transaction-fee base for the quarter.
2. The 70% treasury, 20% development and 10% buyback amounts.
3. The disclosed recipient wallet and contract addresses.
4. Routing and funding transaction hashes.
5. The approved router and pair, and the execution window.
6. Purchase transaction hashes.
7. The amount of ZPZ acquired and burned.
8. Post-burn total supply and the burn capacity left.
9. Any unspent base asset returned to the treasury.

Besides the report, the contracts record on-chain events that anyone can follow: buyback funding, any change to the fee split or the wallets it pays, and any return of reserves to the treasury after buybacks stop at the floor. The token, staking, DAO and buyback contract addresses are planned to be published and source-verified on Polygonscan before DEX launch, so anyone can follow them.

Honest limits

• Burns do not guarantee a smaller supply. Phased minting up to the cap can add more than burns remove while those phases run.
• The split can change. 70/20/10 is the initial setting; the owner can change it, and the change is visible on-chain.
• Timing is a commitment, not code. The contract does not enforce a quarterly execution window.
• Buybacks run through the owner. An automation service has no execution permission of its own. Multisig and timelock administration depend on the deployed ownership setup.
• No eligible fees, no buyback. The buyback is a share of fees actually retained. If there are none in a quarter, nothing is bought.
• At the floor, buybacks stop. The 10% share keeps accruing in the buyback contract and can be returned by the owner only to the treasury wallet.
• The floor is a supply rule, not a price promise. It says nothing about what ZPZ is worth.
• The simulator is an illustration. It runs the rules as the whitepaper states them, with example figures. Nothing in it happens on-chain.

FAQ

Do ZPZ burns shrink supply?

Each burn lowers live supply, and burned tokens can never be minted again. Whether total supply shrinks over a period depends on how much is minted in the same period, and ZPZ is minted in phases up to its 10,000,000,000 cap. The rules fix the ceiling and the 5,000,000,000 floor, not the net direction.

Can the burn floor be lowered?

Not through any ordinary setting. Changing it would take a contract upgrade and a published whitepaper amendment.

What pays for ZPZ buybacks?

10% of eligible ecosystem transaction fees: fees actually retained from completed use of published ecosystem services, after refunds, chargebacks, taxes and pass-through costs.

What happens if a buyback buys more than it can burn?

The burn stays within the capacity above the floor. The purchased surplus is kept and disclosed through an on-chain event.

How will I check that a burn happened?

Each quarterly report lists the funding and purchase transaction hashes, the ZPZ acquired and burned, and the post-burn supply. The contract addresses are planned to be published and source-verified on Polygonscan before DEX launch, so you can match the report to the chain.

Is the simulator the real contract?

No. It is a page on this site that runs the floor rule and the mint cap rule exactly as the whitepaper states them, with example figures. For launch timing, see the roadmap.

Start here

See the tools ZPZ is designed for. You can ask EZRA 5 free questions a day and get the free Finn app for TradingView. EZPZ Trading, EZRA, AiPe, Finn and TradingVox are live today; ZPZ's connections to them are planned.

Then read section 3.2 on burns, section 3.2.1 on the buyback rules and section 5.2 on the floor, see the full supply picture in ZPZ Coin Tokenomics, and follow @ZPZcoin on X for news as it lands.