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

# The LiquidOps Fair Launch

### What is an AO fair launch?

Via the decentralized funding network, The Permaweb Index, users in the AO/Arweave ecosystem can delegate AO yield that is currently being earned on AR tokens towards ecosystem fair launches.

In exchange they get back the project's token, without transferring their underlying AR tokens and the project receives AO/PI through the Permaweb Index.

In short, the AO/Arweave communities receive LQD and LiquidOps receives decentralised funding.

### LQD Tokenomics

[LQD](/protocol-mechanics/the-lqd-token.md), the native token of LiquidOps has a maximum supply of 50,000,000 tokens, distributed as follows:

**28% DAO**

* 23% allocated to the protocol treasury.
* 5% allocated to oToken reserves.
* Both governed by token holder-led governance, ensuring community control.

**25% Liquidity Mining**

* Used to incentivise protocol usage and distribute tokens to active users.
* Helps bootstrap liquidity and network activity.

**15% AO Fair Launch 1**

* Portion of token supply allocated to our first AO fair launch.

**15% Founders & Future Contributors**

* 8% set aside for current founders and team members.
* 7% reserved for future contributors to the protocol.

**10% Foundation**

* Portion of tokens allocated to the foundation, to be used for ecosystem grants, audits, developer tooling and protocol infrastructure.

**7% Private Token Sales**

* Allocated in prior rounds: 2 private sales, 1 incubator round, and 1 pre-seed round.
* Supported by 8 angels and 0 VC’s.

### How to delegate AO to the LQD fair launch

1. Head to[ https://ao.arweave.net/#/delegate/](https://t.co/FrDrVdD5gR)
2. Connect your Arweave/AO wallet
3. Delegate your AO yield to LiquidOps (LQD)
4. Confirm your delegation preferences
5. Start earning LQD!

LQD tokens will remain locked until Mainnet Beta is over and LiquidOps enters Mainnet.

*Token address:* [n2MhPK0O3yEvY2zW73sqcmWqDktJxAifJDrri4qireI](https://aoscan.arweave.dev/#/process/n2MhPK0O3yEvY2zW73sqcmWqDktJxAifJDrri4qireI)

*Fair launch address:* [N0L1lUC-35wgyXK31psEHRjySjQMWPs\_vHtTas5BJa8](https://aoscan.arweave.dev/#/process/N0L1lUC-35wgyXK31psEHRjySjQMWPs_vHtTas5BJa8)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.liquidops.io/protocol-mechanics/the-liquidops-fair-launch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
