> For the complete documentation index, see [llms.txt](https://docs.flex.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flex.trade/tokenomics/usdesfdx-vesting-schedule.md).

# $esFDX Vesting Schedule

esFDX's holders can choose to vest their esFDX tokens to receive FDX. **esFDX vests linearly and will take one year** to fully convert to FDX tokens.

* Users can claim vested esFDX at anytime
* Users will be able to cancel vesting at anytime. Unvested esFDX tokens can be returned to staking for rewards

**Example:**

1. Let's assume Alice has 100 esFDX & Alice chooses to vest her entire 100esFDX holdings.
2. After 26 weeks of vesting (0.5 year), Alice can now claim 50 FDX tokens while the remaining 50 esFDX remain to be converted.
3. At that time, if Alice chooses to cancel her vesting. She can claim the following:
   1. 50 FDX tokens
   2. 50 esFDX tokens will be returned to staking


---

# 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.flex.trade/tokenomics/usdesfdx-vesting-schedule.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.