> 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/create-launch/funding.md).

# Funding

Your launch uses a funder to distribute SOL to all wallets in your plan.

<div align="left"><figure><img src="/files/8sZMovkuCUjZkZCA1YBO" alt="" width="563"><figcaption></figcaption></figure></div>

The Funding Wallet section displays :

* The active funder name and address
* Current balance and amount required to launch

From here you can :

* **Switch funder** : Click the funder name to select a different one from your list
* **Create a fresh wallet** : Generate a new funder dedicated to this launch
* **Deposit** : Add SOL directly to the selected funder
* **Withdraw** : Withdraw SOL from this launch (not funder-specific)

When you click Distribute, the funder sends SOL to every wallet in your launch plan according to their configured allocation.

{% hint style="info" %}
&#x20;The launch cannot proceed until the funder balance meets or exceeds the required amount.
{% endhint %}

[Funder](/funder/funder.md) : Learn how to create and manage your funders

***

### Token Buy %

For each wallet, you can manually edit the % of supply it will buy. Click the ✏️ icon and enter the value (e.g. 0.25%, 0.18%).

<div align="left"><figure><img src="/files/porr6MfI9bycHSIhyRCB" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
Changing the % for any wallet will directly affect the total SOL required for funding.
{% endhint %}

### Sniper Guard

Sniper Guard monitors external buy activity during launch execution. When external purchases exceed a defined SOL threshold, Proxima automatically triggers the selected action.

<div align="left"><figure><img src="/files/HiKssGxmQ7c9MBy8UcwE" alt="" width="563"><figcaption></figcaption></figure></div>

* Tracks total SOL bought by external wallets during execution
* Triggers automatically when the threshold is exceeded
* Can stop further buying or exit the position entirely
* Optional developer wallet exclusion and address whitelisting

[Sniper Guard](/create-launch/funding/sniper-guard.md) : Full configuration details

***

### Auto-Sell

<div align="left"><figure><img src="/files/4vubvodsVOAMVa2bK52q" alt="" width="563"><figcaption></figcaption></figure></div>

Define automated sell strategies directly from this page.

* Add an Auto-Sell plan from the panel
* Plans are linked to the wallets used in this launch
* Execution starts automatically once conditions are met

[Auto-Sell](/live-settings/auto-sell.md) : Full configuration details

***

### DEV Wallet Controls

The developer wallet has additional controls :

<div align="left"><figure><img src="/files/LFZmb5L8u9g0ZmwOzPPi" alt="" width="563"><figcaption></figcaption></figure></div>

* **View Private Key**: Temporarily reveal the private key
* **Edit**: Replace the DEV private key with another one

{% hint style="info" %}
This allows you to swap developer wallets without recreating the launch.
{% endhint %}

***

### Import to Wallets

If a wallet in your launch is fresh and not yet part of your wallet list, you can add it.

<div align="left"><figure><img src="/files/E3BbXca3qc4Tj3g0mEiX" alt="" width="563"><figcaption></figcaption></figure></div>

* Click **Add** to include it in your wallet list
* Once added, it can be funded and used like any other wallet

[Overview](/wallets/overview.md) : Learn more about wallet management

***

### Withdraw

Withdraw SOL from your launch wallets at any point.

<div align="left"><figure><img src="/files/xu4rw3EoqDqGcpAlENKl" alt="" width="563"><figcaption></figcaption></figure></div>

[Withdraw](/live-settings/withdraw.md): Full documentation on withdraw modes, bookmarks, leave dust, and advanced settings

***

### Distribute Funds

Once the funder balance meets the required amount, click **Distribute** to allocate SOL to all wallets in your plan.

{% hint style="info" %}
Distribution is required before launching.
{% endhint %}

#### USD1 Conversion

If your launch uses USD1 as the base currency, an additional conversion step is required between distribution and launch.

<div align="left"><figure><img src="/files/acpfTc3OJeWhpDxt7VGB" alt="" width="563"><figcaption></figcaption></figure></div>

#### CEX Funding Distribution

If CEX Funding was enabled in Launch Settings, the distribution step opens a provider selection modal.

<div align="left"><figure><img src="/files/UAVISLfGkCebdrmzKoU0" alt="" width="563"><figcaption></figcaption></figure></div>

**Select a Provider**

Choose between available providers (SplitNow, Husher). Each provider has its own list of supported CEXs.

**Select CEXs**

Each CEX displays its minimum SOL requirement. You can:

* Select All to use every available CEX
* Pick specific CEXs based on their minimum amounts
* Deselect CEXs that don't fit your requirements

Click **Distribute** to start funding through the selected CEXs.

{% hint style="info" %}
Service fees vary from 1% to 2% depending on the provider.
{% endhint %}

***


---

# 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/create-launch/funding.md?ask=<question>&goal=<endgoal>
```

`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.