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

# Dilution Protection (3,3) Rebases

Cleopatra, adopted the (3,3) model, which includes a mechanism to mitigate dilution. **(3,3) means there HAS to be a rebase.** Without a rebase, the model cannot be coined a ve(3,3) DEX.

During the initial launch, veCLEO holders will benefit from a 25% weekly rebase, which helps counterbalance dilution resulting from the protocol's emissions schedule. With each subsequent epoch (week), this percentage increases by 1% until reaching a maximum cap of 50% anti-dilution per epoch.

Cleopatra strongly believes that rebases/anti-dilution are crucial to the entire model, and without it-- leads to a dangerous misalignment with users.


---

# 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.cleo.exchange/cleo-tokenomics/dilution-protection-3-3-rebases.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.
