Every crash
gets bought.
Every 5 minutes the engine checks the price. If it has dropped 20% or more, the entire fee reserve buys $RFLX and burns it. If it hasn't, the reserve just keeps growing.
Crash it. Watch what happens.
You are the market. A small dump changes nothing. A 20% crash wakes the machine. Push the price, then watch the clock hit zero.
The whole reserve becomes one market buy. Every token it gets is burned.
Nothing is bought. The fees keep stacking for the next crash.
It ignores the noise. It answers the crash with everything.
A buyback that fires on every red candle spends its reserve in small slices, into noise. Reflex lets small dips pass and keeps stacking fees. When a real crash comes, the whole reserve hits at once.
Small dips don't count.
−2%, −5%, −12%: nothing happens. The reserve keeps stacking. That is not the machine failing. That is the machine loading.
72 simulated hours at $5M daily volume and a 2% fee: 864 checks, 6 crashes of 20% or more, average buy $47,450. Between crashes the reserve only grows.
It hits with everything.
Twelve checks pass with no crash, and the reserve stacks up. Then the price drops 24% and all of it fires in one buy. Then it starts again from zero:
Fees stack by $347 every tick. The buy is whatever has stacked up when the crash is confirmed, so the longer the calm, the bigger the answer.
A tiny buy every 5 minutes, up or down, into noise. The reserve never holds anything.
One buy, placed on the red candle that matters. The reserve grows in the calm and empties into the crash.
Honest note: this is not a promise about price. What changes is when the money goes in: all at once, right after a crash, instead of in slices across every red candle.
Simple enough to repeat in one breath.
- A crash is 20% down since the last check.Not 19. Not "feels low". Twenty.
- 100% of the reserve per crash.Not a slice. Everything that has stacked up.
- Bought tokens are burned, not held.totalSupply() on the explorer falls with every buy.
- Skipped checks are logged like fired ones.A feed that only shows buys is a highlight reel.
- No team wallet. No staking. Nothing to do.The rule runs whether anyone is watching or not.
- Check every
- 5 min
- Trigger
- price ≤ −20% vs last check
- Spend per trigger
- 100% of reserve
- Executed as
- 10 transactions, each bought and burned
- Bought tokens
- 100% burned
- Team cut
- 0%
- Minimum buy
- 0.0005 ETH · else rolls over
- Gas reserve
- 0.002 ETH
- 5-minute average price instead of a single spot sample
- A randomised execution moment inside the window
- A per-buy cap relative to pool liquidity, the rest rolls over
- A minimum reserve before the first buy
The six questions everyone asks.
What exactly triggers a buy?
One condition, checked every 5 minutes: is the price 20% or more below where it was at the previous check? Yes: the engine spends the entire reserve on one market buy and burns what it bought. No: it does nothing and waits 5 minutes.
What if the price never crashes 20%?
Then nothing is bought and the reserve keeps growing. That is not a failure state. The reserve is the buy that is waiting under the price, and the longer the calm, the bigger it gets. Fees are never spent on anything else.
Isn't the buy predictable? Can someone farm it?
The rule is public by design. To trigger it, someone has to crash the price by 20% within five minutes and eat that loss first. The buy itself is large and predictable, so it can be front-run: we are considering an averaged price, a randomised execution moment and a per-buy cap. We publish the exact rule instead of pretending it is secret.
Where do the burned tokens go?
They are burned with the token's burn function, so totalSupply() itself goes down. Nothing is parked in a wallet, nothing can be sold, re-minted or recovered. You can check the supply on the explorer yourself.
Is there a team wallet or a team cut?
No. 100% of the creator tax is the reserve, nothing is kept. The reserve sits in the dev wallet listed in the footer, and the bot spends it only on buys that are burned. Every claim, buy and burn is a transaction you can open on the explorer. This is enforced by transparency, not by a contract: verify it yourself.
Is this financial advice?
No. This page describes how a rule behaves, not where the price goes. Buy pressure is not a price guarantee, tokens can go to zero, and you should only spend what you can afford to lose entirely.
Four things we are not going to pretend away.
A large, scheduled buy is worth front-running. A randomised execution moment and a per-buy cap reduce the edge. They do not remove it.
That is what a bid is. The fees become support at the moment support is needed, and the burn returns it to everyone still holding. The transfer still happens.
A shrinking supply with no demand still goes to zero. This page describes how a rule behaves. It is not a prediction.
The reserve can sit and grow for a long time. That is by design, but it means the burn is lumpy, and the mechanism is only as big as the trading behind it.