CLV Documentations
Portal
Portal
  • Welcome to Clover
  • Useful Links
  • CLV Token
  • Quick Start
    • Clover Networks
    • Sakura Networks
    • Using Local Node
    • Using Testnet
      • Create an account
      • Faucet
      • Run a Testnet Node
      • Connect to Testnet
  • Development Guide
    • Introduction
      • Prerequisites
      • Setup environment
    • Using MetaMask
    • Using Remix
    • Using Web3.js
      • Query Balance
      • Send Transaction
    • Counter Tutorial
      • Setup dapp project
      • Setup truffle
      • The Counter Contract
      • Deploy Contract
      • Counter Webapp
  • Clover Wallets & Dapps
    • Clover Extension Wallet
      • Getting Started
      • Switch Networks
      • Add Tokens
      • Send Tokens
      • Cross-Chain Transfer
      • View Seed Phrase
      • Import Account
      • dApp Integration
      • Substrate dApp Integration
      • Solana-dApp-Integration
      • dApp Interaction Protocol
      • Wallet Integration QA
    • Clover Mobile Wallet
    • Clover Web Wallet
      • dApp Integration
    • Clover Assets Explorer
    • Clover Cross-Chain Explorer
  • Maintain
    • Running a validator on Clover Network
    • Running a RPC node
    • Staking on Clover
      • Staking via Apps
      • Staking via Clover Wallet
  • Technical Documentation
    • Web3 compatibility
      • eth_protocolVersion
      • eth_syncing
      • eth_hashrate
      • eth_coinbase
      • eth_mining
      • eth_chainId
      • eth_gasPrice
      • eth_accounts
      • eth_blockNumber
      • eth_getBalance
      • eth_getStorageAt
      • eth_getBlock
      • eth_getTransactionCount
      • eth_getBlockTransactionCount
      • eth_getBlockUncleCount
      • eth_getCode
      • eth_sendTransaction
      • eth_sendSignedTransaction
      • eth_call
      • eth_estimateGas
      • eth_getTransaction
      • eth_getTransactionByBlockHashAndIndex
      • eth_getTransactionByBlockNumberAndIndex
      • eth_getTransactionReceipt
      • eth_getUncle
      • eth_getLogs
      • eth_getWork
      • eth_submitWork
      • eth_submitHashrate
      • eth_subscribe
      • eth_unsubscribe
      • net_version
      • net_peerCount
      • net_listening
      • web3_clientVersion
      • web3_sha3
    • Clover Test Cases
    • Clover EVM
    • Clover Accounts Binding
    • Query Balance
    • Transaction Finality
  • Clover Eco Incentive Program
    • Introduction
    • Clover Developer Incentive Program
    • Virtual Ethereum address binding
    • Clover User Incentive Program
  • Parachain Auction
    • About Polkadot Parachain Auction
Powered by GitBook
On this page
  • Must Read Before Start....
  • Hardware Requirements
  • Prepare Environment
  • Firewall Setup
  • Create Directories
  • Setup Clover Validator Node
  • Create the Compose configure file
  • Bring up the validator node
  • Bond CLV
  • Set the session keys
  • Validate
  • Links
  1. Maintain

Running a validator on Clover Network

PreviousClover Cross-Chain ExplorerNextRunning a RPC node

Last updated 3 years ago

This guide will instruct you how to set up a Clover validator node on Clover networks (Testnet/Sakura/Mainnet).

Must Read Before Start....

Running a validator is a serious thing, you have a lot responsibility for the staked tokens of you and nominators. You take the risk of losing your staked tokens as a slash might happen if your validator node is not properly configured. Please make sure you or your team have the necessary knowledge to run a validator node.

has an awesome introduction of running a validator node on the . As a member of the Polkadot ecosystem, Clover follows the similar process to run and setup a validator node. We may skip some basics steps in this tutorial.

Hardware Requirements

  • CPU - Recent released high end cpu, e.g. Intel 10700/Amd 5800X.

  • Memory - 32GB for Testnet, 64GB for Sakura and Mainnet.

  • Storage - 300GB SSD, Storage usage could increase by time, you might need to increase the capacity as the chain data grows..

  • OS: Linux, Debian/Ubuntu LTS distributions are recommended.

Prepare Environment

We'll use and to run the validator in this guide. You need to install docker and docker-compose firstly. Please follow the installation guide in the docs.

We're using docker to simplify the setup process. You can use the tools which you're familiar with.

Below ports need to be exposed:

  • 30333 - The p2p port of the chain

Create the config and data directories using below command:

sudo mkdir -p /opt/data/
sudo mkdir -p /opt/compose/
# secure the data access
sudo chmod 0700 /opt/data
sudo chmod 0700 /opt/compose 

Currently we only have Clover Testnet(iris) and Clover Mainnet(ivy) launched. Clover Testnet opens for validators to join. Clover Mainnet operates in the POA mode and maintained by 6 nodes belongs to Clover foundation.

Validator Configuration for Clover Mainnet will be updated later once it's ready for staking and validators can join.

Create /opt/compose/docker-compose.yaml and set the content as below:

version: "3.8"
services:
  clover-validator:
    image: "cloverio/clover-ivy:0.1.16"
    restart: always
    command:
      - /opt/clover/bin/clover
      - --chain 
      - /opt/specs/clover-ivy.json  
      - --base-path 
      - /opt/chaindata
      - --validator
      - --name 
      - 🍀clover-validatornode
      - --port 
      - "30333"
      - --ws-port 
      - "9944"
      - --rpc-port 
      - "9933"
      - --rpc-cors=all 
      - --execution
      - wasm
    ports:
      - "30333:30333"
      - "9933:9933"
      - "9944:9944"
    volumes:
      - /opt/data/clover:/opt/chaindata

You can edit the docker-compose.yaml and include your customizations by updating below arguments:

  • --name: The node name of your validator, the name could be found in the telemetry node list.

  • --unsafe-rpc-external: You might need this flag to call the author_rotateKeys api, make sure to remove this flag later on for better security.

  • Ensure enable the --exeuction wasm flag, This is required for all validator nodes.

Use below command to bring up the validator node:

cd /opt/compose # goto the compose file directory
docker-compose up # bring up the validator node in the foreground
## check whether the node starts up normally
## Ctrl-C stop the node
docker-compose up -d # start the validator node in the daemon mode.

You need to check the node logs using docker-compose logs command. Wait until the node is synced and the block numbers syncs with the latest number on the chain.

Firewall Setup

Create Directories

Setup Clover Validator Node

Create the Compose configure file

image: the docker image used to launch the node, for Clover mainnet, use cloverio/clover-ivy:0.1.16.For a full list of clover networks please check out the page.

Bring up the validator node

Bond CLV

Checkout documentation.

Set the session keys

Checkout documentation.

Validate

Checkout documentation.

Links

🛰️
📁
⚙️
📝
🚀
💹
🗝️
🌠
🔱
👉
🛠️
🔧
Polkadot Wiki
Polkadot network
docker
docker-compose
Docker Install Document
Docker-Compose Install Document
Clover Network List
Staking
Polkadot Session Keys
Polkadot Validate
Clover Testnet Apps
Clover Mainnet Apps