> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/guides/stacking/revoking-delegation.md).

# Revoking delegation

I have revoked delegated STX but they remain locked, why?

Once the tokens have been locked by the proof of transfer protocol they will always remain locked for the committed period of time. When you first stacked your STX you will have chosen a number of cycles to Stack for and if you chose to indefinitely Stack. This means that the tokens have been stacked for that many cycles (for example 3) then there is a cooldown cycle and the pool operator will stack the delegated STX again for the next commitment period (i.e. 3 cycles). Once you have send the "revoke" transaction. The pool operator will no longer be able to lock the STX in your account again. You will however have to wait for the remainder of the commitment period to pass.


---

# 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://leather.gitbook.io/guides/stacking/revoking-delegation.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.