Volume Bots
Continuous buy-and-sell cycles through disposable wallets.
A volume bot buys and sells a token on a loop, through wallets it creates, funds and empties itself. Several bots can run at once, one per token, each with its own wallets, log and stop switch.
How a cycle works
For each wallet, in turn: fund it from the base wallet, buy, hold for a random interval, sell, then sweep whatever is left back. Amounts and intervals are randomised between the bounds you set, so the pattern does not read as a machine.
Three numbers that are easy to confuse
| Setting | What it means |
|---|---|
| Wallets | How many sub-wallets the run creates in total, over its whole life. 0 means keep making new ones until stopped. |
| Trading at a time | How many are alive at once, taking turns. This is what someone reading the chain sees. |
| Rounds per wallet | How many buy-and-sell cycles each wallet does before it is retired and swept. |
50 wallets with 2 trading at a time is not 50 addresses trading. It is 2, for as long as it takes the other 48 to have their turn, which can be many hours. If you want more addresses visible at once, raise Trading at a time, not Wallets.
The other settings
-
Base wallet. Funds every cycle and receives every sweep. It needs to hold the working capital plus gas for the whole run, and the bot stops creating wallets when it cannot afford another.
-
Amount range and hold / gap ranges. The randomisation bounds. The gap is between trades across the whole pool, not per wallet.
-
Gas buffer. Extra coin sent to each wallet purely to pay its own gas. The form warns if it is too small to cover a buy, an approval, a sell and a sweep at the current gas price.
-
Max in flight. Capped deliberately. A hundred transactions at once is not more volume; it is a rate-limited RPC and a pool moving against every one of them.
-
Relay funding. Off, every sub-wallet is a spoke off one hub, which is obvious from a single glance at the base wallet's transfers. On, a retiring wallet sends what it has left straight to its successor, so funding reads as a chain of traders paying each other. It hides nothing from anyone willing to walk the graph; it removes the star.
-
Venue. Where the token trades. Every launchpad the chain carries has its own card, plus the pool and the plain pair. On a chain whose launchpad answers for its own tokens there is also Read from the token, which resolves it at the start of the run.
Pinning a venue is a check, not an override. If the token is in a different phase the run stops before spending anything and names the venue it belongs to, because a bot pointed at a curve for a graduated token quotes zero and prints no volume at all. The status panel always shows the venue the run resolved, which is the one it is really trading on.
Find pools
Optional, and read-only. It asks every launchpad on the chain whether it knows the token, then scans for pairs and pools, and reports what it found with the depth of each:
| Badge | Meaning |
|---|---|
| on the ... curve | Still on a bonding curve, named. There is no pool anywhere yet and no aggregator can route to it. |
| trading in a pool | It has a pair or a pool. The list below names each one and how deep it is. |
| no venue found | Nothing on this chain trades it. Usually a wrong address, or a token on another chain. |
The depth column is the coin side of each pool, which is the practical measure of how much a trade can absorb before it moves the price. A bot sized above it is paying the spread to itself.
Stopping
Stopping is cooperative. The bot finishes the round it is in, sells every open position, sweeps every wallet, and only then reports. It is not killed mid-cycle with a funded wallet holding tokens.
The platform fee is taken after that wind-down, on the volume actually printed. A run stopped halfway is charged for the half it printed, not for what it was planning to print.
Recovery
Every sub-wallet key is written to an encrypted vault as the bot creates it, before any money moves to it. If a bot dies badly, or the server restarts, which ends every running bot, the funds are not lost: the Unrecovered runs list on the page replays the sale and the sweep from the vault.
A wallet is only listed as stranded if the chain says it still holds something. A wallet whose funding transfer never landed is listed as failed, and there is nothing to recover from it.
A deployment update restarts the service and therefore stops every running bot. Stop them yourself first if you can, and recover them from the vault if you could not.
Cost
The platform fee is 0.5% of the volume printed, where a buy and its sell each count. Gas and the venue's own fees are on top, per cycle, and on a thin pool the round trip loses the spread every time.
Volume is a cost, not a profit. A healthy round trip returns most of the funding: on a fork, wallets typically come back with 97% to 99% of what they were funded with, and the rest is gas, the curve's fee and the spread. Size a run by what you are willing to spend on it.