> 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/omen-listed/submission-and-review-process.md).

# Submission & Review Process

The OMEN Listed submission and review process.

This page explains how to submit a project to OMEN Listed and understand the payment and review process.

### 1. Project Details

Visit the [OMEN Listed page](https://app.omenprotocol.live/omen-listing) to access the submission form.

Prepare the following information before applying.

**1. Project Name:** The name of your project.

**2. Token Ticker:** The token symbol.

**3. Contract Address:** The token contract address.

**4. Network:** The blockchain network where your token is deployed.

**5. GeckoTerminal Pool URL:** The GeckoTerminal pool link for your token.

**6. Website (Optional):** The official project website.

**7. X (Optional):** The project's official X account.

**8. Telegram (Optional):** The project's Telegram community.

**9. Project Description:** A brief explanation of your project and its purpose.

### 2. Submission Payment

The submission fee is **30 USDG**.

Follow the payment instructions provided on the OMEN Listed page. Verify the accepted network, USDG token contract, and recipient address before sending payment.

### 3. Transaction Hash Submission

After completing the payment, enter your transaction hash (TX hash) in the submission form.

The transaction must be verifiable on the relevant blockchain. Providing a transaction hash alone does not confirm successful payment.

### 4. Payment Verification and Review

**1. Payment Verification:** The submitted transaction is checked against the relevant blockchain.

**2. Project Review:** The team reviews the submitted project information.

**3. Final Decision:** The project receives an approval or rejection decision.

### 5. Approval and Rejection

**Approved:** Projects that pass the review may be added to OMEN Listed and receive an OMEN Listed badge, subject to the program's listing rules.

**Rejected:** Rejected projects are intended to receive a refund of the 30 USDG submission fee to the wallet address that made the payment, according to the official refund procedure.

### Important Notes

**1.** Payment does not guarantee approval.

**2.** Ensure all project information and transaction details are accurate.

**3.** Never share your wallet's private key or recovery phrase.

**4.** An OMEN Listed badge does not guarantee a project's security, legitimacy, performance, or investment potential.

**Availability:** Submission, payment verification, review, and refund procedures are subject to official launch and confirmation by OMEN Protocol.


---

# 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/omen-listed/submission-and-review-process.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.