Connecting to the bot…
The chart that
fights back.
Somebody sells $CATCH hard, the chart drops, and a few seconds later a bot buys back with half of the coin's creator fees and burns every token it bought. Each catch is a public transaction.
One catch, start to finish
Twenty seconds with the cat: the sell, the drop, the buy-back and the burn. The figures in the film are an example; the real catches are in the live log below.
The scoreboard
Every sell that moved the chart, the buy-back that answered it, and the burn, with the transactions on Solscan.
- Dumps caught
- 0
- SOL spent catching
- 0.00
- $CATCH burned
- 0
- Average reaction
- –
| When | Dump | Catch | Burned | Proof |
|---|---|---|---|---|
| No dumps yet. The bot is watching. | ||||
Somebody is watching the chart.
The bot reads every $CATCH trade, day and night. A sell that moves the price 5% or more gets an answer within seconds.
How a catch works
Three moves, on loop. The latest real catch replaces the example numbers once there is one.
Detect
Every trade is read as it lands. A sell of 0.2 SOL or more that moves the chart 5% counts as a dump.
Catch
The vault buys back 30% of the dump through Jupiter, up to 0.25 SOL per catch and 2 SOL a day.
Burn
Everything it bought is burned on the spot with BurnChecked. The supply only goes down, and every step links to Solscan.
The rules, written down
- Half the creator feespump.fun splits the coin's creator fees on-chain: 50% to the catch vault, 50% to the dev. Anyone can check the split on the coin page. The dev also seeds the vault at launch, and catches are paid from the vault and nowhere else.
- Public vaultThe vault address and every transaction from it are on-chain.
- CappedPer catch and per day, so one bad hour can't drain the vault.
- Stops on errorsIf a buy or a burn fails, the bot halts itself and says why. It never retries in a loop.
- What it can't doIt can't stop a dump or hold a price. Catches are smaller than the dumps they answer; they soften the hit and shrink the supply.
- Nothing left outSkipped catches, test runs and errors show up in the log too, next to the catches.
Join the catch.
The contract address goes up on X first. Follow along and watch the first dump get caught.