> For the complete documentation index, see [llms.txt](https://docs.thenile.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thenile.exchange/introduction-to-nile/ve-3-3-fundamentals/dilution-protection-rebase.md).

# Dilution Protection (Rebase)

A key function of the ve(3,3) model is the dilution protection rebases, which occur per epoch, to incentivize users to lock their tokens early on. The rebase is a nod to the OHM (3,3) model that was popularized the past couple years.

A practical example to give you a better understanding of how the system works:

**EXAMPLE: 25% Dilution Protection:**

{% hint style="success" %}
Note: NILE has a 25% rebase, increasing 1% per epoch until 50%
{% endhint %}

* You have 1000 NILE, which is 10% of the total supply of 10,000 NILE at the time.
* During this epoch, another 10,000 NILE was emitted to gauges, pushing the total supply of NILE to 20,000
* You can claim your rebase after the epoch ends and receive 250 extra NILE added to your position. This makes you now have 6.25% of the total supply, at 1250 NILE out of 20,000 NILE

The above is a crude but straightforward example that should simply explain the ideology and functionality of the rebase.


---

# 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.thenile.exchange/introduction-to-nile/ve-3-3-fundamentals/dilution-protection-rebase.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.