🌐 System Overview

Three-Tier Architecture

  • Validator: Network coordination and scoring validation
  • Miner: Resource aggregation and Bittensor network interface
  • Worker: Hardware monitoring and compute task execution
┌────────────────────────┐ ┌───────────────────┐ │ Validator │ Encrypted │ Miner │ │ (Bittensor) │ ←── Communication ─── │ (Bittensor) │ │ │ (via bittensor) │ │ │ • Challenge Creation │ │ • Worker Mgmt. │ │ • Score Validation │ │ • Resource Agg. │ │ • Weight Calculation │ │ • Task Routing │ └────────────────────────┘ └───────────────────┘ ↑ │ WebSocket │ ┌───────────────────────┐ │ Worker(s) │ │ │ │ • System Monitoring │ │ • Challenge Execution │ │ • Compute Tasks │ └───────────────────────┘

📊 Scoring System

Miners earn rewards through a sophisticated dual-factor scoring system designed to incentivize both active compute provision and network participation.

Score Components (Weighted)

  • Lease Revenue (70%): Active compute rentals generate the primary score
  • Challenge Performance (30%): Computational benchmarks for idle workers
  • Availability Multiplier: Based on 169-hour online presence

Lease Revenue

  • Workers with active compute rentals earn lease scores
  • Idle workers score zero on this component
  • Integrated with compute marketplace APIs

Challenge Performance

  • CPU/GPU matrix multiplication benchmarks
  • Two-phase verification prevents cheating:
    • Phase 1: Workers commit to results (merkle root)
    • Phase 2: Validators verify through random sampling
  • Scoring uses participation baseline + performance ranking
  • Rewards consistent participation over peak performance

Worker Management

  • Maximum 100 workers per miner
  • Challenges target only unleased workers
  • Final score sums all worker performance (capped at 100)

⛏️ Miner Documentation

ByteLeap Miners aggregate worker resources and serve as the interface between compute providers and the Bittensor network. This is the recommended starting point for new users.

Prerequisites

  • Python 3.8+
  • Bittensor wallet with registered hotkey

Hardware Requirements

  • CPU: Physical CPU with 8+ cores
  • Memory: 32 GB RAM or higher
  • GPU: One of the following NVIDIA models:
    • GeForce RTX 3090, 4090, 5090
    • Data center GPUs: A100, H100, H200, B200
    • Proper NVIDIA drivers and CUDA runtime installed

Installation

# Setup environment
python3 -m venv venv
source ./venv/bin/activate

# Install dependencies
pip install -r requirements.txt

Configuration

Configure your setup in these files:

  • config/miner_config.yaml - Network settings, wallet, worker management
  • config/worker_config.yaml - Miner connection, compute settings

GPU Configuration

Workers automatically launch the CUDA binary (bin/subnet-miner_static) for GPU challenge execution:

gpu:
  enable: true
  auto_start: true
  binary_path: "./bin/subnet-miner_static"

Running Components

Start Miner

Aggregates workers and communicates with Bittensor:

python scripts/run_miner.py --config config/miner_config.yaml

Start Worker

Provides compute resources:

python scripts/run_worker.py --config config/worker_config.yaml
💡 Typical Setup: Run one miner + multiple workers for optimal resource utilization.

🛡️ Validator Documentation

ByteLeap Validator is the network coordination node for Bittensor SN128, managing challenge validation, weight calculation, and network scoring for the distributed compute resource platform.

Validator Responsibilities

  • Challenge Validation: Two-phase verification protocol for computational integrity
  • Weight Management: Network-wide scoring and weight updates
  • Resource Tracking: PostgreSQL-based miner and worker performance monitoring
  • Secure Communication: Session-based encryption with miners

Prerequisites

  • Python 3.8+
  • PostgreSQL 12+
  • Bittensor wallet with registered hotkey
  • Sufficient TAO stake for network participation

Installation

# Setup environment
python3 -m venv venv
source ./venv/bin/activate

# Install dependencies
pip install -r requirements.txt

# Setup PostgreSQL database, skip this if you use sqlite (default config)
# (cp scripts/setup_database.sh /tmp; cd /tmp; sudo -u postgres /tmp/setup_database.sh setup)

Configuration

Configure your validator in config/validator_config.yaml:

  • Network settings (netuid, wallet paths)
  • Database connection parameters
  • Challenge verification settings
  • Weight update intervals

Running the Validator

Start Validator

python scripts/run_validator.py --config config/validator_config.yaml

Database Management

# Apply database migrations
./scripts/db_migrate.py upgrade

# Check database connection
./scripts/db_migrate.py check

Development Setup

Database Operations (PostgreSQL)

# PostgreSQL Setup (RHEL/CentOS)
yum install postgresql-server postgresql-contrib
/usr/bin/postgresql-setup --initdb
systemctl restart postgresql

# Configure access
vi /var/lib/pgsql/data/pg_hba.conf
# Add: host all all 127.0.0.1/32 md5
systemctl restart postgresql

🔌 API Reference

📝 Note: API documentation is currently in development. Check back soon for comprehensive API reference and integration guides.

The ByteLeap API will provide programmatic access to:

  • Compute marketplace integration
  • Worker status and performance metrics
  • Challenge submission and verification
  • Network scoring and weight information

📄 License

MIT License - see the LICENSE file for details.