> For the complete documentation index, see [llms.txt](https://docs.veno.finance/veno-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veno.finance/veno-finance/protocol/reservoir.md).

# Reservoir

Reservoir carries dual functionality and is both Veno’s reward participation and insurance module. Users can lock VNO to receive CRO/ATOM rewards on Cronos or ETH rewards on zkSync Era here. Users can choose between lock durations of 3-months, 12-months, 48-months, and 96-months to lock their VNO. The longer the lock duration and/or larger the quantity locked, the larger proportion of rewards will be shared to the users.

On Cronos, Veno aims to provide a sustainable 50% share of validator rewards (in CRO) to VNO stakers in the Reservoir. The validator commission on CRO staking yield is 10%, and Veno does not take any additional commission on the staking yield. On zkSync Era, we provide 50% share of the commission on ETH rewards to VNO stakers in Reservoir.

In return, Reservoir VNO stakers also bear the risk of a slashing penalty that could cause a loss in users’ CRO; in such situations, Veno will draw down on any accrued rewards in CRO from its own treasury, and channel future rewards sharing of the Reservoir (if required) to repay affected users until the full damaged is covered.

Below shows the multiplier amount corresponding to different vaults:

<table><thead><tr><th width="122">Vault</th><th width="168">3-month Lock</th><th width="165">12-month Lock</th><th width="173">48-month Lock</th><th>96-month Lock</th></tr></thead><tbody><tr><td>Multiplier</td><td>3x</td><td>12x</td><td>48x</td><td>96x</td></tr></tbody></table>


---

# 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.veno.finance/veno-finance/protocol/reservoir.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.