> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/learn/about-validators/how-to-stop-being-a-validator.md).

# How to Stop Being a Validator

Steps to decommission a Chiliz Chain validator node: clean shutdown, CHZ unstaking with 3-day cooldown, delegator notification, and Governance dApp deactivation.

You can stopping acting as a Chiliz Chain validator anytime you want. The process is straightforward when done responsibly, and it ensures that the network remains secure and stable.

Here's how you can stop being a validator:

1. Shut down your node:
   1. If you’re running your own validator node, ensure a clean shutdown to avoid unnecessary errors or penalties.
   2. Disconnect your node from the network after completing all obligations.
2. Unstake your CHZ:
   1. Access the [Chiliz Governance dApp](https://governance.chilizchain.com/staking).
   2. Navigate to the section where you manage your validator account.
   3. Initiate the process to unstake your CHZ. Keep in mind that unstaking may involve a cooldown period (up to 3 days) during which your CHZ will be locked before becoming available for claiming.
3. Notify delegators (if applicable):
   1. Inform any delegators staked to your validator node about your intention to stop operating as a validator. This allows them to reallocate their CHZ to other validators, and avoids disrupting their rewards.
4. Terminate your validator status
   1. Follow the specific steps outlined in the Governance dApp to deactivate your validator status.


---

# 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.chiliz.com/learn/about-validators/how-to-stop-being-a-validator.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.