> For the complete documentation index, see [llms.txt](https://docs.souless.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.souless.fun/launching/launch-guard.md).

# Launch Guard

> **Availability: ARC MAINNET + TESTNET**

Launch Guard is the short opening phase before normal trading. It gives the creator a priority commitment and batches public commitments so participants do not race through ordinary swaps at the first moment.

## Published V1 rules

| Rule                     |                                                Contract value |
| ------------------------ | ------------------------------------------------------------: |
| Opening duration         |                                                    60 seconds |
| Minimum commitment       |                                                       10 USDC |
| Opening fee              |                                       0.10% of committed USDC |
| Finalization grace       |                                      30 seconds after opening |
| Contract participant cap |                                                  64 addresses |
| Cancellation delay       |                 30 minutes, only on the defined recovery path |
| Public wallet cap        |    83 USDC in the current Arc Mainnet and Testnet deployments |
| Creator cap              | 126.9 USDC in the current Arc Mainnet and Testnet deployments |

Deployment and UI limits can be lower than contract maxima. Always use the launch-specific values shown before signing.

## Lifecycle

```
CREATED ──→ OPENING ──→ FINALIZING ──→ LIVE
                │              │
          60 seconds           └──→ RECOVERY ──→ FINALIZING
                                      │
                                      └──→ CANCELLED (when eligible)
```

The product may display friendlier names, but the economic sequence is the same.

## Commitments and allocation

Participants deposit USDC during the opening. Finalization deducts the explicit Opening fee, creates the market, and executes the opening amounts against the same initialized pool. Minimum-token protections apply. Allocation comes from settlement output—not from arrival position inside the accepted batch.

For Community-enabled launches, finalization also activates the Creator/Community allocation and Staking/InfoFi split chosen at launch as the market's starting Community policy. See [Launch a token](/launching/launch-a-token.md).

## Finalization and fallback

Souless can finalize immediately after the opening. If finalization is delayed, anyone can call the same path after the 30-second grace period. This prevents a launch from depending permanently on one service.

If settlement cannot safely satisfy the launch terms, it must not silently change them. The defined recovery or delayed cancellation path applies. Refund behavior depends on the recorded terminal state; users should use the Souless claim/refund view rather than resubmitting arbitrary calls.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.souless.fun/launching/launch-guard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
