> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/token-and-ecosystem/tokenomics.md).

# Tokenomics

Explore the $OMEN token supply, distribution, launch allocation, and developer token lock.

OMEN Protocol ($OMEN) is the token associated with the OMEN ecosystem.

### Token Information

**Token Name:** OMEN Protocol

**Token Symbol:** $OMEN

**Total Supply:** 1,000,000,000 OMEN

**Launch Platform:** PONS Launchpad

**Network:** Robinhood Chain

### Token Distribution

The total supply of 1 billion OMEN is allocated as follows:

#### PONS Launchpad Allocation

**Allocation: 95% — 950,000,000 OMEN**

The PONS Launchpad allocation represents 95% of the total token supply.

#### Developer Allocation

**Allocation: 5% — 50,000,000 OMEN**

The developer allocation represents 5% of the total token supply. The developer allocation was intended to be locked after launch.

### Allocation Breakdown

| Allocation       | Percentage | Amount                 |
| ---------------- | ---------- | ---------------------- |
| PONS Launchpad   | 95%        | 950,000,000 OMEN       |
| Developer        | 5%         | 50,000,000 OMEN        |
| **Total Supply** | **100%**   | **1,000,000,000 OMEN** |

### Developer Token Lock

The developer allocation was intended to be locked after launch. The lock status and mechanism should be verified using the relevant onchain records before being presented as confirmed.

### Transparency

OMEN Protocol aims to maintain transparency regarding its token supply and distribution. Users should refer to official project information and verifiable onchain records when checking allocation and token-lock status.


---

# 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://omen-protocol.gitbook.io/omen-protocol-docs/token-and-ecosystem/tokenomics.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.