> For the complete documentation index, see [llms.txt](https://guide.dem.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.dem.exchange/community/glossary/liquidity-providers.md). # Liquidity Providers Liquidity providers are individuals who contribute their digital assets to a liquidity pool, forming the backbone of decentralized exchanges. These users lock their cryptocurrencies into the smart contract of a DEX, becoming liquidity providers in exchange for potential rewards. The compensation, typically in the form of trading fees, is distributed to liquidity providers based on the proportion of the total liquidity they contribute to the pool. This incentivizes users to participate actively, ensuring a robust and efficient trading environment within the decentralized ecosystem. The rewards are often distributed through LP tokens, which represent the liquidity provider's stake in the pool. Examples of liquidity providers include individuals contributing assets to pairs like SWTH-ETH on various DEX platforms. --- # 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://guide.dem.exchange/community/glossary/liquidity-providers.md?ask=&goal= ``` `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.