> For the complete documentation index, see [llms.txt](https://litepaper.burnify.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.burnify.app/overview/fair-launch-meaning.md).

# Fair Launch meaning

The Burnify project's team members would not possess privileged access to the token distribution, thereby ensuring a level playing field for all participants. We consider that the following elements would set the $BFY token distribution apart:

<mark style="color:blue;">**No Private Sale.**</mark> The $BFY tokens are not subject to any private sale.

<mark style="color:blue;">**No Marketing Allocation.**</mark> There would be no allocation of $BFY tokens for marketing purposes.

<mark style="color:blue;">**No Team Allocation.**</mark> The team members of Burnify would have no allocation of $BFY tokens.

<mark style="color:blue;">**No Treasury Allocation.**</mark> There would be no allocation of $BFY tokens to a treasury.

Central to our **Fair Launch Philosophy** is the **Proof of Burn Mechanism.** Proof of Burn is a fundamental principle where new $BFY tokens are generated only when existing tokens are burned. This process ties the creation of new tokens directly to the active participation of users in reducing the overall token supply.&#x20;

* By requiring users to burn tokens to receive new $BFY tokens, the supply of $BFY is intrinsically linked to community engagement.
* Every burn transaction is recorded on the blockchain, providing clear and verifiable proof of burn.
* As new $BFY tokens are minted based on the number of tokens burned, all participants have an equal opportunity to earn rewards proportional to their contributions.


---

# 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://litepaper.burnify.app/overview/fair-launch-meaning.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.