Solana Bot Wallet Setup

Why Wallet Architecture Matters

When running a volume bot, you are not just using one wallet. You need multiple wallets that each appear as independent traders on the blockchain. If all your volume comes from a single wallet doing rapid buy-sell cycles, it is immediately obvious to anyone checking the token's trade history that the activity is automated. Multiple unique wallets create the appearance of diverse market participation.

The boss/worker architecture solves this by separating the roles of fund management and trade execution. One boss wallet holds your capital and manages distribution. Multiple worker wallets each execute independent trading cycles. On the blockchain, each worker appears as a separate trader.

The Boss/Worker Architecture

Your External Wallet | v (fund) [BOSS WALLET] ---- Main fund holder | | | | v v v v (distribute) [W1] [W2] [W3] [W4] ... [Wn] Worker wallets | | | | v v v v (trade) Buy/Sell cycles on pump.fun | | | | v v v v (gather) [BOSS WALLET] ---- Reclaim funds

Boss Wallet

The boss wallet is the central treasury. It holds the bulk of your SOL and has two main functions:

Distribute: Send SOL to worker wallets in equal or custom amounts so they have funds to trade with.
Gather: Reclaim remaining SOL from all worker wallets back to the boss wallet after a campaign ends.

The boss wallet itself never trades. It only sends and receives SOL from workers. This keeps your main funds isolated from trading activity.

Worker Wallets

Worker wallets are the trade executors. Each worker is an independent Solana keypair that executes buy-sell cycles against the target token. Key properties:

Each has a unique public address, appearing as a separate trader on-chain
Workers only hold the SOL they need for their current trading session
If a worker is compromised, only that worker's small balance is at risk
Workers can be created and destroyed as needed

Unique wallet advantage: On BirdEye and DexScreener, each worker's trades show up as activity from a different wallet address. This makes the volume look like it comes from multiple independent traders, which is much more convincing than a single wallet doing hundreds of transactions.

Step-by-Step Wallet Setup

Here is how to set up the boss/worker wallet system for Vol Bot:

1

Create the Boss Wallet

In Vol Bot, navigate to the wallet management section and create a new boss wallet. This generates a new Solana keypair. The private key is immediately encrypted with AES-256-GCM and stored in data/wallets.enc. Write down the public address to send SOL to it.

2

Fund the Boss Wallet

Send SOL from your personal wallet (Phantom, Solflare, etc.) to the boss wallet address. Send the total amount you want to use for your campaign, plus a small buffer for transaction fees. For example, if you plan to distribute 1 SOL each to 10 workers, send at least 10.1 SOL to cover distribution transaction fees.

3

Create Worker Wallets

Create the number of worker wallets you need. Each worker generates a new keypair, also encrypted and stored alongside the boss wallet. For most campaigns, 10-30 workers provides a good balance of diversity and manageability. The Degen tier supports up to 999 workers for maximum scale.

4

Distribute SOL to Workers

Use the "distribute" command to send SOL from the boss wallet to each worker. You can distribute equally (split total evenly) or set custom amounts per worker. Each worker needs at minimum 0.01 SOL to execute micro-trades, but 0.5-2 SOL per worker is recommended for sustained campaigns.

5

Start Volume Generation

Configure your target token, strategy, and trade size, then start the volume engine. Each worker begins executing independent buy-sell cycles using its own funded wallet. Monitor progress through the dashboard.

6

Gather Funds When Done

After your campaign ends, use the "gather" command to pull all remaining SOL from worker wallets back to the boss wallet. From there, you can withdraw back to your personal wallet. The gather function reclaims everything including the rent-exempt minimum from each worker account.

Funding Calculations

How much SOL to allocate per worker depends on your campaign goals:

Campaign Type	Workers	SOL per Worker	Total SOL Needed	Expected Volume
Quick test	3-5	0.1 SOL	~0.5 SOL	~20 SOL
Short burst	10	0.5 SOL	~6 SOL	~250 SOL
Standard campaign	10-20	2 SOL	~25-45 SOL	~1,000-2,000 SOL
Heavy volume push	30	5 SOL	~155 SOL	~7,000 SOL
Maximum scale	100+	2-10 SOL	~500+ SOL	~20,000+ SOL

Rent-exempt minimum: Every Solana account must hold a minimum balance (~0.002 SOL) to remain on-chain. This is automatically handled by Vol Bot. When you gather funds, the gather function closes worker accounts to reclaim this rent deposit. It is not lost, just temporarily locked while the worker is active.

Security Best Practices

Your wallet security directly determines the safety of your funds. Follow these practices to minimize risk:

Encrypted Storage

Vol Bot stores all private keys in an encrypted file (data/wallets.enc) using AES-256-GCM encryption. The encryption password is set during initial setup. Without this password, the wallet file is unreadable. Choose a strong, unique password and store it securely (password manager, not a text file on the same server).

Isolate Bot Funds

Never use your main personal wallet as the boss wallet. Create a dedicated wallet for bot operations and only fund it with the amount you plan to use. If anything goes wrong, your personal holdings remain safe. Think of bot funds as capital deployed to a specific purpose, separate from your holdings.

Limit Worker Balances

Only distribute the SOL workers actually need. If each worker needs 1 SOL for a 4-hour campaign, do not send them 10 SOL each. Smaller worker balances mean smaller losses if any individual worker keypair is somehow compromised.

VPS Security

Since the bot runs on your VPS, your server security is critical:

SSH key authentication only — disable password-based SSH login
Firewall — only open the ports you actually need (SSH, bot dashboard)
Keep software updated — run apt update && apt upgrade regularly
Non-root user — run the bot as a non-root user when possible
Fail2ban — install fail2ban to block repeated failed SSH attempts

Never expose private keys. Do not log, print, or transmit wallet private keys. Never store them in plain text, in environment variables, or in code repositories. Vol Bot's encrypted storage is designed to prevent key exposure. If you suspect your server has been compromised, immediately gather all funds to the boss wallet and withdraw to an external wallet.

Backup Your Wallet File

The data/wallets.enc file contains all your wallet keypairs. If this file is lost or corrupted and you do not have a backup, your funds are permanently inaccessible. Keep an encrypted backup of this file in a separate location (encrypted cloud storage, separate drive). Remember to also backup your encryption password.

Common Issues and Solutions

"Insufficient balance" errors: Workers need enough SOL for both the trade amount and the transaction fee. If a worker has exactly 0.001 SOL, it cannot execute a 0.001 SOL trade because it also needs ~0.000005 SOL for the Solana transaction fee. Always distribute slightly more than the bare minimum.
Workers showing 0 balance after creation: New workers start with 0 SOL. You must distribute funds from the boss wallet before they can trade. Creating a worker only generates the keypair; it does not fund it.
Gather not reclaiming all SOL: If workers hold token balances (tokens bought but not yet sold), the gather function only reclaims SOL, not tokens. Make sure all trading cycles are complete (all positions closed) before gathering. Run a "sell all" command first if needed.
"Account does not exist" errors: If a worker wallet has never received SOL, it does not exist on-chain. The first distribution transaction creates the account. This is normal Solana behavior.