Best Practices
Pre-launch and launch-time configuration that keeps wallets and execution clean across scanners and bubble map tools.
Overview
A clean launch depends on two things : wallets that pass scanner checks (Axiom, Padre), and launch timing that does not produce visible clustering on bubble maps. Both are covered by a small set of rules applied before and during the launch.
- Funding : prepare wallets so they pass scanner checks before launch
- Execution : configure timing so wallets do not appear clustered on bubble maps
- Cleanup : recover during the launch if clustering is triggered
Funding Wallets
Wallets must be funded according to the criteria used by external scanners. The same funding workflow satisfies every check at once.
Fresh Wallets ( Axiom )
 Axiom flags wallets as fresh until 24 hours after their first funding
\ Fresh Wallets ( Padre )
Padre (Terminal) flags wallets as unfunded until they have held at least 0.1 SOL balance continuously for 2 Hours
\ Funding clustering : both scanners link wallets that are funded within a short window of each other, regardless of age
{% hint style="info" %} A complete withdrawal resets Padre's balance counter regardless of how old the wallet is. So you use Leave Dust To leave at least 0.1 SOL on each wallet used. {% endhint %}
Funding Rules
- Fund each wallet at least 30 minutes apart from the others to avoid being linked together
- Fund all wallets at least 24h before launch, using CEX FUNDING
- Always leave 0.1 SOL minimum when withdrawing : never fully drain with Leave Dust
- Keep the balance non-zero between funding and launch
{% hint style="warning" %} CEX Funding must be run from the Wallets page. Only that interface lets you set a delay between wallets without it, wallets funded in the same batch are linked together by scanners. Bundle's internal funding from the launch Funding page is safe to use and does not need this step. {% endhint %}
{% hint style="info" %} When these four rules are followed, no additional delay or extra funding step is required at distribute time. {% endhint %}
Bubble Map Configuration
Launch timing controls how wallets appear on bubble map tools. Tight timing produces visible clusters that expose coordinated wallets.
Presets
Two presets cover most launches and require no manual tuning :
- Stealth : default for standard launches
- Full Build : for full build configurations
Custom Configuration
If timing is configured manually, respect the following minimum values :
| Parameter | Minimum |
|---|---|
| Buy Delay | 16,000 |
| Front-to-Back | 800 |
| Back-to-temp ( if available ) | 800 |
{% hint style="info" %} Values below these thresholds significantly increase the chance of visible clustering on the bubble map. {% endhint %}
→ See Launch Settings for the configuration interface
Mid-Launch Cleanup
If wallet clusters trigger during a live launch, Cleanup breaks the pattern before it propagates across subsequent buys.
When a cluster appears mid-session, run Cleanup immediately. Acting early limits the chain reaction on the bubble map and keeps the rest of the session clean.
→ See Cleanup for the action details