XOLIX Explorer Logo

How to Become a XOLIXBlock Validator

A step-by-step guide to securing the network and earning rewards.

Introduction: The Role of a Validator

Validators are the backbone of the XOLIXBlock network. They are responsible for running the node software, participating in the consensus mechanism, producing new blocks, and verifying transactions. In return for their service, validators earn staking rewards and a portion of the network's transaction fees.

Our network uses a unique combination of Stochastic Proof-of-Stake (SPoS) and Neural Consensus, which means validators are chosen based on a fair, randomized lottery weighted by their stake and their AI-determined performance score. Maintaining high uptime and performance is crucial for maximizing rewards.

Step 1: Meet the Prerequisites

A. Minimum Staking Requirement

To become a validator, you must meet the minimum staking threshold. The current threshold is **2,500,000 FLUID**. This stake acts as a security deposit, ensuring validators act in the network's best interest. This value can be changed by the administrator via the Node Controls dashboard.

B. Hardware Requirements

While the network is efficient, running a stable and performant validator node requires dedicated hardware. We recommend the following minimum specifications:

  • CPU: 4+ Cores, 3.0GHz or higher
  • RAM: 16 GB DDR4
  • Storage: 1TB NVMe SSD (Solid State Drive)
  • Network: 100 Mbps, stable, low-latency internet connection

Step 2: Set Up Your Node

First, you need to compile and run the XOLIXBlock node software on your dedicated server.

  1. Clone the project repository from our official source.
  2. Navigate to the node's source directory:
    cd src/lib/xolix-block/xolix_node
  3. Build the node software in release mode. This will compile the Rust source code into a highly optimized binary.
    cargo build --release
  4. Run the node for the first time. It will initialize its database and begin syncing with the network.
    ./target/release/xolix_node

    This will start the node, which listens for RPC requests on `http://localhost:3030`. The node must be running continuously for you to be an active validator.

Step 3: Generate Your Validator Key

Your validator needs a unique, secure keypair to sign blocks. This is separate from your personal wallet address. Use our official wallet CLI to generate this key.

The CLI tool is part of the main project source code, which you will have after cloning the repository. Navigate to its directory and run the command.

  1. Navigate to the wallet CLI directory from the project root:
    cd src/lib/xolix-block/xolix_wallet
  2. Run the `generate` command using Cargo:
    cargo run -- generate
  3. The tool will output your **Public Key (Address)** and your **Private Key (Secret)**.
    CRITICAL: Securely back up your **Private Key**. If you lose it, you will lose control of your validator and any associated funds. Do not share it with anyone.

    The **Public Key** is your validator's address. You will use this in the next step.

Step 4: Stake Your Tokens

The final step is to stake the required 2,500,000 FLUID to your validator's public address. This action registers your node as an active validator on the network.

  1. Go to the official Staking page in the XolixScan explorer.
  2. Connect the wallet that holds the FLUID you wish to stake.
  3. In the "Stake Your Tokens" section, enter `2500000` as the amount.
  4. Click the "Stake" button and approve the transaction in your wallet.

Once your transaction is confirmed, the network's consensus layer will recognize your stake. Your node will be added to the active validator set and will become eligible to be selected for block production by the SPoS algorithm in the next epoch.

Step 5: Maintaining Your Validator

Congratulations! You are now a XOLIXBlock validator. To maximize your rewards and contribute to network health, you must:

  • Ensure your node remains online and connected 24/7.
  • Monitor your node's performance and logs for any issues.
  • Participate in governance votes on protocol upgrades.
  • Keep your server and node software updated as new releases are announced.