> For the complete documentation index, see [llms.txt](https://docs.communityfinance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.communityfinance.io/how-to-use-community-market/providing-liquidity.md).

# Providing Liquidity

Community Market's pools will have unilateral liquidity provision. This means only one type of token is needed to provide liquidity to the system.

Liquidity pair token creation is not required to mine liquidity (provide liquidity) in Community Market. 

This makes liquidity provisioning impeccably flexible and scalable.

There are currently three tokens in our stablecoin pools (USDC, USDT, and DAI). 

By depositing liquidity, you may mine stablecoins based on a variable share on transaction fees collected from each asset swap in the future.

**Unlike previous-generation liquidity pools, pool composition or pool size will not pose significant impact for deposit and withdrawal of single-sided tokens, even in bulk.** 

That being the case, we will make certain that addition or removal of new tokens to the main pool is scaled naturally, hence securing 100% exposure to single-asset utilisation.


---

# 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.communityfinance.io/how-to-use-community-market/providing-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.