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

# 8.1  Round-by-Round Detail

#### Round 1 - Pre Seed Round (Highest Upside)

* Token Price: $0.004 per LQX
* Minimum Investment: $1,000 USDT
* Fundraise Target: $400,000 USDT
* This round is reserved for serious capital - highest bonus, lowest price, maximum upside

#### Round 2 - Seed Round

* Token Price: $0.007 per LQX
* Minimum Investment: There is no limit for minimum investment
* Activates automatically once Pre Seed Round target is reached

#### Round 3 - Presale

* Token Price: $0.011 per LQX
* Minimum Investment: There is no limit for minimum investment
* Open to broader community participation

#### Round 4 - Public Sale

* Token Price: $0.016 per LQX
* Bonus: None - final opportunity before public listing
* Minimum Investment: There is no limit for minimum investment
* Still represents a 36% discount to planned TGE price of $0.025

<br>


---

# 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://liquidx-3.gitbook.io/liquidx-whitepaper/8.-presale/8.1-round-by-round-detail.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.