> 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-governance/tokenomics.md).

# Tokenomics

**RSUP** is the Resupply governance token. It is minted on a **set inflation schedule** (no hard cap).

* Staking **RSUP** grants **protocol revenue (reUSD)** + **voting power** (1 staked RSUP ≈ 1 weight).
* Unstaking is a two-step process with a **14-day cooldown (2 epochs)**; while cooling down you stop earning revenue and voting power.
* RSUP is emitted to **voting incentives**, the **insurance pool**, and **borrowers** via governance set weights.

### Launch distribution (5-year schedule)

* **60%** of the 5-year emissions were minted at Token Generation Event (TGE).
* Emissions ramp: **12% → 10% → 8% → 6% → 4%** per year over 5 years, then **2% tail inflation**.
* Protocol allocations (vested):
  * **20%** Convex protocol sub-DAO (5y vest — staked for veCRV power + revenue)
  * **10%** Yearn protocol (5y vest)
  * **0.5%** Frax Protocol (codebase grant, 1y vest)
  * **15%** Prisma token burns incl. liquid lockers (5y)
  * **2%** Prisma hack victims (2y)
  * **2%** Team (1y)
  * **10.5%** Treasury (5y)
  * Remaining \~**31%** emitted as protocol emissions (voting incentives / insurance / borrowers)
* **RSUP** that **Prisma** holders redeemed at the **11.54:1** PRISMA:RSUP conversion vests over 5 years.<br>

<figure><img src="https://700558760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuvAB3MBg39dnAFUqHuUe%2Fuploads%2FiOeSKkZMC8F7zy4wY0Nc%2Fressuply-gitbook-token-distribution-banner-1280x640-v1%20(2).png?alt=media&amp;token=bafa77fe-7d78-4c70-820b-57efa9a86457" 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 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-governance/tokenomics.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.
