How to Run a Volume Bot on Your Token: The Complete Setup Guide

You launched a token. The contract is live, the liquidity pool exists, and the project is real. But when someone discovers it and clicks through to the chart, they see flat lines and zero activity for days at a time.

That dead chart kills deals before they start. Even genuinely interested buyers hesitate when there is no movement — it signals abandonment, or that nobody else believes in it. Volume is social proof. An active chart tells a new visitor that something is happening here.

The solution is a volume bot: a lightweight Python script that automatically buys and sells small amounts of your token at random intervals, keeping the chart moving and signalling that the market is alive. This is not price manipulation — it is the same function a traditional market maker performs on a stock exchange, automated and running on your laptop.

This guide covers the exact bot we used to test on web3guides.com. We ran it for several days with a $10 daily cap. Total spend across all days came in under $5 — because on some days, real buyers showed up after seeing the chart activity and absorbed our sell-side at a slight premium.

The bot connects to your wallet and a Uniswap V3 liquidity pool on any EVM-compatible chain. Every one to five minutes — at a randomly chosen interval — it picks a direction (buy or sell) and a random dollar amount between your minimum and maximum settings. It executes the swap, logs the result, waits, and repeats indefinitely.

The randomisation is intentional. Perfectly spaced trades are easy to identify as bot activity. Random intervals and amounts look like an actual trader — slightly erratic, occasionally quiet, occasionally active.

On each cycle, the bot reads the current token price from the pool at no cost, randomly picks a direction and trade size, sends a signed transaction from your wallet to the Uniswap router, waits a random number of seconds, and repeats. It never pauses to analyse price trends or try to be profitable — it simply maintains consistent two-sided activity.

The daily cap is a hard limit on gross buying spend per UTC calendar day. Once reached, the bot sleeps until midnight and resets. This matters because the cap counts total buy spend, not net loss. If the bot spends $8 buying but earns $9 back selling, it still stops when gross buys hit the limit — preventing runaway spending on unexpectedly profitable days.

Why does it sometimes make money? When a real external buyer purchases tokens, they absorb some of the bot's sell-side at the current market price. If the bot previously accumulated those tokens at a slightly lower price earlier in the session, it sells into real demand at a small premium. The profit covers the swap fees and occasionally more.

Before touching any configuration, you need three things in place: a dedicated bot wallet, Python installed on your computer, and the correct contract addresses for your token.

Create a brand new wallet in MetaMask specifically for the bot. Do not use your main wallet. If a configuration error exposes the private key or a bug drains funds, you want the damage limited to the bot wallet balance. Write down the 12-word seed phrase offline and keep it safe.

Fund the bot wallet with a small amount of the chain's native gas token — 0.01 ETH is enough for weeks of trading on low-fee chains where gas costs fractions of a cent per transaction. Also fund it with three to five times your intended daily cap in USDC. If your daily cap is $10, put in $30 to $50 so it runs for several days without needing attention.

Install Python 3.9 or newer from python.org/downloads. During installation, check the box labelled "Add Python to PATH" — this is critical. Without it, your terminal will not find Python. After installation, open Command Prompt and type python --version to confirm it shows Python 3.x.x.

You need four contract addresses from your chain's block explorer. The token address is your token contract. The USDC address is the stablecoin paired with your token on that chain. The pool address is the specific Uniswap V3 pool holding your token/USDC pair. The router address is the Uniswap router — find it by locating any recent successful swap on your token and checking which contract that transaction interacted with. Copy every address directly from the explorer — never type them manually. A single wrong character causes either a failed transaction or funds sent somewhere wrong.

You do not need to write any code yourself. The entire bot can be generated in under five minutes using Claude, Anthropic's AI assistant. Go to claude.ai, start a new conversation, and paste the following prompt exactly as written.

This first prompt builds the complete bot:

