> 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.md).
# Validator Application: User Guide
Official guide to onboard as a validator in the Qubetics network using the Qubetics validator application.
Validators play an important role in ensuring the security of a blockchain network and facilitating the creation of new blocks. They also participate in the consensus process with other validators.\
This document is intended to guide users through the process of becoming a validator on the Quebtics network.
**Before proceeding, please ensure you have successfully set up your Quebtics Validator Node.**
### Who are validators?
A validator is a participant in a network who is responsible for maintaining the integrity of the distributed ledger by validating transactions and adding them to the blockchain. They are in charge of creating new blocks, as well as ensuring the network's finality and, ultimately, its security.
\
Validators are incentivized to participate in the network through the use of a cryptocurrency or tokens ***(TICS Tokens in our chain)*** and are required to ***"stake"*** a certain amount, min. **100 TICS** of tokens to become a validator on **Testnet** and **25000 TICS** on **Mainnet.**
\
The stake acts as a guarantee of good conduct, and whenever they make a mistake, this stake is slashed. In contrast, when they follow the rules, they are generously compensated.\
Running a validator on a live network involves a significant amount of responsibility. They will be made responsible for not just their stake but also for the stake of their delegators. Their money and reputation will be affected if validators make a mistake and get slashed.
{% hint style="info" %}
**Qubetics Blockchain (Mainnet) uses a two-epoch system with its use cases:**\
\
Daily or 24 Hours (86400 seconds): Distribute staking rewards daily
* Trigger inflation/minting
* Update fee splits
* Perform daily IBC housekeeping
* Prune the temporary state
\
Weekly or 7 Days (604800 seconds):\
Run expensive processes less often (e.g., slashing checks, validator jailing)
* Rotate the validator performance evaluation
* Payout long-term incentives (e.g., liquidity mining)
* Reset TWAP (Time-Weighted Average Price) if used
* Snapshot state for governance or analytics
{% endhint %}
**Link:**
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://qubetics.gitbook.io/qubetics-docs/getting-started/validator-application-user-guide.md?ask=&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 `build a script that syncs our docs to a CMS` 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.