> For the complete documentation index, see [llms.txt](https://help.defisaver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.defisaver.com/protocols/curveusd/what-are-bands-in-curveusd.md).

# What are bands in CurveUSD?

In CurveUSD protocol, each band represents a price range (calculated by the protocol) at which the amount of collateral in that band can be liquidated if the oracle price reaches it.<br>

The number of bands can go from 4 to 50, and the width of each one is determined by the Amplification parameter - A.<br>

Formula: `1/A * coll_price`\
Example: A = 100, 1 ETH = $2000 -> Band width = $20.

However, band width isn't fixed as each band uses its collateral price in the calculation.

Choosing a bigger number of bands gives you a wider price range for liquidation, but increases the chances of higher loss (**`LINK`**) during soft liquidations (and gas costs).

<figure><img src="/files/vT778S72H7zdP5RJuXld" alt=""><figcaption></figcaption></figure>


---

# 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://help.defisaver.com/protocols/curveusd/what-are-bands-in-curveusd.md?ask=<question>&goal=<endgoal>
```

`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.