Build me a Python Uniswap V3 volume bot. I need four files: bot.py, config.py, requirements.txt, and .env.example. The bot must: connect to any EVM chain via RPC URL; load all settings from a .env file using python-dotenv; support wallet auth via either a 12-word MNEMONIC or a raw PRIVATE_KEY (not both simultaneously); execute random buy or sell swaps on a Uniswap V3 pool between TRADE_MIN_USD and TRADE_MAX_USD dollar amounts; wait a random number of seconds between INTERVAL_MIN_SEC and INTERVAL_MAX_SEC after each trade; enforce a hard daily gross buy spend cap of DAILY_SPEND_LIMIT_USD that resets at UTC midnight; include a DRY_RUN mode that simulates everything without sending real transactions; log every event with a UTC timestamp, direction, dollar amount, estimated token quantity, current price, and wallet balances; gracefully handle not enough token balance by switching to a buy, and not enough USDC by switching to a sell; stop trading and log a warning if ETH balance drops below MIN_ETH_FOR_GAS; print a daily summary showing total spent and total gained. Use web3.py for all blockchain interactions. Include full comments in the code explaining each section.

Claude will output all four files. Create a folder on your computer — for example C:\trading-bot — and save each file there with its exact name. Do not rename them.

If the bot generates any errors when you first run it, paste the error message back into the same Claude conversation and ask it to fix the issue. Claude will diagnose the problem and give you an updated file. This iterative approach — run, paste error, get fix — typically resolves any environment-specific issues within two or three exchanges.

For chain-specific issues such as ABI errors or router incompatibilities, use this follow-up prompt:

The bot is running on [your chain name, e.g. Doma OP Stack L2]. The Uniswap V3 router address is [paste your router address]. I am getting this error: [paste the exact error message]. Please fix the bot.py file to resolve this.

Replace the text in square brackets with your actual details before sending. Always paste the complete error message — the line number and error type are what Claude needs to diagnose the problem accurately.

Once Claude has generated your four files and you have saved them into your bot folder, the rest of setup is configuration only — no more code needed.

Open Command Prompt, navigate to your bot folder, and copy the example config file to create your real one. Open the new .env file in any text editor — Notepad works fine. Fill in your wallet credentials using either your 12-word seed phrase or your raw private key, but not both. Comment out whichever you are not using by adding a hash symbol at the start of that line.

Fill in your RPC URL (the blockchain node endpoint for your chain), your chain ID, and all four contract addresses. Set your trade minimum and maximum in USD, your interval range in seconds, your slippage tolerance, and your daily cap. Leave DRY_RUN set to true for now — you will change this only after confirming everything works correctly.

Once the config file is saved, install the Python libraries the bot needs. In Command Prompt in your bot folder, run pip install followed by -r requirements.txt. A large amount of text scrolls past as the libraries download — this is normal and takes about a minute. If pip is not found, try the alternative form: python -m pip install -r requirements.txt.

With DRY_RUN still set to true, start the bot by running python bot.py in your Command Prompt. The bot will connect to the chain, read your wallet balance, and begin simulating trades without spending real money.

The output shows the chain it connected to, your wallet address, and a warning confirming dry run mode is active. Every cycle prints the proposed trade direction, the dollar amount, the estimated token quantity, and the current price from the pool. After each simulated trade, it shows how long it will wait before the next one.

Watch for several things. The wallet address in the output should match your bot wallet exactly — character for character. The price shown should match what you see on the token's chart page on the block explorer. The trade amounts should fall within your configured minimum and maximum. The intervals should vary randomly within your range.

Run at least ten full cycles without errors before considering going live. If the price is wrong, your pool address is incorrect. If the wallet address is wrong, your credentials are misconfigured. If swaps say "execution reverted" even in dry run, your router address is wrong.

When everything looks correct, open your .env file, change DRY_RUN=true to DRY_RUN=false, save the file, and start the bot again. The very first live trade will include an approval transaction — a one-time step authorising the router to spend your USDC. After that, every trade executes directly. To stop the bot at any time, press Ctrl+C in the terminal window.

TRADE_MIN_USD and TRADE_MAX_USD control the size of each individual swap. Starting at $0.10 to $0.30 is conservative and appropriate for thin markets. Each trade will be a random amount within this range. Candles of this size on a chart look like a real small-cap trader rather than mechanical activity.

