> For the complete documentation index, see [llms.txt](https://cintara.gitbook.io/testnet.cintara.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cintara.gitbook.io/testnet.cintara.io/basics/how-to-become-a-validator.md).

# How to become a Validator

### **1. What Are Validators?** <a href="#qcew3wjecv1c" id="qcew3wjecv1c"></a>

Validators are the backbone of the Cintara blockchain network. They are trusted participants who help maintain the network by validating transactions, producing new blocks, and securing the blockchain. Validators play a crucial role in maintaining decentralization, security, and trust in the Cintara ecosystem.

Validators **run special nodes** called validator nodes that verify and confirm transactions. In return for their work, validators earn rewards in the network’s native token, **CINT**. However, to be a validator, users must **stake CINT tokens** as collateral, which can be partially forfeited if they act maliciously or fail to follow the protocol rules.

### **1.1 Responsibilities of Validators** <a href="#qs2s2hnsbbs" id="qs2s2hnsbbs"></a>

Validators must carefully fulfill these key responsibilities:

1. **Maintain Network Uptime and Reliability**
   * Keep the validator node running 24/7 with minimal downtime.
   * Ensure high availability to avoid penalties and maintain consistent transaction validation.<br>
2. **Secure the Network**
   * Protect the validator node from unauthorized access and cyberattacks.
   * Secure private keys and sensitive data using encrypted backups and best security practices.<br>
3. **Validate Transactions and Produce Blocks**
   * Verify all incoming transactions for correctness and legitimacy.
   * Participate in block creation and consensus processes to keep the blockchain running smoothly.<br>
4. **Follow Governance and Protocol Rules**
   * Abide by Cintara network governance policies and protocol standards.
   * Act ethically and honestly to maintain the community’s trust and network integrity.<br>
5. **Manage Delegations Responsibly**
   * Validators are accountable not only for their own stake but also for the tokens delegated to them by others.
   * Ensure transparent communication and reliable operation to maintain delegator confidence.

### **2. Pre-Login Technical Setup** <a href="#id-4c9kvv634sjd" id="id-4c9kvv634sjd"></a>

#### **Step 1: Install Required Software** <a href="#nou7krxpm1oi" id="nou7krxpm1oi"></a>

Ensure your server has the following tools installed:

| **Tool**        | **Purpose**               |
| --------------- | ------------------------- |
| bash            | Command-line shell        |
| go              | Go programming language   |
| jq              | JSON processor            |
| wget            | File download utility     |
| unzip           | Archive extractor         |
| build-essential | Compilation tools (Linux) |

#### **Step 2: Hold and Stake CINT Tokens** <a href="#fgwr2tl7a658" id="fgwr2tl7a658"></a>

* Minimum **100 CINT tokens** required for validator activation.
* Tokens must be bonded/staked as economic collateral.
* Misbehavior may result in **slashing** (loss of tokens).<br>

#### **Step 3: Set Up and Run Your Validator Node** <a href="#id-87gw7r3xg0gs" id="id-87gw7r3xg0gs"></a>

* Follow official setup instructions to install node software.
* Synchronize your node with the Cintara blockchain.
* Secure private keys and ensure 24/7 uptime.<br>

#### **Step 4: Participate in Governance** <a href="#asdk24jhwm18" id="asdk24jhwm18"></a>

* Vote on proposals using your validator address.
* Upgrade your software as needed to comply with new protocol rules.
* Maintain community transparency and trust.

### **3. How to Become a Validator on Cintara** <a href="#id-558rsine8zyq" id="id-558rsine8zyq"></a>

#### **Step 1: Connect Node** <a href="#qyzxyn1tgigu" id="qyzxyn1tgigu"></a>

The user must enter the node IP address and port (**Format:** *protocol://IP:port)* in the Node information section and click on **Submit**.

If the system firewall is enabled, the Node host must make the following ports (TCP) accessible:

* 9944 (for Web Socket)
* 9933 (for RPC)

#### **Step 2: Log in** <a href="#engix86o6wl5" id="engix86o6wl5"></a>

* Once a node is successfully connected
* Enter Mnemonics
* Click on ‘Login’ button.

![](/files/ia80HGq2x4jxsNmOK5D2)

#### **Step 3: View Dashboard** <a href="#dklsz3f2jyej" id="dklsz3f2jyej"></a>

* After a successful login, the user is redirected to the dashboard page.
* The dashboard page shows the status of the validator.
* The status could be Active, Inactive, or Waiting.
* In case the user has not completed the process of becoming a validator, the status will be shown as "-".

![](/files/6nKfPUpgOqC74aR5qdwl)

#### **Step 4: Set Up as A Validator** <a href="#qkl8rlmrn9c" id="qkl8rlmrn9c"></a>

![](/files/FYARUIlj9a3f3VUgwT2S)

* Click on the **‘Setup as a Validator’** button, and the user will see the following mandatory fields:
  * Name
  * Description
  * Website
  * Identity
  * Security Contact
* ‘Next’ button: Once you click on it, the user will see the next screen to see other fields

![](/files/cqBKn6XxW0Fcg1cqODVb)

* The following fields can be here:
  * Stake/Bond Amount
  * **Commission (%)**: What the validator charges (a percentage of your staking rewards).
  * **Max Rate**: The highest commission they'll ever charge.
  * **Initial Rate**: The commission they start with.
  * **Max Change Rate**: How much they can change their commission at a time (prevents sudden hikes).
* Click on ‘Bond and Validate’ to set up as a Validator.

**Note:** *The minimum acceptable amount for a validator bond is 100 CINT Coin.*

* The higher the amount of CINT Coins staked, the higher the chances of becoming a validator.
* The commission is the percentage amount that is earned by the validators from the delegator's rewards.

#### &#x20;<a href="#e4y9cxptlxjc" id="e4y9cxptlxjc"></a>

#### **Step 5: Authorizing** <a href="#i8dabi9ft6ho" id="i8dabi9ft6ho"></a>

1. Review and confirm the Stake amount and Commission settings.
2. Enter mnemonics to sign the transaction.
3. Click Sign and Submit.
4. A small transaction fee will be deducted.
5. Upon confirmation, validator status will update, and you'll be redirected to the dashboard.

![](/files/BuFjGtps16gL1XjfG090)<br>

### **4. Summary** <a href="#id-3f0birqjyhc1" id="id-3f0birqjyhc1"></a>

| **Aspect**               | **Description**                                                 |
| ------------------------ | --------------------------------------------------------------- |
| **Who are Validators?**  | Trusted nodes validating transactions and securing Cintara.     |
| **Key Responsibilities** | Uptime, security, block production, governance compliance.      |
| **Prerequisites**        | Linux server, 4GB+ RAM, 20GB+ storage, stable internet, tools.  |
| **Stake Required**       | Minimum 100 CINT tokens to be staked as collateral.             |
| **How to Start?**        | Setup server → Install tools → Stake tokens → Run node → Govern |


---

# 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://cintara.gitbook.io/testnet.cintara.io/basics/how-to-become-a-validator.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.
