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

# Launch Architecture

Hatchr uses one factory transaction to create a fixed-supply token and a live Uniswap V3 market.

```mermaid
flowchart TD
    A[Creator wallet] -->|launchToken| B[TokenFactory]
    B --> C[Deterministic LaunchToken clone]
    B --> D[TokenInitializer]
    B --> E[Uniswap V3 token/WETH pool]
    E --> F[Position NFT]
    F --> G[LPLocker]
    B -->|optional initial buy| H[SwapRouter02]
    B --> I[TokenCreated event]
    I --> J[Hatchr indexer]
    J --> K[PostgreSQL]
    K --> L[REST and realtime APIs]
```

## Launch call

The public factory entry point accepts:

```solidity
launchToken(
    string name,
    string symbol,
    string metadataURI,
    address feeWallet,
    address initialBuyRecipient,
    bytes32 salt
)
```

The call is payable. `msg.value` contains the configured launch fee plus any optional initial-buy ETH.

## Execution order

1. Validate metadata and wallet addresses.
2. Transfer the configured launch fee.
3. Deploy a deterministic minimal clone.
4. Initialize token metadata and supply through the trusted initializer.
5. Create and initialize the Uniswap V3 pool.
6. Mint a single-sided concentrated-liquidity position.
7. Transfer the position NFT to the locker.
8. Register creator and platform fee recipients.
9. Lock any token rounding dust.
10. Execute the optional WETH-to-token initial buy.
11. Emit `TokenCreated`.

The factory uses `nonReentrant`, and all steps share one transaction. A revert rolls back the complete launch.

## No pre-market

There is no separate Hatchr exchange or pre-graduation bonding curve. The Uniswap V3 pool is the market from launch.


---

# 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://docs.hatchr.fun/protocol/launch-architecture.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.