Developer Docs
  • Overview
  • Setup & Configuration
    • Run a Validator
    • Configuration
    • Disk Usage Optimization
    • State Sync
    • Mempool
    • Validator FAQ
  • Security Essentials
    • Security
    • Tendermint KMS
    • Validator Security Checklist
  • Upgrades Overview
    • Upgrades
    • List of Upgrades
    • Hard Fork Upgrades
    • Manual Upgrades
    • Rollback
  • BitNet Ops Handbook
    • Testnet
    • Mainnet
    • Run an IBC Relayer
Powered by GitBook
On this page
  • Validator Node Operations on BitNet
  • Validator Selection and Staking
  • Slashing and Misbehavior
  • Infrastructure Requirements
  • Recommended Minimum Specifications
  • Community and Visibility

Overview

Validator Node Operations on BitNet

BitNet operates using a modular Layer 1 framework secured through a decentralized network of validators. These validators play a critical role in reaching consensus, securing the network, and processing transactions by proposing and attesting to new blocks.

Validator Selection and Staking

BitNet's consensus layer, built upon CometBFT, relies on a rotating validator set elected based on stake. Validators can bond their own BNC tokens or receive delegations from token holders to increase their total voting power. The top validators, ranked by total stake, participate in block production and consensus voting.

Validators and their delegators are rewarded in BNC tokens through both block provisions and transaction fees. BitNet governance may expand accepted fee tokens in the future, enabling whitelisted assets to serve as fee payment methods. Validators can set commission rates on rewards earned by their delegators.

Slashing and Misbehavior

To maintain the integrity of the network, validators are subject to slashing penalties for misbehavior. This includes double-signing, prolonged downtime, or failing to participate in governance. Slashing results in the loss of staked BNC, including tokens delegated by other users.

Infrastructure Requirements

Validator nodes must be operated on secure, reliable infrastructure with a strong focus on redundancy. Operators are encouraged to run nodes in professional-grade data centers with:

  • Redundant Power & Connectivity

  • Dedicated Firewalls and Network Failovers

  • Enterprise-grade SSD Storage

BitNet is designed to scale efficiently, but validators should anticipate increased resource demands as the network grows. Operators are advised to plan for long-term capacity, including expanded disk storage for blockchain history.

Recommended Minimum Specifications

To run a BitNet mainnet or testnet validator node, the following baseline hardware is recommended:

  • 4+ physical CPU cores

  • 32 GB RAM minimum

  • 500 GB NVMe SSD (fast I/O is critical)

  • 100 Mbps minimum network bandwidth

Supported operating systems include:

Linux (amd64 / arm64)
macOS (x86_64 / arm64)

Community and Visibility

Aspiring validators are encouraged to engage with the BitNet community. Establishing a validator brand—via a dedicated website and active presence on platforms like X (formerly Twitter)—helps delegators make informed staking decisions.

Validators should also participate in BitNet’s governance forums and technical Discord channels to stay updated on network proposals, upgrades, and ecosystem changes.

NextRun a Validator

Last updated 5 days ago