# APR Formulas

<figure><img src="/files/kpXnb5IgtJF7vrdEOhDp" alt=""><figcaption></figcaption></figure>

This page of the documentation is dedicated to a detailed explanation of the APR calculations used in the Chi Protocol's frontend. Before listing all respective APR calculations, it is important for the reader to understand the following information about the rewards and their distribution periods:

### Reward Types and Their Origins

The rewards within the Chi Protocol ecosystem are primarily derived from two key sources:

<details>

<summary><strong>Protocol Revenue:</strong></summary>

* *stETH and wETH rewards* generated from the protocol's reserves.
* *Arbitrage revenue* in USC, generated through the Dual Stability Mechanism.\
  For more details, refer to [Sustainable Reward Sources](/chi-docs/concepts/sustainable-reward-sources.md) and [Rewards Generation & Distribution](/chi-docs/usc/rewards-generation-and-distribution.md).

</details>

<details>

<summary><strong>CHI Incentives:</strong></summary>

These are additional token incentives provided from the Chi Protocol's treasury contract.\
For more information on the current Rewards Program, visit our [Medium](https://medium.com/chi-protocol).

</details>

### Rewards Distribution Periods

The rewards within the Chi Protocol ecosystem are distributed according to the following schedule:

<details>

<summary><strong>Rewards to Stakers:</strong></summary>

Rewards to stakers are calculated on a per-second basis and distributed with every Ethereum block. This applies to stakers of stUSC, wstUSC, CHI/ETH LP, and USC/ETH LP.

</details>

<details>

<summary><strong>Rewards to USC and LP Boosters:</strong></summary>

Rewards for boosters are calculated on a daily basis and distributed once per day. Boosters include wstUSC boosters, CHI/ETH LP boosters, and USC/ETH LP boosters.

</details>

<details>

<summary><strong>Rewards to CHI Boosters:</strong></summary>

Rewards for CHI boosters are calculated on a weekly basis, with each epoch lasting one week, and are distributed once per week.

</details>

This foundational understanding is essential for interpreting the APR calculations presented in the following sections.

### APR Calculations

Below are the respective formulas used to calculate the APRs for **staking** contracts within the Chi Protocol User Interface (UI):

#### stUSC

<figure><img src="/files/FlqjGXUOXnaULS6zTt12" alt=""><figcaption><p>stUSC APR</p></figcaption></figure>

#### wstUSC

<figure><img src="/files/DLgWN7oJALetyPglb1yS" alt=""><figcaption><p>wstUSC APR </p></figcaption></figure>

#### veCHI

<figure><img src="/files/R24dQwXqeOAVcaPXz8sX" alt=""><figcaption><p>veCHI APR </p></figcaption></figure>

#### Staked CHI/ETH LP&#x20;

<figure><img src="/files/Gj0KvTzbeV3wqtXykVJV" alt=""><figcaption><p>Staked CHI/ETH APR </p></figcaption></figure>

#### Staked USC/ETH LP&#x20;

<figure><img src="/files/xzQKQJ0ey3v8f7d6lpF2" alt=""><figcaption><p>Staked USC/ETH APR </p></figcaption></figure>

Below are the respective formulas used to calculate the APRs for **boosting** contracts within the Chi Protocol User Interface (UI):

#### Boosted stUSC

<figure><img src="/files/GsIxIYLO7g6UhBLzDzir" alt=""><figcaption><p>Boosted stUSC APR </p></figcaption></figure>

#### Boosted wstUSC

<figure><img src="/files/uEO96d1UIiAnPHqdeQ9h" alt=""><figcaption><p>Boosted wstUSC APR </p></figcaption></figure>

#### Boosted CHI/ETH LP&#x20;

<figure><img src="/files/HR49EilqyLZamHImWjQF" alt=""><figcaption><p>Boosted CHI/ETH LP APR</p></figcaption></figure>

#### Boosted USC/ETH LP&#x20;

<figure><img src="/files/rru3csZh9YdoEVUd08fY" alt=""><figcaption><p>Boosted USC/ETH LP APR</p></figcaption></figure>


---

# 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://chi-protocol.gitbook.io/chi-docs/resources/apr-formulas.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.