> For the complete documentation index, see [llms.txt](https://launchium.gitbook.io/launchium/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://launchium.gitbook.io/launchium/presale-system.md).

# Presale System

#### LNCHM Token Presale Details

**Presale Period**: July 4, 2025 20:00 UTC - July 9, 2025 20:00 UTC

**Key Information:**

* **Hard Cap**: $50,000
* **Soft Cap**: $15,000
* **Minimum Purchase**: 0.5 SOL
* **Maximum Purchase**: No limit
* **Accepted Currency**: SOL only
* **At Launch:** 100% unlock at TGE

**Timeline:**

* July 4-9: Presale period
* July 9-10: Token calculation and distribution
* July 10, 20:00 UTC: Raydium listing

#### How to Participate

1. **Via Website**

   ```
   Visit launchium.app/presale → Connect wallet → Enter SOL amount → Confirm transaction
   ```
2. **Via Telegram**

   ```
   Join @launchium → Use /presale command → Follow bot instructions
   ```
3. **Via Twitter**

   ```
   Follow @launchium → Check pinned presale tweet → Click presale link
   ```

#### Token Distribution

Token distribution will occur automatically within 24 hours after presale ends. Tokens will be sent directly to the wallet address used during purchase.


---

# 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://launchium.gitbook.io/launchium/presale-system.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.