> For the complete documentation index, see [llms.txt](https://docs.ellipsis.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ellipsis.finance/liquidity-providers/base-and-metapools.md). # Base, Meta and Factory Pools Ellipsis has three types of pools: 1. Base pools: `3EPS` (`BUSD-USDC-USDT`), `btcEPS` (`BTCB/renBTC`) 2. Meta pools: for example `[fUSDT, [3EPS]]`, `[DAI, [3EPS]]` or `[TUSD, [3EPS]]` 3. Factory pools: permissionless pools that can be created by anyone. These pools can be meta pools or plain pools, and can contain stablecoins, pegged `BTC` or `BNB` and can contain anywhere from two to four tokens. {% hint style="info" %} Factory pools, being permissionless, can be created by anyone or any team. Please be sure to understand the assets in a factory pool if you are going to provide liquidity or trade in the pool. {% endhint %} Meta pools allow for one token to trade with another underlying Base pool. In this example users could seamlessly trade `fUSDT` between the three coins in the `3EPS` pool (`BUSD-USDC-USDT`). This is helpful in multiple ways, including: * preventing dilution of existing pools, * allowing Elipsis to list less liquid assets, * providing more volume and more trading fees for liquidity providers. A Meta pool consisting of `[fUSDT, [3EPS]]` would contain `fUSDT` and `3EPS` LP tokens. This means that liquidity providers of the 3EPS pool who do not provide liquidity in the `[fUSDT, [3EPS]]` Meta pool are shielded from systemic risks from the Meta pool. --- # 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://docs.ellipsis.finance/liquidity-providers/base-and-metapools.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.