https://github.com/curvefi/scrvusd

Savings vault for crvUSD.
https://github.com/curvefi/scrvusd

Last synced: about 1 month ago
JSON representation

Savings vault for crvUSD.

• Host: GitHub
• URL: https://github.com/curvefi/scrvusd
• Owner: curvefi
• Created: 2024-09-04T14:39:55.000Z (4 months ago)
• Default Branch: main
• Last Pushed: 2024-11-01T17:59:59.000Z (about 2 months ago)
• Last Synced: 2024-11-01T19:16:42.896Z (about 2 months ago)
• Language: Vyper
• Homepage:
• Size: 465 KB
• Stars: 5
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# scrvUSD

Savings vault for crvUSD.

## Vault Implementation Details

The vault is an unmodified instance of a [Yearn v3 multi-strategy vault](https://github.com/yearn/yearn-vaults-v3) that accepts crvUSD deposits.

This vault aims to be as cheap as possible for users to deposit and withdraw funds. For this reason funds deposited in the vault are not moved anywhere and are always available to be redeemed.

Although the vault is called "multi-strategy" it actually doesn't contain any strategies. This is possible thanks to yearn vaults' v3.0.3 ability to [report on self](https://github.com/yearn/yearn-vaults-v3/pull/205).

## Rewards

Rewards in the vault will come from the fees generated by crvUSD controllers. The vault distributes a percentage of the fees through the fee splitter. What percentage of the fees is distributed is determined by Curve's DAO and the vault's [RewardsHandler](contracts/RewardsHandler.vy).

Anyone sending crvUSD to the rewards handler is also effectively donating those funds for distribution to scrvUSD vault depositors.

```mermaid

graph LR

    A[crvUSD controllers] --> B[Fee Splitter]

    O[Other Donors] --> C

    B --> C[Rewards Handler]

    C --> D[Yearn Vault]

```

## Fee Splitter Interaction and Weight calculation

For the fee splitter to send funds to the rewards handler, the rewards handler must be added as a receiver in the fee splitter by the DAO. Once this condition is met, the fee splitter will send funds to the rewards handler according to what the `weight` function in the rewards handler returns.

The `weight` function allows anyone to take snapshots of the ratio of crvUSD in the vault compared to the circulating supply of crvUSD. This ratio is used to determine the percentage of the fees that can be requested by the fee splitter.

For instance if the time-weighed average of the ratio is 0.1 (10% of the circulating supply is deposited into the vault), the fee splitter will request 10% of the fees generated by the crvUSD controllers.

---

The percentage of rewards that can be requested from the fee splitter has the following constraints:

$$\text{minimum weight} \leq \text{weight} \leq \text{fee splitter cap}$$

- Upper bounded by whatever percentage cap the fee splitter has. (Controlled by the DAO)

- Lower bounded by the `minimum_weight` parameter in the rewards handler. (Controlled by any `RATE_MANAGER` appointed by the DAO, or the DAO itself)

- The weight can be adjusted using a `scaling_factor` if necessary. (Controlled by any `RATE_MANAGER` appointed by the DAO, or the DAO itself)

Furthermore, it can be adjusted at any time by any `RATE_MANAGER` by calling the `set_distribution_time` function in the rewards' handler to prevent manipulation (i.e. MEV on the snapshots).