> For the complete documentation index, see [llms.txt](https://docs.behodler.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.behodler.io/user-docs/ecosystem/behodler/liquidity.md). # Liquidity Providers ## Enter single sided liquidity Since Behodler pools are created through Scarcity ([SCX](/user-docs/tokens/scarcity.md)) (and not ETH), and SCX is an index of the value of all tokens on the DEX, and SCX is minted on a token bonding curve, there is no linear progression of tokens & ETH up and down a price curve. This means that impermanent loss is significantly reduced (not completely eliminated however — this would be impossible). What we describe technically is that the impact of impermanent loss diminishes drastically and rapidly as more tokens are added. When an exchange happens on a pair on multi-token pools, both underlying tokens change in composition. With Behodler, a swap does change the relative composition of 2 tokens but the remaining tokens are unaffected. The relative immediate impact of a swap is therefore more substantially muted in Behodler. ### Adding Liquidity To provide liquidity on Behodler, one simply swaps the desired token to SCX. ***Note:*** the UI button will change from "Swap" to "Add Liquidity" ### Withdrawing Liquidity To remove liquidity from Behodler, one simply swaps an amount of SCX to the desired output token. ***Note:*** the UI button will change from "Swap" to "Withdraw Liquidity" --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.behodler.io/user-docs/ecosystem/behodler/liquidity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.