> For the complete documentation index, see [llms.txt](https://docs.harmony.one/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.one/home/network/delegator/redelegation.md).

# Redelegation

To minimize the friction of delegation and allow delegators to easily switch between validators, redelegation feature is supported in Harmony Staking. If a delegator wants to redelegate tokens from one validator to another, he or she can undelegate the tokens which will be locked immediately. After that, any new delegations will try to utilize the locked tokens first and, if not enough, the liquid tokens from the user's wallet. Note the locked tokens are only available for redelegation after the end of the epoch when they were first undelegated. This is to make sure the tokens can still be slashed within the same epoch of undelegation if they are used for malicious double signing.

![Undelegated tokens are available for delegation after the epoch of undelegation](https://miro.medium.com/max/1485/1*0YYTOLOAdHDaccQTrPZGIA.jpeg)

Specifically, if stakers want to redelegate X tokens from validator A to validator B, they can first undelegate the X tokens from validator A and the tokens will be locked immediately. After the end of the epoch, they can send a delegate transaction with X tokens to validator B and the locked tokens will be immediately unlocked and used for the new delegation. Alternatively, If the delegation amount is greater than the locked tokens that’s available for redelegation, the liquid tokens will be used to fill the difference.

With the restoration of 7 epoch locking period and the newly introduced redelegation support, we are bringing back the security guarantee of the original EPoS model without significantly affecting the existing stakers’ workflow. For more discussion and proposal about Harmony network, feel free to write a post at <https://talk.harmony.one/>.


---

# 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.harmony.one/home/network/delegator/redelegation.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.