> For the complete documentation index, see [llms.txt](https://help.trade.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.trade.fun/memecoins/multi-wallet-buy.md).

# Multi Wallet Buy

<figure><img src="/files/1jeefd21tUtPeWJndBlO" alt=""><figcaption><p>Multi Wallet Buy Feature</p></figcaption></figure>

<figure><img src="/files/Q4ERxUikcyza1Tujz6p6" alt="" width="375"><figcaption><p>Multi Wallet Buy Settings Tab</p></figcaption></figure>

{% tabs %}
{% tab title="Variance" %}
Randomizes each wallet's buy amount by up to the set percentage. This is applied to the already-split per-wallet amount. For example, at 20%, a wallet allocated 0.5 SOL may spend between 0.4–0.6 SOL.&#x20;

The result is always capped at the wallet's available balance. Set to 0% for exact amounts across all wallets.

> Variance makes each transaction look independent.
> {% endtab %}

{% tab title="Transaction Delay" %}

### Transaction Delay Mode

Toggle delay between transactions **On** or **Off**. When off, all wallets execute simultaneously.

***

Set the delay between each wallet's transaction, from **0ms to 1s**. A small delay staggers your buys so they don't all land in the same block.

> Multiple buys landing in the same block is easy to spot. A small delay spreads them out so each buy looks unrelated.
> {% endtab %}
> {% endtabs %}


---

# 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://help.trade.fun/memecoins/multi-wallet-buy.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.