> For the complete documentation index, see [llms.txt](https://docs.astro.meme/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.astro.meme/protocol/fair-mint.md).

# Fair Mint

Fair Mint is Astro's fixed-price launch system. Creators choose between an 80 OKB configuration and an 800 OKB configuration.

## Fixed launch structure

Each token has a total supply of **1,000,000,000 tokens**:

* **800,000,000 tokens (80%)** are divided into public mint shares.
* **200,000,000 tokens (20%)** are reserved for Uniswap V3 liquidity.

Every share costs **0.1 OKB**. The number of shares and tokens per share depend on the selected configuration:

|                      | 80 OKB Mode | 800 OKB Mode |
| -------------------- | ----------- | ------------ |
| Shares               | 800         | 8,000        |
| Tokens per share     | 1,000,000   | 100,000      |
| Mint price per share | 0.1 OKB     | 0.1 OKB      |
| Public allocation    | 800,000,000 | 800,000,000  |
| Fundraising target   | 80 OKB      | 800 OKB      |
| Mint window          | 24 hours    | 72 hours     |

## Why a fixed price?

Within the selected configuration, all participants receive the same number of tokens for the same OKB amount. The price does not rise with mint progress, and neither configuration uses a bonding curve.

Creators participate under the same public mint rules. Astro does not reserve a separate team or creator allocation within the fixed 80/20 supply structure.

## Launch lifecycle

| Stage      | What happens                                                                                        |
| ---------- | --------------------------------------------------------------------------------------------------- |
| Created    | The token contract and launch parameters are deployed.                                              |
| Minting    | Users mint shares at 0.1 OKB each. Tokens are delivered to their wallets.                           |
| Successful | Every share is minted and the selected 80 or 800 OKB target is reached.                             |
| Finalized  | Minting and refunds close, and the liquidity position is created.                                   |
| Listed     | The token can trade against OKB or the selected RWA asset.                                          |
| Failed     | The selected 24-hour or 72-hour window ends below its target; the launch does not create liquidity. |

## Before finalization

Minted tokens can be returned through the refund mechanism before finalization. The corresponding tokens are burned and the original mint payment is returned, excluding gas.

Refunds reduce both the number of completed shares and the amount raised.

## After finalization

Finalization is the irreversible transition from Fair Mint to open-market trading:

* New minting stops.
* Fair Mint refunds stop.
* The reserved 20% token allocation is deployed to liquidity.
* The raised assets are committed to the Uniswap V3 liquidity position.

After this point, users buy or sell through the market and are exposed to price movement, liquidity depth, slippage and trading fees.

> The fixed mint price applies only during Fair Mint. It does not guarantee a future market price or a loss-free exit after finalization.


---

# 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.astro.meme/protocol/fair-mint.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.