> For the complete documentation index, see [llms.txt](https://ocelex.gitbook.io/ocelex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ocelex.gitbook.io/ocelex/protocol-overview/flywheel-fundamentals.md).

# Flywheel Fundamentals

The Ocelex ecosystem thrives on synergy and balance, combining the efforts of users, protocols, and liquidity providers to propel our liquidity strategy. This collaborative approach creates positive feedback loops, boosting platform functionality and value.

<figure><img src="/files/p2dspI9HOBCRj50BTrGO" alt=""><figcaption><p>Ocelex Flywheel</p></figcaption></figure>

### **Liquidity Providers**

At the heart of our DEX, liquidity providers offer seamless trading by utilizing a concentrated liquidity model. This not only improves capital efficiency but also increases fee generation, outperforming traditional DEX models. Providers are rewarded with oOCX tokens, giving them flexibility to meet their goals.

### Traders

Traders enjoy a vibrant trading environment with ample liquidity and minimal slippage, ensuring competitive rates. All trading fees go directly to veOCX voters, rewarding those who actively contribute to our growth.

### Protocols

Protocols can kickstart their liquidity by incentivizing veOCX voters to support their pools. This increases emissions to those pools, enhances APR, and attracts more liquidity providers, making protocols an essential piece of our ecosystem.

### veOCX Voting

veOCX voters play a critical role, receiving 100% of trading fees and bribes from protocols to prioritize certain pools. This system allows them to guide emission rewards to preferred pools, creating a dynamic liquidity landscape.

Ocelex adopts ve(3,3) mechanics, combining Vote-Escrow (inspired by Curve) for long-term engagement and (3,3) game theory (from Olympus DAO) for stake-based rewards. This encourages liquidity provision, strategic OCX locking, and active governance participation, enriching our ecosystem for all stakeholders.


---

# 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://ocelex.gitbook.io/ocelex/protocol-overview/flywheel-fundamentals.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.