To join the Qubetics network as a validator, users must meet specific system requirements, install essential tools to run a validator node, and fulfill staking requirements. Below is a detailed guide to help become a validator in Qubetics ecosystem:

System Pre-Requisites

To ensure optimal performance and reliability as a validator, users need to have a dedicated server with the following computational resources:

• Operating System: Ubuntu 22.04 or a compatible Linux distribution.

• Memory: At least 4 GB of RAM to handle network demands.

• Storage: A minimum of 20 GB of available disk space to store Qubetics chain data and logs.

• Internet Connection: A stable, high-speed internet connection would be required to maintain a consistent node performance and uptime.

• Server Setup: You can set up your server either on a cloud platform or on your local system to host the validator node.

Software and Tool Installation

The following tools must be installed on the system to operate as a validator on the Qubetics network:

• Bash: Command-line shell for script execution.

• Go: Install a version compatible with the Cosmos SDK requirements.

• jq: A lightweight and flexible command-line JSON processor.

Make sure all tools are properly installed and configured before proceeding to node setup on the Qubetics chain.

Minimum TICS Holdings

To participate as a validator in the Qubetics network, users must hold a minimum balance of 100 TICS coins in their wallet. This balance is critical for the following:

• Staking Requirements: Validators must stake TICS coins to join the network and participate in transaction validation.

• Economic Security: Staked tokens serve as collateral, ensuring validators act in the best interest of the Qubetics network. Validators are rewarded with TICS tokens for adhering to protocols, but any mistakes or rule violations can result in slashing their stake. Beyond their own tokens, validators are also accountable for those delegated to them, making reliability and integrity essential. This dual responsibility highlights their critical role in maintaining network security and safeguarding the community's trust.

Steps to run a Validator Node

Here is the step-by-step guide to run a Qubetics Validator Node:

Responsibilities of Validators

1. Maintain Uptime

• 24/7 Operations: Keep your node online and fully operational at all times to avoid penalties and ensure consistent participation.

• Redundancy: Implement backup systems to minimize downtime due to hardware or network failures.

2. Secure the Network

• Node Security: Follow best practices to protect your node from unauthorized access and attacks.

• Private Keys: Safeguard your private keys securely in encrypted backups.

3. Adhere to Governance Policies

• Compliance: Follow the governance rules and protocol standards of the Qubetics network.

• Ethical Practices: Ensure fair and honest participation to maintain the integrity of the Qubetics network ecosystem.

How to onboard as a Validator

Here is the link with a step-by-step guide to onboarding as a validator on Qubetics Validator:

Prerequisites

System Requirements

• Operating System: Ubuntu 22.04

• Memory: At least 4GB RAM

• Storage: Minimum 20GB available disk space

Tools and Dependencies

Ensure the following tools are installed:

• Go ( by running the install_go.sh script )

• Jq

• Bash

All of these installations are already covered in the qubetics-testnet-script.sh script.

Step 1: Prepare Your Environment

1. Run as Root or with Sudo Privileges: Ensure the script is executed with root privileges. If not, you may encounter permission issues.

2. Clone the Repo: Clone the repository and change into the directory.

Step 2: Execute the Script

Run the Script

Execute the script to install the required components and set up the node.

• The script prompts for the node name; please provide it.

• The script prompts the user to set up a password for the keyring so that the keys are stored securely.

• Set a secure numeric/alphanumeric password and provide it whenever prompted.

Key Configuration Prompts

• If a previous node configuration exists, you will be prompted to overwrite it. Choose y to overwrite or n to retain the existing setup.

• Save the generated keys and mnemonics securely when prompted. These are essential for accessing your node.

Step 3: Verify Installation

1. Validate Genesis: Ensure the genesis file is properly configured.

1. Display Node Information: After setup, the script displays important node details:

• Tendermint Public Key

• Bech32 Address

• Node ID

Record these details for future reference.

Step 4: Start the Node

The script automatically sets up and starts the node as a system service.

Manage the Node Service

• Start the Service:

• Check the Service Status:

• Enable the Service to Start on Boot:

Additional Configurations

Update Configurations

The script automatically modifies configuration files located in /data/.tmp-qubeticsd/config/

• Timeout Settings: Adjusted for optimal performance.

• Gas Prices: 0.25 TICS.

• Networking: Configured to listen on all interfaces (0.0.0.0).

Persistent Peers

The script includes default persistent peers to facilitate P2P communication. To add or modify peers, edit the config.toml file.

Troubleshooting

Common Issues

1. Dependency Errors: Ensure all dependencies (e.g., jq, go) are installed before running the script.

1. Service Not Starting: Check logs for detailed error messages:

1. Genesis File Validation Failed: Verify the Genesis file contents and ensure they match the required network configuration.

2. Permission Denied: Please verify that you have completed all the required steps and granted the necessary permissions to the script using the chmod command.

Maintenance

Restart the Node

Stop the Node

Qubetics nodes work best on Linux and macOS. While you can technically run a node on Windows, it’s not recommended for production use. Most validators and node operators prefer Ubuntu or other Linux systems because they are stable, secure, and fully compatible with the Cosmos SDK. MacOS is fine for local development but isn’t used for production nodes. Running a node on Windows comes with several challenges:

• Limited Compatibility: Qubetics node uses Cosmos SDK tools and scripts.These are designed only for Linux/macOS.

• Performance Issues: Windows handles processes and networking differently, which can lead to instability.

• Dependency Problems: Setting up qubetics node on Windows requires extra steps, like using WSL2 (Windows Subsystem for Linux 2).

For the best experience:

• Use Linux (Ubuntu 22.04 LTS is recommended) for development, testnets, and production.

• macOS is okay for local testing.

• If you’re on Windows, use WSL2 (Windows Subsystem for Linux 2) instead of running the node natively.