> For the complete documentation index, see [llms.txt](https://docs.ethena.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethena.fi/video-guides/how-to-un-lock-positions.md).

# How to \[Un]lock positions

Locking tokens and positions enables holders to receive the protocol's generated rewards

Users in permitted jurisdictions can [**lock** & **unlock**](https://app.ethena.fi/overview) positions with Ethena via the UI.

Using the UI, the **locking & unlocking** positions user workflow is:

1. The user requests to **lock/unlock** positions via the dApp interface by clicking "Lock"/"Unlock", which pops up their selected wallet to sign the requested transaction.
2. After the user signs the transaction with their wallet, the transaction is submit to the blockchain, if successful, the cooldown period starts.
3. Once the cooldown period ends, the user now needs to click on "Withdraw" and sign a second transaction.
4. Upon successful confirmation of the transaction, the user receives unlocked tokens.

#### Important to Note

* There is a cooldown period of 7 days after unlocking *USDe, USDe* will be available to withdraw after  that period.
* There is a cooldown period of 7 days after unlocking *sENA, sENA* will be available to withdraw after  that period. This is in addition to the 7 day sENA unstaking cooldown.
* There is a cooldown period of 21 days after unlocking LP tokens, these LP tokens will be available to withdraw after  that period.  Some LP tokens have no cooldown and can be withdrawn immediately.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ethena.fi/video-guides/how-to-un-lock-positions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.