> 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/understanding-crypto-pools.md).
# Understanding Crypto Pools
Crypto pools are Ellipsis pools holding assets with different prices. Ellipsis' core originally was pegged assets but a new type of AMM allows for extremely efficient trading and low risks of non-pegged assets. \
\
Crypto pools use liquidity more effectively by concentrating it at current prices. As trades happen, the pool readjusts its internal price to the highest liquidity region without creating losses for the pool. Crypto pools also have variable fees which can range between 0.04% and 0.45%.\
\
Our first pool using this new design has the following coins: BUSD/BNB on the BNB chain.
## Whitepaper
Read the [Curve whitepaper](https://curve.fi/files/crypto-pools-paper.pdf) on which Ellipsis crypto pools is based off.
## Liquidity Providers
Becoming a liquidity provider in an Ellipsis Crypto pool is in all ways similar to stable pools. Unlike stable pools, however, you will gain exposure and risks to all assets in the pools, also known as [impermanent loss](https://academy.binance.com/en/articles/impermanent-loss-explained). \
\
To provide liquidity to the pool you can choose to add a single asset to the pool or add multiple depending on the pool. \
\
For example: LPs can add either BUSD, BNB or both to the BUSD-BNB pool.
## Fees
Fees on those pools range from 0.04% to 0.4%. The current fee varies based on how close the price is to the internal oracle. You can check a pool's current fee which changes every trade at the bottom of a pool page.
## Risks
As with any liquidity providing in blockchain, there are some smart contract risks involved. Curves' crypto pools have been audited by MixBytes and ChainSecurity but audits never eliminate risks completely.
\
---
# 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/understanding-crypto-pools.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.