# CL Gauges

<figure><img src="https://574688988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYMqlsCWiUq0hugfAqLjK%2Fuploads%2FbYk9XbGpxZKCmKEjOwnL%2FCleo%20CL%20Gauges.png?alt=media&#x26;token=c04f61e7-ee9e-431d-a68e-a8ea4f8855e6" alt=""><figcaption></figcaption></figure>

Cleopatra introduces a significant enhancement to the CL rewarding model, primarily through the innovative CL Gauge contract infrastructure. This crucial component seamlessly integrates into the ve(3,3) model, and we have chosen to secure it under a BUSL-1.1 license.

**Features of Cleopatra CL Gauges**

* Non-custodial staking solution
  * Cleopatra employs a unique method of staking and rewarding LP providers through a delegation mechanism. This approach allows users to retain their NonFungiblePositions in their wallets while still earning Fees, CLEO, and other LP Bribes through emissions.
* Competitive Rewarding Logic

  * The CL Gauges determine rewards based on several factors:
    * Tick Delta (Δ) \[Upper - Lower] of the user's position
    * Position size
    * Position Utilization: In Range? \[True or False]
  * An example formula is such:

  $$userLiquidity / tickDelta = rewardMultiplier$$

  * This rewarding methodology offers several benefits. It encourages tighter liquidity ranges, resulting in higher emissions for participants. By concentrating liquidity within these utilized ranges, overall slippage decreases, and volume/fees increase due to more favorable swap routing.


---

# 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://docs.cleo.exchange/concentrated-liquidity-core/cl-gauges.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.