# Public Sale

The Ocelex Public Sale is scheduled to begin on **December 9th at 10:00 UTC** and will run for 6**0 hours or until all tokens are sold**. This event will use a **Dutch auction format**, ensuring fair price discovery based on real market demand. Here’s everything you need to know about participating.

***

### How the Public Sale Works

* **Start Date:** December 9th, 2024, 10:00 UTC
* **Duration**: 60 Hours
* **Format:** Dutch Auction
* **Tokens for Sale:** 2,000,000 $OCX (2% of the total supply)
* **Raise Token:** USDC
* **Starting Price:** $0.30
* **Minimum Price:** $0.06

***

### What Is a Dutch Auction?

A Dutch auction begins with a high starting price that gradually decreases over time until all tokens are sold or the auction ends.

**Key Benefits:**

* **Fair Market Pricing:** Real demand sets the token price, minimizing speculative inflation.
* **Equal Pricing:** Regardless of purchase timing, everyone pays the same final price once the auction ends.
* **Anti-Bot Protection:** The dynamic pricing mechanism discourages bots from manipulating the auction.

***

### How the Price Drop Works

* The token price decreases every block throughout the auction’s 60-hour duration or until all tokens are sold.
* The decrease happens evenly and continuously, providing transparent and predictable price reductions.

***

### Maximum Raise Amount Adjusts with Price

As the token price drops, the maximum possible raise amount also decreases proportionally:

* Starting Price: $0.30 → Maximum Raise = $600,000
* Mid-Point Price: $0.15 → Maximum Raise = $300,000
* Minimum Price: $0.06 → Maximum Raise = $120,000

**Example:**

If 1,000,000 $OCX tokens are still available when the price reaches $0.10, the maximum amount that can be raised at that price is $100,000 ($0.10 x 1,000,000 tokens).

***

### How the Final Price Affects FDV

The auction’s final token price directly sets Ocelex’s FDV (Fully Diluted Valuation). Here’s how the price affects the FDV:

| Token Price ($)       | FDV ($) | Token Allocation (%)       |
| --------------------- | ------- | -------------------------- |
| 0.30 (Starting Price) | $30M    | Highest possible valuation |
| 0.24                  | $24M    | Strong public sale success |
| 0.15                  | $15M    | Balanced auction demand    |
| 0.06 (Minimum Price)  | $6M     | Lowest possible FDV        |

***

### How It Works – Example

Imagine the auction starts at $0.30 and decreases over time:

* Buyer A commits $2,000 when the token price is $0.15, expecting 13,333 tokens ($2,000 / $0.15).
* The auction continues, and the final token price is $0.10.
* Buyer A’s tokens are adjusted to the final price, receiving 20,000 tokens ($2,000 / $0.10) instead..

***

### Claim Options & Token Distribution

Upon sale completion, participants can claim their $OCX using two options:

**1. Balanced 25/25/25/25 Split:**

* 25% liquid $OCX
* 25% locked in veOCX (6-month lock)
* 25% locked in veOCX (12-month lock)
* 25% locked in veOCX (24-month lock)

**2. Max-Lock Bonus:**

* Lock the entire allocation as veOCX for 24 months to receive a 10% bonus on tokens.

***

### Next Steps After the Public Sale

**Token Generation Event (TGE): December 12th, 2024**

* Epoch 0 Launch: Trading, liquidity mining, and staking begin.

**Community Airdrop:**

* Eligible community members from Lynex, Thena, Aerodrome, Velodrome, and Fenix will receive a governance token airdrop.

**Post-Sale Opportunities:**

* Vote & Earn: Use veOCX tokens to vote on liquidity gauges, earn trading fees, and receive bribes.
* Weekly Rewards: Participate in veOCX emissions and rebases.


---

# Agent Instructions: 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:

```
GET https://ocelex.gitbook.io/ocelex/info-and-security/public-sale.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
