> 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/locked-liquidity.md).

# Locked Liquidity

The factory transfers each Uniswap V3 position NFT to the Hatchr `LPLocker` during the launch transaction.

## Position lock

The deployed locker has no function that withdraws or transfers a registered position NFT. Neither the token creator nor the Hatchr factory receives custody of the LP NFT after registration.

The pool remains active and the position continues earning fees. Locking prevents removal of this Hatchr-created position; it does not prevent independent users from creating other positions in the same pool.

## Rounding dust

Uniswap tick mathematics may prevent a tiny portion of the fixed supply from entering the position. The factory transfers this dust to the locker and records it in `lockedDust`.

The dust:

* is not sent to the creator;
* is not shown as a burn transaction;
* remains held by the locker; and
* does not have a withdrawal path in the deployed locker.

{% hint style="warning" %}
“Locked liquidity” describes the Hatchr position NFT. It is not a guarantee of token value, stable pricing, minimum WETH depth or trading profitability.
{% endhint %}


---

# 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/locked-liquidity.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.