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

# Locking

EPX holders can lock their EPX to receive vlEPX. The longer you lock EPX, the more vlEPX you'll receive. vlEPX allows users on Ellipsis 2.0 to:

* Vote on incentive distribution between pools;
* Receive platform fees;
* Boosting EPX rewards;
* And nominate new pools for a vote towards receiving EPX rewards.

Some things to note:

* Users can have multiple locks per account.
* Lockers *do not* have to vote. Lockers can claim platform fees even if they do not vote.
* Ellipsis 2.0 works in a week long epoch, starting at 00:00 Thursday, UTC, every week. This means that every week your lock declines by one week and voting starts anew.
* Locker rewards are paid out from the previous week's fees. Every Thursday a new balance of fees streams out to users who were locked during that previous week.&#x20;

### Locking EPX

Locks can last from 1 to 52 weeks; longer locks mean more vote weight and a higher share of fees.

![Lock EPX to receive vlEPX](/files/zMgzSl7HmEngcycoNbAZ)

Important things to know about locks:

1. Locks that are less than 52 weeks can be extended to the 52-week maximum.&#x20;
2. Expired EPX locks must be claimed before you can withdraw your EPX. Released EPX is then streamed out over a period of 7 days. During those 7 days released EPX can be claimed at any time.


---

# 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.ellipsis.finance/the-epx-token/locking.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.
