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

# $IDLE

### **stkIDLE**&#x20;

Staking allows users to lock their $IDLE for a flexible period (up to 4 years) in return for a series of benefits.  You could find more details on [IDLE documentation ](https://docs.idle.finance/governance/idle-staking)

### ve3IDLE

**ve3IDLE is tokenised version of stkIDLE**

veToken Finance enable users to deposit $IDLE and converted to ve3IDLE. And users are able to stake and unstake ve3IDLE. By staking ve3IDLE, Users are able to get the same rewards from stkIDLE, and additional rewards from IDLE Farms. And you could exchange ve3IDLE for IDLE at the secondary markets.

In the meanwhile, veToken Finance locks $IDLE permanently, which allows the system is able to get boosted rewards and voting ability on gauge weights.&#x20;


---

# 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.vetoken.finance/vetoken-finance/for-usdveasset-stakers/usdidle.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.
