# Liquidity Bootstrapping - Presales

Fullhouse has a dual-token model, with $YUUKI (main utility token) and $FH (governance token). To establish **initial on-chain liquidity** for FH trading, team has employed a presale with partners (launchpads) as well as on a open Public sale (linked below). We work with a range of launchpad partners to facilitate the momentum of the launch as well as host a portion on the website itself. Please note, partner sales have not begon for $FH token, beware of scams!\
\
The to be announced launchpad protocols involve gradually selling tokens in the Public round for a specified period, for a fixed price of 0.75$.  Leveraging the presales will provide FH with robust initial on-chain liquidity, enabling users and traders to purchase FH through a decentralized and permissionless approach. For a full list of token utilities, [view this page](/fullhouse.gg-whitepaper/platform-economy/token-utility-of-usdfh.md).

**Key Info:** 

* Start Date & Time: Live at [presale.fullhouse.gg](https://presale.fullhouse.gg)
* End Date & Time: Until sold out
* Chain: BNB
* Hardcap: 10,000,000 (ten million) USDC/USDT
* Available to Purchase with: USDC/USDT
* Vesting: Yes

<figure><img src="/files/aMqxeOblTc4p8viokrRC" alt="" width="188"><figcaption></figcaption></figure>

The FH token will initially be priced at $0.75, in order to participate in the sales it is wise to follow the Fullhouse twitter or discord announcements. Sales are all held for a fixed period of time.\
\
Token utilities can be found [here](/fullhouse.gg-whitepaper/platform-economy/token-utility-of-usdyuuki.md).


---

# Agent Instructions: 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:

```
GET https://bit-hotel.gitbook.io/fullhouse.gg-whitepaper/platform-economy/liquidity-bootstrapping-presales.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.