# Configuration

Launching a token requires configuring four categories of parameters. Every choice is made before deployment and locked onchain.

Token Identity

| Parameter         | Description                                                                                                          |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Token Name**    | The full name of your token (e.g., "ABC Token"). Stored onchain in the ERC-20 contract.                              |
| **Token Symbol**  | The ticker symbol (e.g., "XYZ"). Used across Aerodrome, explorers, and wallets.                                      |
| **Total Supply**  | The total number of tokens minted at launch.                                                                         |
| **Logo**          | An image uploaded and pinned to IPFS. Linked to the token's onchain metadata for display on Aerodrome and explorers. |
| **Twitter X URL** | Optional link to your project's Twitter/X profile, displayed on the token detail page.                               |

Liquidity Settings

| Parameter          | Description                                                                                                | Options                                               |
| ------------------ | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| **Liquidity %**    | Percentage of total supply allocated to the Aerodrome pool. The remaining tokens go to the creator wallet. | 1-100%                                                |
| **Pair Token**     | The asset paired against your token in the pool.                                                           | ETH (WETH: `0x4200...0006`) or USDC (`0x8335...2913`) |
| **Initial Amount** | The amount of ETH or USDC you deposit to seed the pool. This sets the initial price of your token.         | Any amount                                            |
| **Pool Type**      | The AMM model for your trading pair.                                                                       | vAMM or CL (see Pool Types)                           |

Pool Types

**vAMM (Volatile AMM)** - standard constant-product pools (x \* y = k), similar to Uniswap V2. Liquidity is spread across the entire price range. Simple, battle-tested, and best suited for new tokens with expected volatility. LP is represented as an ERC-20 token.

**CL (Concentrated Liquidity)** - concentrated liquidity pools similar to Uniswap V3. The Launcher deploys a full-range position by default (widest possible ticks), giving you the benefits of Aerodrome's CL infrastructure and fee tiers while keeping the setup simple. LP is represented as an NFT position.

| Feature           | vAMM                    | CL                      |
| ----------------- | ----------------------- | ----------------------- |
| Price range       | Full range (automatic)  | Full range (default)    |
| LP representation | ERC-20 token            | NFT (position manager)  |
| Locker contract   | V2 Pool Launcher Locker | CL Pool Launcher Locker |
| Fee model         | Standard swap fees      | Tick-based fee tiers    |
| Best for          | Most launches           | Advanced use cases      |

Lock Duration

| Option            | Behavior                                                                                                        |
| ----------------- | --------------------------------------------------------------------------------------------------------------- |
| **Custom (days)** | LP is locked for the specified number of days. After expiry, it can be withdrawn.                               |
| **Permanent**     | LP is locked forever (max uint32 duration). It can never be withdrawn. Maximum trust signal for your community. |

Locking is handled natively through Aerodrome's LockerFactory contracts, not a third-party lock service. The lock is onchain, verifiable, and non-upgradeable.


---

# 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://docs.reflect.now/launcher/configuration.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.