> 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/launch-settings/multilaunch.md).

# MultiLaunch

{% hint style="info" %}
MultiLaunch is currently only available in Beta on Pons with Block-0 execution.
{% endhint %}

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

***

### How it works

Select the number of launch attempts.

<div align="left"><figure><img src="/files/unx5I3fiU4oK0JDIgZRC" alt="" width="375"><figcaption></figcaption></figure></div>

Provide at least the same number of **MEV** and **Holder** wallets.

<div align="left"><figure><img src="/files/jB8MgmDe3fJ7KOo7ktwB" alt="" width="375"><figcaption></figcaption></figure></div>

All attempts are launched simultaneously. Once one captures the configured supply, all others instantly sell their Dev positions and are nuked. If none succeed, every Dev position is sold immediately, limiting losses to the initial Dev buy.

<div align="left"><figure><img src="/files/qm3fs3KZ41E7ZrgVLQOe" alt="" width="274"><figcaption></figcaption></figure></div>

### Why use MultiLaunch?

Robinhood launches can be highly competitive.

Instead of relying on a single deployment, MultiLaunch sends multiple identical launches at the same time. If one attempt is sniped, another can still successfully capture the supply.

### Example

You launch **5 attempts**.

* Attempt #3 captures the supply.
* Attempt #3 becomes **Live**.
* Attempts #1, #2, #4 and #5 instantly sell their Dev positions and are **Nuked**.

This significantly improves your chances of winning highly contested launches while minimizing losses on unsuccessful attempts.


---

# 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/launch-settings/multilaunch.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.