> For the complete documentation index, see [llms.txt](https://docs.auto.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auto.finance/developer-docs/contracts-overview/autopool-eth-contracts-overview/autopool-contracts-glossary.md). # Autopool Contracts Glossary * **Autopool System** - Name of the overall system * **Autopool** - A 4626 vault that users deposit assets into * **AutoPoolETH** - A specific implementation of an AutoPool denominated in ETH/WETH * **Destination** - An external contract, or set of contracts, that we LP/stake user funds into * Examples * A Balancer pool * A Balancer pool with LP staked into Aura * A Curve pool with LP staked into Convex * **DestinationVault** - A contract that sits in front of a Destination in our system. These act has a proxy and give us a common interface to that Destination to perform our operations. * **Solver** - Contract that can turn assets into LP tokens, LP tokens into other LP tokens, or LP tokens into assets * **Strategy** - A contract that determines whether a Rebalance is in the best interest of an Autopool * **Rebalance** - The deployment of: * Idle funds to a Destination * Funds from one Destination to another Destination * Funds from one Destination back to Idle * **Liquidation -** The process of taking rewards and auto-compounding them into WETH --- # 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.auto.finance/developer-docs/contracts-overview/autopool-eth-contracts-overview/autopool-contracts-glossary.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.