> For the complete documentation index, see [llms.txt](https://docs.resupply.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resupply.finance/resupply-protocol/overview.md). # Overview Resupply is a decentralized stablecoin protocol. Depositors supply **crvUSD** or **frxUSD** to battle tested lending markets (Curve Lend, Curve Lend v2, Fraxlend), borrow **reUSD** against that collateral, and keep earning the underlying lending yield. **reUSD** is backed 1:1 by these stablecoin denominated positions. ### How Resupply works 1. **Borrowers** earn the lending market's yield on their collateral while paying a **borrow rate** which is always at least half the lending rate, half the **sfrxUSD** "risk-free" rate or 2%, whichever is greater. 2. **Revenue** (borrow interest + redemption fees) is routed to a fee deposit and split every week: **70% to RSUP stakers, 15% to sreUSD stakers, 10% to the Insurance Pool, and 5% to the Treasury**. 3. **RSUP emissions** are directed by governance at voting incentives, the insurance pool, and directly at borrowers. 4. The revenue that borrowers generate will directly correlate with the emissions directed towards them. The more revenue a borrower generates for Resupply, the greater the share of emissions it will receive. --- # 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.resupply.finance/resupply-protocol/overview.md?ask=&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.