Bundle Wallets Setup Guide — Complete Configuration for Pump.fun Launches

Bundle wallets are the foundation of every successful Pump.fun launch. Set them up correctly once and your launches will be consistently more profitable. This is the definitive setup guide.

What Are Bundle Wallets?

Bundle wallets are separate Solana keypairs used exclusively for buying your token in the same Jito bundle as the token creation. They're distinct from your dev wallet (creator) and snipe wallets. Each has a specific role in your launch strategy.

How Many Bundle Wallets?

Minimum: 2 bundle wallets (better than 0, limited supply control). Standard: 3-4 wallets (good supply control, manageable cost). Maximum per bundle: 3 wallets (Jito bundles max 5 transactions: 1 create + 1 dev buy + 3 bundle wallets). For more wallets, use snipe wallets beyond the bundle.

Generation Best Practices

Generate fresh wallets for each launch campaign. In SolBundler Dashboard → Wallets → Bundle → Generate. Set count to 3. These wallets are stored browser-side. Export private keys immediately and store securely.

Funding the Right Way

Use Fund Wallets for batch funding. Set individual amounts — not all wallets need the same amount. Wallet 1: Free, Wallet 2: 0.3 SOL, Wallet 3: 0.7 SOL. Variation looks organic. Always verify balances before launching.

Post-Launch Management

After selling all token positions, use Withdraw SOL to sweep SOL back to dev wallet. Delete old bundle wallets after withdrawal — accumulated wallets create clutter and security risk. Generate fresh wallets for your next launch.

What Are Bundle Wallets?

Bundle wallets are the multiple Solana wallet addresses that execute coordinated buy transactions as part of your Jito bundle at token launch. Unlike your main personal wallet, bundle wallets are created specifically for a single launch and retired afterward. Each bundle wallet independently holds SOL, executes a buy transaction in block 0, and holds the tokens it purchased until you decide to sell. Using multiple bundle wallets instead of one large buy is what creates the organic-looking holder distribution that passes Bubblemaps analysis.

Step 1: Generate Bundle Wallets in SolBundler

Navigate to the Wallets tab in your SolBundler dashboard. Select wallet type "Bundle" and set count to 10-20 depending on your supply control strategy. Click Generate — SolBundler creates cryptographically secure Solana key pairs and stores them encrypted in your Supabase account. Each generated wallet gets a label (Bundle #1, Bundle #2, etc.) and shows in your wallet list with its public address and current SOL balance. Generation takes less than 5 seconds regardless of wallet count.

Step 2: Calculate Funding Amount Per Wallet

Each bundle wallet needs exactly: your intended buy amount + 0.003 SOL for transaction fees. If you want each wallet to buy 0.15 SOL worth of tokens, fund each wallet with 0.153 SOL. Do not fund less — an underfunded wallet causes the entire bundle to fail. Do not fund significantly more than needed — excess SOL sits idle until you withdraw it post-launch. SolBundler shows a funding calculator in the deployment interface that computes exact amounts based on your planned buy amounts.

Step 3: Fund Wallets Using SolBundler's Fund Feature

In the Wallets tab, select all bundle wallets you plan to use. Click "Fund Wallets" and enter the amount per wallet. Connect your funding source wallet (Phantom or Solflare). SolBundler distributes SOL to all selected wallets in a single transaction from your connected wallet, saving time compared to manual transfers. After funding, click "Refresh Balances" to verify all wallets show the correct balance. Never proceed to launch until every wallet shows green with sufficient balance.

Step 4: Configure Buy Amounts in Bundle Settings

In the Bundle deployment interface, select your bundle wallets and set individual buy amounts. Best practice: vary amounts slightly between wallets — use 0.13, 0.15, 0.12, 0.16, 0.14 SOL rather than exactly 0.15 for every wallet. This variation makes the bundle look less automated on on-chain analysis tools. SolBundler lets you set individual amounts per wallet or use the uniform distribution option for speed. For maximum stealth, take 2 minutes to vary amounts manually.

Step 5: Post-Launch Wallet Management

After a successful launch, your bundle wallets hold tokens and remaining SOL. Post-launch workflow: use Smart Sell to exit token positions gradually across all wallets. After selling all tokens, use Withdraw to consolidate remaining SOL back to your main wallet. Close empty token accounts to recover rent deposits (approximately 0.002 SOL per wallet). Once withdrawn and closed, retire the wallets — don't reuse them for future launches. Generate fresh wallets for every new launch to maintain on-chain hygiene.

FAQ

How many bundle wallets is optimal? 10-15 wallets for standard launches, 18-20 for maximum distribution on large launches. Under 8 wallets creates visible clustering on Bubblemaps. Over 20 wallets approaches Jito bundle size limits and increases transaction fee costs without meaningful distribution benefit.

Can I reuse bundle wallets from a previous launch? Technically yes, but not recommended. Reused wallets have transaction history connecting them to previous launches, which on-chain analysts can use to identify you as a serial launcher. Fresh wallets per launch maintain maximum operational separation between your launches.

What if I forget to fund one wallet before launching? The entire bundle will fail if any wallet is underfunded. SolBundler checks wallet balances before allowing bundle submission and will warn you if any wallet has insufficient funds. The balance check is your safety net — always run it immediately before clicking Deploy.

Should I vary the number of bundle wallets between launches? Yes — using exactly 15 wallets every single launch creates a recognizable pattern. Vary between 10-20 wallets across launches. Combined with fresh wallet generation each time, this makes it much harder to link your launches together through on-chain pattern analysis.