> For the complete documentation index, see [llms.txt](https://docs.novamp.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novamp.io/creators/liquidity-and-pools.md).

# Liquidity & Pools

Your token launches straight into a real DEX pool — you decide whether the liquidity is burned or time-locked.

{% hint style="info" %}
There is **no bonding curve and no migration** on EVM. The pool exists and is tradable from the first block, and the liquidity disposition you choose is **permanent once trading begins**.
{% endhint %}

## Overview

At launch, Novamp seeds a **real Uniswap / PancakeSwap pool** with your token. The pool type is derived from your [tax setting](/creators/taxes.md), and how the launch liquidity is held is your choice — burned forever, or locked for a fixed period.

## How it works

```mermaid
flowchart LR
  A[launch tx] --> B{Any tax?}
  B -- No --> C[v3 single-sided pool]
  B -- Yes --> D[v2 pair + opening liquidity]
  C --> E[Position held in PositionVault]
  D --> F[LP burned or locked]
```

| Token type                | Pool                             | Seeded by  |
| ------------------------- | -------------------------------- | ---------- |
| **Zero-fee**              | v3 pool (concentrated liquidity) | `V3Seeder` |
| **Tax** (fee-on-transfer) | v2 pair                          | `V2Seeder` |

### v3 opening price & range

For v3 launches, opening price is **normalized to a target FDV** rather than a fixed per-token price, so your opening market cap is consistent no matter which [supply preset](/creators/supply-and-allocation.md) you choose. The position's **top tick is uncapped**, so the token can appreciate without an artificial price ceiling.

## How to use it

### v3 (zero-fee tokens)

Liquidity is added **single-sided** and held permanently in the protocol `PositionVault`. There are no LP tokens to withdraw and no opening-liquidity input is needed — the disposition is permanent by design.

### v2 (tax tokens)

You pair opening liquidity (in the chain's native coin) with your tokens, then choose what happens to the LP:

| Option               | What happens                                                        |
| -------------------- | ------------------------------------------------------------------- |
| **Burn permanently** | LP tokens sent to the dead address — liquidity can never be pulled. |
| **Lock 30 days**     | Held by `LiquidityLocker`, withdrawable after 30 days.              |
| **Lock 90 days**     | Withdrawable after 90 days.                                         |
| **Lock 1 year**      | Withdrawable after 365 days.                                        |

### The burn (dead) address

Burned LP — and any token tax routed to **Burn** — is sent to the canonical dead address:

```
0x000000000000000000000000000000000000dEaD
```

It has no known private key, so anything sent there is permanently removed from circulation. Burned-liquidity tokens show a **🔥 Burned** badge on the token page linking here on the explorer, so anyone can verify the LP was destroyed.

## Important details

| Property          | Detail                                                      |
| ----------------- | ----------------------------------------------------------- |
| v3 liquidity      | Single-sided, permanently held in `PositionVault`           |
| v2 liquidity      | Burn or lock 30 / 90 days / 1 year via `LiquidityLocker`    |
| Opening liquidity | Required for v2; not applicable for v3                      |
| Permanence        | The lock/burn choice **cannot change** after trading starts |
| Disclosure        | The disposition is shown on the token page                  |

## What happens next?

* The pool is live and tradable immediately; no graduation step.
* Burned liquidity is irrecoverable; locked liquidity unlocks only after its committed period.
* **Burn** is the strongest trust signal; **lock** lets you manage liquidity later while guaranteeing it stays put for the committed window.

## Troubleshooting

| Symptom                                         | Fix                                                                   |
| ----------------------------------------------- | --------------------------------------------------------------------- |
| "Add the initial liquidity required to launch"  | v2 (tax) launches need opening liquidity greater than 0.              |
| "Liquidity was provided where none is expected" | v3 (zero-fee) launches take no opening liquidity — clear the field.   |
| Can't change lock/burn after launch             | This is by design — the disposition is permanent once trading begins. |

## Continue exploring

* [💸 Token Taxes](/creators/taxes.md)
* [🛡️ Anti-Sniper Protections](/creators/anti-snipe-and-protection.md)
* [📜 Contract Addresses](/protocol/contracts-and-addresses.md)
* [⚡ Trading Overview](/traders/overview.md)


---

# 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.novamp.io/creators/liquidity-and-pools.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.