> For the complete documentation index, see [llms.txt](https://qubetics.gitbook.io/qubetics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qubetics.gitbook.io/qubetics-docs/getting-started/validator-application-user-guide/validators/deactivated-validator-tab.md).

# Deactivated Validator Tab

The Deactivated Tab on the Validators Page of the Qubetics Validator interface provides critical information about validators who are no longer actively participating in the network. It offers insights into their past performance, commission rates, total stake, and delegator count, helping users make informed staking decisions. This section also enables delegators to review validators for potential future staking opportunities and allows validators to analyze their deactivated status for potential reactivation. By ensuring transparency and accessibility, the Qubetics ecosystem empowers both delegators and validators to contribute effectively to network participation and growth.

<figure><img src="https://2711441218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F36u23gOZEZc21qS2BbPV%2Fuploads%2FgLISPqJQgCJZD89gSucm%2Fimage.png?alt=media&amp;token=89d3f51b-3985-4e84-83b9-235f580b8e16" alt=""><figcaption></figcaption></figure>

### Validators Table Overview

The Validators Table offers a comprehensive view of all validators in the network, displaying essential details in organized columns. This information helps both delegators and validators assess performance, trustworthiness, and staking opportunities.

* **Sr.No.**\
  Each validator is assigned a unique serial number to make navigation and identification straightforward.
* **Name**\
  The validator's name *(e.g., Shinobi Validator, Sherlock Nodes)* provides an easily recognizable identity, allowing delegators to quickly locate and evaluate specific validators.
* **Validator Address**\
  The blockchain address associated with the validator *(e.g., 0x47865...46845)*. Clicking on the address reveals detailed metrics, such as the validator's performance, transaction history, and operational activities.&#x20;
* **Status**\
  The status column indicates the validator's current role in the network:
  * **Active:** The validator is actively participating in block validation and consensus.
  * **Inactive:** The validator is not currently validating but remains registered within the network.
  * **Deactivated:** The validator has been removed from active participation, often due to non-compliance or insufficient self-stake.
* **Total Stake**\
  This metric displays the total tokens staked with the validator, including both the validator's self-stake and delegator contributions.&#x20;
* **Commission**\
  The percentage of rewards retained by the validator for their validation services.&#x20;
* **Self-Stake**\
  This is the amount of tokens staked by the validator themselves to maintain their status.&#x20;
* **Delegators**\
  The number of delegators who have chosen to stake their tokens with this validator *(e.g., 2)*.&#x20;


---

# 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://qubetics.gitbook.io/qubetics-docs/getting-started/validator-application-user-guide/validators/deactivated-validator-tab.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.