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

# V3

<figure><img src="/files/v9sUu51ytaBZHkOqH7mK" alt=""><figcaption></figcaption></figure>

DragonSwap V3 introduces LP NFTs, allowing liquidity providers to control how they supply liquidity.

### Concentrated Liquidity

<figure><img src="/files/NAqAfssxqs58aRgmsxGf" alt=""><figcaption></figcaption></figure>

V3 allows liquidity providers to allocate liquidity within a specific price range, making capital use more efficient.

Example: Instead of distributing $10,000 across the entire price range, a provider can concentrate liquidity within $1.5-$2.0, increasing fee earnings within that range.

### Non-Fungible Liquidity Positions

LP tokens in V3 are issued as NFTs, representing liquidity positions and accrued trading fees. These NFTs act as receipts and provide flexible liquidity management.

### Active Liquidity & Price Ranges

Liquidity earns fees only when market prices are within the provider’s specified range. When prices move outside the range, liquidity becomes inactive but remains secure.


---

# 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.dgswap.io/products/pools/v3.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.