> For the complete documentation index, see [llms.txt](https://docs.caval.re/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caval.re/overview/multiswap-for-liquidity-providers.md).

# Multiswap: For Liquidity Providers

1. **Access to an ETF-Like LP Token:**&#x20;

LP tokens on Multiswap represent the value of all assets within the pool in their given weights, similar to how an ETF represents a basket of different stocks. This diversified exposure reduces risk and optimizes portfolio management.

2. **Perfect Rebalancing:**&#x20;

Multiswap pools are constantly rebalancing, aligning asset weights with preset constraints, and mimicking ETF behavior.

3. **No Single-Trade Impermanent Loss:**&#x20;

With its unique post-trade pricing mechanism, Multiswap eliminates subsidies on trades that would lead to both the single-trade impermanent loss and loss-vs-rebalancing found in other AMM designs.

4. **Native Single-Sided Staking:**&#x20;

Providing and removing liquidity is as easy as swapping one of the tokens in the pool for the LP token or vice versa. Greatly simplifying the user experience.


---

# 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.caval.re/overview/multiswap-for-liquidity-providers.md?ask=<question>&goal=<user_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.
