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

# Fair Launch Mechanics

A "fair launch" is one of those phrases that's almost meaningless in DeFi — most launches calling themselves fair are anything but. stonk.market takes the term seriously. Every mechanism in the protocol exists to remove the advantages early insiders normally have.

## What "Fair" Means Here

Concretely:

* **No one can buy before the public can.** The deployer's only privileged action is a single atomic buy during the deployment transaction itself — and that buy is capped, on-record, and at the same starting price everyone else gets.
* **No one can dump on the public at launch.** Trading is locked the instant the contract is deployed, and stays locked until the next NYSE market open. There is no quiet window where insiders trade and retail can't.
* **No one can change the rules after the fact.** Every token parameter is immutable. The deployer has no admin powers after the initial buy.
* **No one can rug the liquidity.** The token's liquidity lives in a Uniswap v4 pool from launch, and the StonkHook reverts every attempt to remove it — from anyone, the team included.

## The Mechanisms

### No Grace Period

The moment `deployToken()` returns, trading is locked. There is no window between deployment and first-trade where the deployer can quietly accumulate.

| Deploy Time       | First Trade Possible |
| ----------------- | -------------------- |
| Monday 8:00 AM ET | Monday 9:30 AM ET    |
| Monday 2:00 PM ET | Tuesday 9:30 AM ET   |
| Friday 5:00 PM ET | Monday 9:30 AM ET    |
| Sunday            | Monday 9:30 AM ET    |

Tokens always wait for the **next** market open. Deploy before the bell on a trading day and that is today's 9:30; deploy mid-session and the token sits out the rest of the day.

### Atomic Initial Buy

The deployer can choose to make one buy in the same transaction that creates the token. It happens after the Uniswap v4 pool is seeded but before trading is unlocked — and it's all one atomic step. No one can sandwich it, front-run it, or insert a buy between deployment and the deployer's purchase.

```
One transaction:
  1. Clone the token contract
  2. Seed the Uniswap v4 pool with the bonding-curve position
  3. Execute the deployer's launch buy (if any)
  4. Lock trading until the first market open
```

The launch-buy amount is capped (`maxDevInitialBuyAmount`, 0.1 WETH for WETH-backed tokens or 160 USDC for USDC-backed tokens) so the deployer can't take a disproportionate share of supply.

### Dev Allocation Limits

The deployer optionally receives a small minted allocation (capped at 10%, typically 0.5%). Those tokens are **locked** until first market open — the deployer can't transfer them before the public can trade.

### Max Wallet

Every token caps how much of supply any single address can hold (typically 5%). This makes whale accumulation impossible by design.

### Name + Symbol Registry

The factory rejects duplicate `(name, symbol)` pairs. You can't deploy "PEPE / PEPE" twice. This makes impersonation attacks — where someone clones a popular token's branding — structurally impossible at the factory level.

### Immutability

Once deployed, **nothing** about your token can change:

* Trading fee, max wallet, dev allocation
* Oracle, hook, and pool addresses
* Bonding curve parameters
* Launch time (first window open)

No owner. No admin. No upgradeability. Every token is a standalone contract whose behavior is fixed at the moment it's born.


---

# 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://stonkmarket.gitbook.io/docs/concepts/fair-launch.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.