Dhive Docs
  • Welcome to Dhive
  • Dhive L1
  • Dhive EVM "CLI"
    • Client Configuration Guide
    • Using Dhive with Docker
    • Running a Single Node Local Network
  • Loyalty Program
    • Tokenization of loyalty Program
  • Redeemable NFTs
  • Onchain Reviews
  • Dhive Bridging
  • Dhive Amm
    • Overview
    • Get Started
    • Create A Wallet
    • Get DVI 20 Tokens
    • Token Swaps
  • Liquidity Pools
  • Add/Remove Liquidity
  • Contracts
  • Dhive rNFT Marketplace
    • Overveiw
  • Tokenize Your Business
  • List Product "rNFT"
  • Buy rNFT
  • Redeem rNFT
  • Cashback Mechanism
  • Contracts
  • Post A Reveiw
  • For Validators
    • Overview
    • Run a Validator
    • Configuration
    • Disk Usage Optimization
    • State Sync
    • Mempool
  • Tokenomics
    • Overview
    • DFuel Tokenomics
    • Dhive Validator Token Tokenomics
  • Others
    • Dhive Roadmap
Powered by GitBook
On this page

Was this helpful?

  1. For Validators

Overview

Validating on Dhive

Dhive is built on CometBFT, which operates through a network of validators responsible for committing new blocks to the blockchain. These validators engage in the consensus protocol by broadcasting votes that contain cryptographic signatures, each signed with the validator's private key.

Becoming a Validator

Prospective validators can bond their own staking tokens and receive delegated stakes from token holders. Dhive's native token, DHIVE, plays a crucial role in this process. Initially, Dhive launched with a total of 150 validators. The active validator set comprises the top 150 candidates with the highest stake delegation.

Validators and their delegators earn DHIVE as block rewards and transaction fees through the execution of the Tendermint consensus protocol. Additionally, validators can set commission rates on the fees earned by their delegators as an added incentive.

Potential Risks

Validators must adhere to best practices to avoid penalties. Actions such as double signing, prolonged downtime, or failure to participate in governance may result in slashing of their staked DHIVE, including that of their delegators. The severity of the penalty depends on the nature of the violation.

Infrastructure and Hardware Requirements

Validators must establish secure physical operations with restricted access. A recommended starting point is co-locating in secure data centers with redundant power, connectivity, and storage backups. It is advisable to have multiple redundant networking components for fiber, firewall, and switching, along with small servers featuring redundant storage and failover mechanisms. While initial hardware requirements may be modest, they are expected to grow as the network scales. Sufficient bandwidth, CPU, and memory will be essential, and large storage capacity is recommended for maintaining blockchain history over time.

Supported Operating Systems

Dhive officially supports macOS and Linux on the following architectures:

  • darwin/arm64

  • darwin/x86_64

  • linux/arm64

  • linux/amd64

Minimum System Requirements

To operate a validator node on the mainnet or testnet, the following minimum hardware specifications are required:

  • At least 4 physical CPU cores

  • A minimum of 500GB NVMe SSD storage (high I/O speed is critical)

  • At least 32GB of RAM

  • Minimum 100Mbps network bandwidth

As the network scales, these requirements may increase. Validators should plan for future upgrades accordingly.

Getting Involved

Tip: Seek legal counsel before operating a validator.

To establish credibility, validators should create a dedicated website and social media presence (e.g., X, formerly Twitter) and announce their intent to become a validator on Discord. Transparency is key, as delegators will seek reliable information about the entity managing their staked DHIVE.Either start typing below, or press / to see a list of the blocks you can insert into your page.

PreviousPost A ReveiwNextRun a Validator

Last updated 3 months ago

Was this helpful?