Loading...
Loading
Overview
Registration Activity
Neuron registration trends
This Interval
0
— burn · — PoW
Target / Interval
Loading
Neuron registration trends
Organizations managing distributed compute infrastructure face fragmentation: worker nodes are scattered across environments, resource availability is opaque, and monetization requires custom middleware. Traditional centralized compute platforms lock users into proprietary APIs and pricing models. A decentralized compute network solves this by pooling resources from independent operators, making availability transparent and rewarding contributors directly based on actual lease activity and network participation. ByteLeap Miner implements this on Bittensor SN128 by aggregating up to 100 worker nodes under a single miner identity, routing computational tasks through an encrypted Bittensor protocol, and earning rewards proportional to active compute leases—eliminating intermediaries and giving operators direct control over their resource pools.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
ByteLeap Miner is a resource aggregation component for the Bittensor SN128 distributed compute network. It manages worker nodes, aggregates their computational resources, and earns rewards through active compute leases and challenge participation. Miners connect to validators, manage up to 100 workers via WebSocket, and route computational tasks while reporting resource availability and performance metrics to the Bittensor network.
ByteLeap uses a three-tier architecture: Validators coordinate the network and validate miner scoring; Miners (this component) aggregate worker resources, manage lifecycle via WebSocket (1-to-N connections), handle task routing, and communicate with Bittensor; Workers (separate repo) provide system monitoring, execute challenges, manage VMGW sessions, and handle libvirt management. The miner acts as the central coordinator between the Bittensor network and distributed worker nodes, with encrypted communication via Bittensor protocol and WebSocket for local worker management.
The scoring system operates on two main dimensions: (1) Lease Revenue - workers with active compute rentals earn scores while idle workers contribute zero, with integration to compute marketplace APIs for lease tracking; (2) Availability Multiplier - based on 169-hour rolling window of continuous online presence. Miners can manage up to 100 workers, and challenges target only unleased workers to avoid disrupting revenue-generating workloads. The final miner score is the sum of all individual worker scores, with a maximum cap of 100 points.
This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository for the latest instructions.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
Pioneering the Future of Cloud & Blockchain
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 2h ago (hourly snapshot)
Hardware requirements depend on connected workers. Miner itself is lightweight; actual compute power comes from aggregated workers.
Validator documentation not provided in source materials
Create Python virtual environment
python3 -m venv venv
Activate virtual environment (Linux/macOS; use venv\Scripts\activate on Windows)
source ./venv/bin/activate
Install all required dependencies
pip install -r requirements.txt
Configure network settings, wallet credentials, and worker management parameters
Edit config/miner_config.yaml
Start the miner process (development/testing)(optional)
python scripts/run_miner.py --config config/miner_config.yaml
Start miner with PM2 process manager (recommended for production)(optional)
pm2 start ecosystem.config.js
Validator setup instructions are not included in the source materials
Documentation not provided
