> For the complete documentation index, see [llms.txt](https://docs.lodacicero.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lodacicero.finance/ilp-rewards.md).

# ILP Rewards

### Strategies

Rewards in the ILP grow exponentially proportional to the amount of LODA invested into the pool. In the ILP there are two types of reward strategies:

#### Initial Rewards Strategy (IRS)

The IRS strategy provide rewards per LODA invested in the ILP, without a daily limit. This is done to encourage early Loda staking where the pool is not actually insuring anything. 

#### Maturity Rewards Strategy (MRS)

The MRS stategy will unlike the IRS have an upper limit of rewards. These rewards will be distributed between the ILP and SLP based on the current pool and healthy pool ratio.

![](/files/dZCqvonJ2Vj7nQcvV6nh)

#### USDC to LODA and vice versa Conversion

**LODA to USDC** conversion will happen in case of defaults. USDC can be borrowed from the treasury by pledging LODA tokens, so they never enter the open market or be bought from the open market directly by selling LODA.

In case of pledging, then the ILP contract is responsible for buying back all the pledged tokens at the pledged at price.

**USDC to LODA** conversion when collecting ILP fees as USDC and adding it to the ILP as LODA tokens.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lodacicero.finance/ilp-rewards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.