How to Setup a Node

This guide outlines the step-by-step process for installing, configuring, and running a validator node on the Cintara blockchain testnet using the cintara_ubuntu_node.sh script. Please follow the instructions carefully to ensure a successful setup and participation in the Cintara testnet.

Prerequisites

1.1 System Requirements

  • Operating System: Ubuntu 22.04 LTS

  • Memory: Minimum 4 GB RAM

  • Disk Storage: At least 20 GB of available space

  • Network: Stable and high-speed internet connection

1.2 Required Tools and Dependencies

Ensure the following dependencies are installed:

  • Go (Install via install go.sh)

  • jq

  • bash

  • wget

  • unzip

  • build-essential

These dependencies are automatically installed by the cintara-testnet-script.sh.

2. Environment Preparation

Step 1: Run with Sudo Privileges

The script must be executed with root privileges to avoid permission issues.

sudo su

Step 2: Clone the Repository

git clone https://github.com/Cintaraio/cintara-testnet-script.git cd cintara-testnet-script

3. Node Installation and Setup

  1. Execute the Script

Run the script to install required packages and initialize the validator node.

./cintara_ubuntu_node.sh.

  1. Prompts During Installation

  2. Node Name: Enter a unique identifier for your node.

  3. Keyring Password: Set a secure alphanumeric password. You will be required to enter this password during key operations.

  4. Overwrite Configurations: If a previous setup is detected, choose y to overwrite or n to retain the existing setup.

  5. Key Backup: Save your key mnemonics and credentials securely. These are critical for node access and recovery.

4. Post-Installation Verification

  1. Validate Genesis File

Verify the integrity of the genesis file: cintarald validate-genesis --home /data/.tmp-cintarald

  1. Review Node Information

After installation, the following details will be displayed:

  • Tendermint Public Key

  • Bech32 Address

  • Node ID

Important: Save these details for future reference.

5. Running the Cintara Node

The script sets up the node as a systemd service.

Manage the Node Service

  • Start the Service

  • Check Service Status

  • Enable Auto-Start on Boot

6. Configuration Settings

The configuration files are located at: Swift /data/.tmp-cintarald/config/

Key Settings Applied by the Script

  • Timeouts: Optimized for network performance.

  • Gas Prices: Set to 0.25 CINT

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

Adding or Modifying Peers

To add persistent peers: nano /data/.tmp-cintarad/config/config.toml

Locate the persistent_peers field and add your desired peer addresses.

7. Troubleshooting

Common Issues and Solutions

  • Missing Dependencies: sudo apt-get install -y jq build-essential wget unzip

  • Service Not Starting: Check logs for more information: sudo journalctl -u cintarachain.service -f

  • Genesis Validation Failure: Ensure that the genesis file matches the expected format and contents of the Cintara testnet.

  • Permission Errors: Run the script with execution permission: chmod +x cintara_ubuntu_node.sh

8. Maintenance

  1. Restart the Node

“sudo systemctl restart Cintarascan chain.service”

  1. Stop the Node

  2. Validator Cooldown Period After Stopping Validation If a validator is stopped or unbonded (either manually or due to an issue), there is a mandatory cooldown period of 30 minutes before it can be re-initialized or re-setup as an active validator on the network. Note: This restriction helps ensure stability and prevents rapid validator switching or abuse within the consensus mechanism.

  3. Validator Inactivity Due to Delegation Removal If all delegators remove their stake from a validator (i.e., undelegate their CINT tokens), the validator will automatically become inactive. This status change occurs because the validator no longer meets the minimum stake requirement to participate in the consensus process. To become active again, the validator must receive new delegations that satisfy the minimum stake threshold.

3. Running a node on Windows comes with several challenges:

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

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

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

  4. No Systemd Support: Systemd, a tool commonly used to manage Cintara nodes on Linux, isn’t natively supported on Windows.

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.

PreviousWelcome to CintaraNextHow to become a Validator

Last updated