> For the complete documentation index, see [llms.txt](https://docs.blend.capital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blend.capital/pool-creators/setting-backstop-take-rate.md).

# Setting Backstop Take Rate

The Backstop Take Rate is the percent of the interest paid by pool borrowers sent to the pool's backstop module depositors. The level it's set at influences the proportion of capital you can expect the backstop module to have in relation to the pool. This correlation results from a higher backstop take rate making depositing in the backstop module more profitable.\
\
Here are example backstop take rates for pools of various risk levels using the following formula:

$$BackstopInterestRequirement = RequiredTVLCoverage\*RequiredInterestMultiple$$\
\
$$BackstopTakeRate = \frac{BackstopInterestRequirement}{(1+BackstopInterestRequirement)}$$

#### Low-Risk Pools

* Assumptions:
  * Need 2% of TVL covered
  * Backstop depositors demand a rate of 2.5x the lender's rate
* Required take rate of 4.75%
* Compound V3 would be considered a low-risk pool

#### Medium Risk Pools

* Assumptions:
  * 7.5% of TVL covered
  * Backstop depositors demand a rate of 4x the lender's rate
* Required take rate of 23.508%
* Aave V2 would be considered a medium-risk pool

#### High-Risk Pools

* Assumptions:
  * 15% of TVL Covered
  * Backstop depositors demand a rate of 5x lender's rate
* Required take rate of 42.86%
* Most pools with Stellar native tokens should be considered high risk


---

# 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.blend.capital/pool-creators/setting-backstop-take-rate.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.