> For the complete documentation index, see [llms.txt](https://docs.bitplanet.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitplanet.ai/node-operation/node-operation.md).

# Overview

## Overview

This documentation provides comprehensive guidance for operators running and maintaining Bitplanet's validator nodes. It covers setup, operations, troubleshooting, and emergency procedures for maintaining a healthy validator.

**Target Audience:** Node operators, validators, and infrastructure engineers

## What is a Bitplanet Node?

A Bitplanet node is a server running the `evmd` binary that participates in the Bitplanet network. Nodes maintain a copy of the blockchain, validate transactions, and — if configured as validators — participate in consensus to produce new blocks.

Bitplanet combines three powerful technologies:

* **BitSDK** - Modular blockchain framework with proven governance, staking, and IBC capabilities
* **CometBFT Consensus** - Byzantine Fault Tolerant consensus engine ensuring network security
* **BitEVM** - Full Ethereum Virtual Machine compatibility for running Solidity smart contracts

This hybrid architecture allows Bitplanet to support both native Cosmos modules (like the AI-focused Brahma module) and Ethereum-compatible smart contracts, creating a unique bridge between ecosystems.

## How Bitplanet Consensus Works

Bitplanet uses **Proof of Stake (PoS)** consensus powered by CometBFT:

1. **Validators Stake Tokens** - Lock up BPL tokens as collateral, demonstrating commitment to honest behavior
2. **Block Proposal** - Validators take turns proposing blocks in proportion to their stake
3. **Block Voting** - Other validators vote on proposed blocks through a two-phase commit protocol
4. **Finality** - Once >2/3 of voting power approves, the block is permanently committed
5. **Reward Distribution** - Block rewards and transaction fees are distributed to validators and delegators

This creates **fast finality** and **economic security** (attacking the network requires controlling >1/3 of staked tokens).

## Node Operations Lifecycle

### 1. Setup & Installation

Get your node software ready:

* Install dependencies (Go, Make, system libraries)
* Build the `evmd` binary from source, or
* Use Docker for containerized deployment

### 2. Configuration

Customize your node's behavior:

* Set network parameters (chain ID, denomination)
* Configure P2P networking and peer connections
* Enable APIs (RPC, gRPC, JSON-RPC for EVM)
* Adjust consensus timeouts and gas prices

### 3. Syncing

Connect to the network and catch up:

* Download the genesis file (network's initial state)
* Connect to peer nodes
* Sync the blockchain (hours to days depending on method)
* Use snapshots for faster bootstrapping

### 4. Validation (Optional)

Become an active validator:

* Ensure sufficient stake (50+ BPL minimum, 1,000+ BPL recommended)
* Create and fund validator account
* Submit create-validator transaction
* Monitor signing performance and uptime

### 5. Maintenance

Keep your node healthy:

* Monitor logs and metrics
* Update software during network upgrades
* Manage disk space and resources
* Respond to governance proposals
* Withdraw rewards regularly

## Network Roles & Responsibilities

### For Validators

* **Uptime**: Maintain 24/7 operation with redundancy
* **Security**: Protect validator keys with hardware security modules
* **Governance**: Vote on proposals that shape the network
* **Upgrades**: Coordinate updates during planned hard forks
* **Community**: Communicate with delegators and ecosystem

### For Node Operators

* **Reliability**: Ensure stable infrastructure and connectivity
* **Performance**: Use recommended hardware (SSDs, adequate RAM)
* **Monitoring**: Set up alerts for node health and sync status
* **Backup**: Maintain secure backups of keys and configuration

## Key Benefits of Running a Node

**For Validators:**

* Earn staking rewards (variable APR based on total stake and network conditions)
* Earn commission on delegated stake
* Influence network governance through voting power
* Support Bitplanet's AI economy mission

**For Full Node Operators:**

* Independent access to blockchain data
* Trustless verification of transactions
* Support network decentralization
* Enable application development and services
* Educational experience in blockchain operations

## Common Use Cases

* **Development & Testing** - Run a local node to develop and test smart contracts or applications without network fees.
* **RPC Services** - Operate public RPC endpoints for community applications to query the blockchain.
* **Archival Nodes** - Maintain complete historical data for block explorers, analytics, or auditing.
* **Validator Operations** - Participate in consensus, earn rewards, and help secure the network.
* **Private Networks** - Deploy isolated testnets for enterprise use cases or protocol research.

## Documentation Sections

This operator documentation is organized into the following sections:

1. [**Hardware Requirements**](/node-operation/hardware-requirements.md) - System specifications and prerequisites
2. [**Setup & Configuration**](/node-operation/setup-configuration.md) - Installation and node configuration
3. [**Operations**](/node-operation/operations.md) - Daily operations, backups, and monitoring
4. [**Troubleshooting**](/node-operation/troubleshooting.md) - Common issues and solutions
5. [**Runbooks**](/node-operation/runbooks.md) - Step-by-step procedures for critical operations
6. [**Additional Resources**](/node-operation/additional-resources.md) - Quick reference and support links