> For the complete documentation index, see [llms.txt](https://docs.stakestone.io/stakestone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakestone.io/stakestone/stone-fi/liquiditypad/how-liquiditypad-works.md). # How LiquidityPad Works Upon depositing assets, users receive **LP tokens**, which represent their share in the liquidity vault. These LP tokens can be leveraged across Ethereum’s DeFi ecosystem, unlocking multiple opportunities: * **Liquidity Provision and Trading on DEXs:** Users can deploy LP tokens on DEXs such as **Uniswap and Curve**, providing liquidity to earn trading fees or trade LP tokens directly * **Collateralized Borrowing:** LP tokens can be used as collateral on lending platforms such as **Aave and Morpho** * **Yield Optimization Strategies:** Through platforms like **Pendle**, users can trade or lock in their future yields, optimizing their returns based on market conditions * **Ecosystem Incentives:** LP tokens provide access to exclusive opportunities such as **airdrops, governance rights, and reward programs** from partner protocols LiquidityPad's flexible and customizable liquidity infrastructure enables users to enhance their returns while providing emerging ecosystems with a long-term, tailored liquidity solution. --- # 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.stakestone.io/stakestone/stone-fi/liquiditypad/how-liquiditypad-works.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.