> For the complete documentation index, see [llms.txt](https://gitbook.raac.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.raac.io/learn/production-suite/raaclend-or-rwa-tokenization-and-index/raac-lending-infrastructure/stability-pool.md).

# Stability Pool

When deploying crvUSD, lenders receive a receipt token called RcrvUSD. RcrvUSD can be deployed into the stability pool LP (RcrvUSD/DecrvUSD) to earn additional yield distributed by veRAAC holders through the second gauge.

{% hint style="info" %}
Note: DecrvUSD is the receipt token of RcrvUSD when deploying into the stability module. RcrvUSD and DecrvUSD are paired to make up the stability pool LP.
{% endhint %}

In return for higher yields, stability pool depositors accept but higher risk in the event of bad debt.&#x20;

The stability pool comes with a 14 day withdrawal window. Depositors send a withdrawal request, wait for the withdrawal window, and then have 72 hours to claim their withdrawn funds. If a user misses the claiming window, a new request is required.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.raac.io/learn/production-suite/raaclend-or-rwa-tokenization-and-index/raac-lending-infrastructure/stability-pool.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 `build a script that syncs our docs to a CMS` 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.
