# veRCT

### `veRCT` **Utility** <a href="#vethe-utility" id="vethe-utility"></a>

* Protocol revenue access: `veRCT` holders can vote for gauges on a weekly basis, and access 90% of the trading fees and 100% of the voting incentives for the associated pool.
* Governance participation: `veRCT` holders can partake in governance and cast votes for the protocol improvement proposals.

#### `veRCT` voters receive:

* Trading fees generated by the pool(s) they vote for.
* Voting incentives deposited for the pools they vote for.
* Weekly veRCT rebase (early adopter anti-dilution mechanics).

### `veRCT` **Specifications** <a href="#vethe-specifications" id="vethe-specifications"></a>

* *ve(3,3) Mechanics*: The Olympus DAO anti-dilution method, commonly known as the rebase mechanism, is combined with Curve's *vote-escrowed* model in the Solidly-initiated ve(3,3) Mechanics concept. To safeguard `veRCT` holders from dilution and to enable a dynamic distribution of `veRCT` among participants over time, the anti-dilution level has been capped at 30%.
* *Gauge:* A pool with dynamic `$RCT` rewards based on `veRCT` weekly voting allocation.
* *Voting incentives*: Custom amount of tokens deposited by a protocol on a gauge to `veRCT` holders in exchange for their votes.
* *Max Lock*: 2 years.
* *Farming Boost*: This feature has not been included to prevent from the emergence of any profit maxi protocols on top of Reactor. Conversely, a dynamic and decentralized governance over `$RCT` emissions is fostered over time.
* *Flexibility*: `veRCT` positions can be merged, split, and sold on the secondary market.


---

# 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://reactors.gitbook.io/reactor/tokenomics/tokens-rct-verct-rctnft/verct.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.