# What is reUSDe ?

### reUSDe (Insurance Alpha)

**TL;DR** — reUSDe is Re Protocol's junior tranche token. It earns a higher yield — the risk free rate but with an 850 bps spread instead of 250 bps — in exchange for sitting lower in the capital stack. The reinsurance company's own equity still absorbs losses first, but reUSDe takes the next hit before reUSD. Redemptions are processed quarterly.

***

### 1. Purpose & Capital Stack Role

* **Junior tranche:** reUSDe sits below reUSD in the capital stack but above the reinsurance company's own equity. If losses exceed the reinsurer's equity contribution, reUSDe absorbs the next layer of losses before reUSD is affected.
* **Higher yield:** In exchange for this junior position, reUSDe earns a significantly higher spread (850 bps vs. 250 bps for reUSD).
* **Regulatory structure:** Deployed via the same §114 Trust structure, providing contingent capital to the reinsurance program.

#### Capital Waterfall (Losses Absorbed Top-Down)

1. **Reinsurance company equity** — first loss
2. **reUSDe — absorbs losses after reinsurer equity is exhausted**
3. **reUSD** — most senior, last to be impacted

### 2. Yield Mechanism

####  Yield Model

* reUSDe earns a very predictable reisk free rate + a spread of 850bps

### 3. Deployment & Loss Absorption

* **Mint** — Users deposit accepted assets into the reUSDe ICL contract.
* **Off-ramp** — Funds transfer to the ICL and onward to the §114 Trust as junior capital.
* **Loss absorption** — If portfolio losses exceed the reinsurance company's equity, reUSDe trust assets backstop claims, reducing tNAV accordingly.
* **Yield accrual** — The yield plus 850 bps spread flows into the token price daily. Idle funds pending deployment earn the sUSDe rate automatically until called.

### 4. Redemption Framework

| Stage               | Window                                                            | Fulfilment Basis                                | Settlement                      |
| ------------------- | ----------------------------------------------------------------- | ----------------------------------------------- | ------------------------------- |
| **Request**         | First 72 hours of each fiscal quarter                             | Queue captures amount & wallet                  | Instant confirmation            |
| **Actuarial Gate**  | **End-of-quarter reserve analysis (Also gated by regulators)**    | Determines available surplus                    | ≤ 10 business days              |
| **Pro-Rata Payout** | If requests ≤ surplus: 100% fill. If > surplus: proportional fill | Assets wired from trust → on-chain → burn & pay | Up to 5 business days post-gate |
| **Rollover**        | Unfilled balance auto-rolls to next quarter                       | Retains seniority in queue                      | N/A                             |

No secondary market maker pool is promised. OTC trades are unrestricted but not protocol-guaranteed.

### 5. Transparency & Risk Controls

* **Chainlink oracles** — Publish daily price, surplus buffer.
* **Independent actuary** — Validates claim reserves and surplus release schedule.
* **Custodian reporting** — Trust bank provides daily statements; hashed and posted on-chain.
* **Audit & assurance** — Smart-contract audits and annual SOC-type reports on off-chain entities.

### 6. Risks & Disclaimers

* **Loss risk** — reUSDe absorbs portfolio losses after the reinsurer's equity is exhausted. Severe claim events may impair NAV.
* **Liquidity risk** — Redemptions are gated quarterly and **only available as regulators allow collateral release**; distress scenarios may extend settlement.
* **Regulatory** — Not offered to U.S. persons; local securities laws may apply.

This document is informational and not investment advice. Parameters (fees, redemption cadence, Ethena integration) may evolve — always consult the latest docs and on-chain feeds.


---

# Agent Instructions: 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:

```
GET https://docs.re.xyz/insurance-capital-layers/what-is-reusde.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.