the ape

aped is a bot that buys its own coin, and burns what it buys.

Every $APED trade pays a fee to the coin’s creator, and the creator is the bot. It claims that fee continuously, and spends it in fixed 0.05 SOL buys, destroying what it buys in the same transaction that buys it. Then it does it again.

Small buys, over and over, is the point. A percentage of the vault would mean one big burn now and then. 0.05 at a time means a burn lands constantly, each one its own transaction you can open. The loop runs on buying pressure and it feeds itself buying pressure.

It cannot sell. That is not a promise. The code has no sell function, so there is nothing to switch on later, and the bot’s wallet history is public if you would rather check than believe.

None of the numbers in this window are decoration. They are read live from the chain and from the bot. Anything that has not happened yet shows a dash until it has.

the record

Everything it does, as it does it.

Every entry that moved money carries its transaction signature; open tx to see it on solscan. Failed buys stay in the record with the reason. They are not hidden, because hiding them is how you end up trusting a bot that stopped working.

the coin

The cap is read live from Dexscreener in your browser, not reported by this site. Burned supply is the chain’s own count: starting supply minus what exists now. Both keep working with the bot switched off, because neither is the bot’s word for anything.

The contract address will appear here when the coin is deployed. If a coin is trading under this name before that, it is not ours.

the rules it runs under

Six rules. All of them checkable.

• One job. Claim the vault, buy $APED, burn what it bought. One transaction for the buy and the burn, so there is never a moment where the bot is holding tokens that could go anywhere else.
• 0.05 SOL per buy. Every buy is the same size, whatever the vault holds. It buys again as soon as there is another 0.05 to spend, so burns land constantly rather than occasionally. When income dries up, a final sweep spends the tail instead of stranding it.
• No sell function. Nothing to switch on later. See for yourself.
• It can only spend what the coin earned. Spending is capped at what it has claimed in fees. Anything else that touches the wallet sits there, untouchable.
• Failures are published. A buy that fails shows up in the record with the reason, next to the ones that landed.
• A restart costs nothing. The books are written to disk as it goes, so if it stops and starts again it resumes from exactly where it left off. Nothing is spent twice on the way back up, and nothing is forgotten.

These are not settings we promise to respect. They are how the program is built, and the parts that touch the chain can be checked on the chain.

the manual

The name. Old computer programs that run by themselves in the background have names ending in d: sshd, httpd, crond. The d stands for daemon, which is just the old word for that kind of program. An ape one is therefore called aped. We are aware of the other reading. No fix is planned.

The loop, end to end. A buy pays a fee. The fee lands in the creator vault. The bot claims the vault and spends it 0.05 SOL at a time, burning what it buys in the same transaction, over and over for as long as there is fee income. So buying pressure becomes burned supply, continuously. Nobody has to take that on trust: the fees, the claims and the burns are all separate transactions on a public chain.

The receipts. Nothing in this window is self-reported. The bot’s wallet and every transaction it has ever signed are public, each burn links its signature in the activity tab, and the burned-supply count is the chain’s own arithmetic. If this site vanished tomorrow, the burns would still be sitting on the chain, readable by anyone.

The paperwork. For the terminally curious, it is kept in its original formatting: the manual page, the config, the service file, the raw journal, and the place everything it buys ends up.