You snooze, you win. where to buy · contract checker · size curve · standing order · getting a slot
These are read from the pool on the live site. They are editable here so you can see what the dial does before you hold any. The same arithmetic runs in quoteSell() on chain, so the number here and the number you get cannot drift apart.
If the price is above its 24-hour average and you sell today, the difference burns. If it is at or below the average, you sell at today's price and nothing burns.
No wallet sells more than 20% of its balance per day, whales included. Splitting across fresh wallets does not help: five wallets holding a fifth each sell 20% of a fifth, which is the same 20%. It used to cap every transfer, which capped nothing extra and broke every router, deposit address and swap widget on Base. One address is exempt — the launcher's, which cannot seed the pool without it — and the same flag also skips the haircut, so that wallet is outside both rules and stays that way after freeze(). Read capExempt() on the launcher's address before you believe any sentence about fairness, this one included.
Fixed supply, and it only falls — provided the deployer took no share of the burn. The contract answers that itself: supplyOnlyFalls() returns false if any part of the haircut is paid out instead of destroyed, so this page cannot claim it by accident.
Every line here came out of running the contract, not out of writing the pitch. They are the parts a buyer is most likely to get wrong.
The burn is (price − average) / price, which is zero whenever the price is at or below its average — which is exactly what a downtrend looks like. Selling into a crash costs nothing. Rule 1 taxes selling into strength only. "Dumpers fund the burn" is not true of the dumpers you care about; Rule 2 is the only thing slowing them.
Tomorrow you are paid the lower of tomorrow's price and tomorrow's average. If the price falls back overnight you get the fallen price, and the spike was never yours. Waiting trades a certain haircut for an uncertain price. That can be a good trade. It is not the same as "tomorrow the jump is yours".
A wallet that moves its full 20% every day still holds 32.8% after five days and 10.7% after ten. Tokens are uncapped once they arrive somewhere, and each new wallet gets its own 20%, so a determined exit spreads and drips in parallel. It is slower than a nuke. It is not five days and done.
Buy at a price 70% above the average and your immediate exit value is the average — you are down 41% the moment the transaction confirms, and 41% is the number at the top of this page. The pitch says Rule 1 stops buying the top being the dumbest trade on the chart. It does the opposite: it makes the loss mechanical and immediate instead of probabilistic. The higher the dial, the worse a moment it is to buy, not just to sell.
20% of what remains, every day, is geometric. A wallet holds 32.8% after five days, 10.7% after ten, 0.12% after a month, and never reaches zero. There is no lock-up period because there is no end to it. That is a softer constraint than a cliff and it is not "no lock".
The haircut only fires on addresses the deployer registered as pools. Any other venue — a pool nobody registered, an OTC counterparty, a wrapper contract — takes tokens at no haircut. And registering is disabled by freeze(), which is exactly what you should want the deployer to call. So either the deployer keeps the power to change the rules, or new venues are permanently outside them. There is no setting where both hold.
A 24-hour average needs 24 hours. Until the oracle has a full window the burn reads zero, so "snipers get nothing" does not hold for the first day — the day snipers care about. The dial says warming up while that is true rather than showing a reassuring 0%.
Exchange deposits, bridges, aggregator routes, lending markets and LP withdrawals all move more than 20% of a balance at once as a matter of course. They will fail, and to someone who does not know the rule a failed sell looks exactly like a honeypot. Scanners flag this shape for that reason.
This page describes a mechanism. It does not prove that the token you are about to buy implements it. Those are different claims and only the second one costs money.