INTERVAL_MIN_SEC and INTERVAL_MAX_SEC set the wait time between trades in seconds. A range of 60 to 300 seconds means the bot trades at most once per minute and sometimes waits up to five minutes. This produces roughly 12 to 60 trades per day — enough to show consistent chart activity without being obviously automated.

DAILY_SPEND_LIMIT_USD is the hard cap on gross USDC spent buying per UTC day. Ten dollars is a good starting point. Once this is hit, the bot stops trading and waits until midnight.

SLIPPAGE_PERCENT is the maximum price movement you will tolerate per swap. Two percent is standard. On very thin markets, you may need to raise this to 3 or 5 percent to avoid constant transaction failures as price moves during confirmation.

MIN_ETH_FOR_GAS sets a floor below which the bot will not trade — preserving enough gas for you to manually withdraw funds if needed. The default of 0.001 ETH is a sensible minimum.

On day one, the chart transitions from flat lines to consistent green and red candles. Volume numbers tick up. The token appears on activity feeds and token explorers as an active market. This is the primary outcome — the chart looks alive to any new visitor.

By days two and three, if the token has any organic discovery happening through social media, search, or the chain's explorer, the active chart makes potential buyers significantly more likely to act. A live chart removes the main objection — "is this abandoned?" — before it even forms.

Over time, when real external buyers discover and purchase the token, they absorb the bot's accumulated sell-side at market price. If the bot bought those tokens earlier in the session at a slightly lower price, it earns the spread minus fees. This is not the goal, but it is a genuine side effect that can reduce or even eliminate net cost on active days.

The bot runs indefinitely until stopped or the wallet balance runs out. With a $10 daily cap and $50 in the wallet, it can operate for at least a week without attention. Top up USDC when it gets low. The native gas token balance barely moves on low-fee chains.

Volume activity cannot create genuine demand where none exists. If the token has no community, no utility, and no marketing, the bot will run at its fee cost indefinitely without attracting external buyers. Volume is a prerequisite for discovery — it is not a substitute for the underlying project.

The bot prints a timestamped line for every significant event. Knowing what each message means lets you confirm it is working correctly or diagnose a problem quickly.

The connected line confirms the chain ID and RPC endpoint. The wallet line shows the address being used — verify this matches your bot wallet. The DRY RUN MODE warning confirms simulation is active when applicable. Each trade line shows the direction, the dollar amount, the estimated token quantity, and the price at execution time.

When a confirmed transaction goes through, the output shows "confirmed" alongside the transaction hash. You can paste that hash into the block explorer to verify the swap happened on-chain. Balance lines show your current ETH, USDC, and token holdings after each trade.

The "daily cap hit" message means gross buying has reached your limit for the day. The bot is pausing until UTC midnight, not crashing. The "ETH too low for gas" message means you need to bridge more native token to the bot wallet. The "Today: spent=X gained=Y" summary at the end of each session shows your net position for the day.

Swaps fail with "execution reverted" when your router address is wrong. Every EVM chain deploys its own Uniswap V3 router contract at a unique address. Find the correct one by locating any recent successful swap on your token in the block explorer and checking which contract that transaction interacted with.

A "non-hexadecimal digit found" error means your wallet credentials are misconfigured. If using a seed phrase, confirm the PRIVATE_KEY line in your .env file is commented out with a hash symbol at the start. The two credential types cannot coexist in the active config.

If you funded the bot wallet with ETH but the logs still show "ETH too low for gas," you likely sent ETH on the wrong network. ETH sent on Ethereum mainnet does not appear on Base, Arbitrum, or a custom chain automatically. Use the chain's official bridge to move ETH from mainnet to your target chain.

If the price in the logs does not match the chart, your pool address points to the wrong contract. Each token and stablecoin pair creates a separate pool contract. Verify by finding a recent swap transaction, clicking into the event log, and confirming which pool contract emitted the Swap event.