> For the complete documentation index, see [llms.txt](https://docs.proxima.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxima.tools/other/best-practices.md).
# Best Practices
***
#### 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](/live-settings/withdraw.md#leave-dust) To leave at least 0.1 SOL on each wallet used.
{% endhint %}
**Funding Rules**
1. Fund each wallet at least **30 minutes apart** from the others to avoid being linked together
2. Fund all wallets at least **24h** before launch, using [CEX FUNDING](/wallets/funding.md#cex-funding)
3. Always leave **0.1 SOL** minimum when withdrawing : never fully drain with [Leave Dust](/live-settings/withdraw.md#leave-dust)
4. 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. Proxima'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](/create-launch/launch-settings.md)
***
#### 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](/live-settings/cleanup.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.proxima.tools/other/best-practices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.