> For the complete documentation index, see [llms.txt](https://docs.bancor.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bancor.network/developer-guides/data-and-events/liquidity-data.md).

# Liquidity Data

Bancor version 3 pools allow unlimited deposits, but, only a predetermined amount is available for trading. The amount of trading liquidity is determined by the Bancor DAO for each token, denominated in BNT. These values can be tracked from Events with the parameters Total Liquidity & Trading Liquidity. 

* **Total Liquidity:** The total number of tokens deposited into a pool. All liquidity is protected from impermanent loss and represented by pool tokens (bnToken). 
* **Trading Liquidity:** The number of tokens available for trading. This number is used to determine the rate and slippage for each trade. 

For example if: 

* TOKEN is trading at 1 TOKEN = 1 BNT.  
* The trading liquidity for TOKEN is set to 100,000 BNT
* 250,000 TOKEN are deposited

Total Liquidity would equal 250,000. 

Trading liquidity would equal 100,000. 

{% content-ref url="/pages/sSl1W5Xjcfbtu4vYLQcd" %}
[UniswapV2PositionMigrated()](/developer-guides/data-and-events/liquidity-data/cross-amm-migration-data/uniswapv2positionmigrated.md)
{% endcontent-ref %}

{% content-ref url="/pages/Stfvx1s8ZqK3GcB9FxKz" %}
[SushiswapV1PositionMigrated()](/developer-guides/data-and-events/liquidity-data/cross-amm-migration-data/sushiswapv1positionmigrated.md)
{% endcontent-ref %}


---

# 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.bancor.network/developer-guides/data-and-events/liquidity-data.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.