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

# Liquidity Tracking

To facilitate query liquidity Midas uses a 3-layer tree structure. Each node is a 256bit array recorded with uint256. There are exactly $$256^3=2^{24}$$ slots at the bottom of the tree, corresponding to the theoretical maximum of $$2^{24}$$ slots in our bin. We record this underlying slot as 1 when there is liquidity in a bin, and label it as 0 otherwise. When a parent node has a 1 in the 256 slots it contains, the parent node is also marked as 1, and so on.

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

This structure can help us efficiently find the next bin with liquidity in a given direction and update the current floor price and best offer.


---

# 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://midaswap.gitbook.io/docs/technical-reference/liquidity-tracking.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.
