NI Compuτe: Subnet Miner Setup
How to Mine on the Bittensor NI Compute Subnet (SN27) - The Permission-less Compute Market
Last updated
How to Mine on the Bittensor NI Compute Subnet (SN27) - The Permission-less Compute Market
Last updated
For miners interested in joining this innovative network, Subnet 27 offers the opportunity to contribute computing resources and earn $NI in return. This guide is structured to provide a comprehensive breakdown of how you can get started with contributing to Bittensor’s commodity markets using your compute power.
NI Compute decentralizes computing resources by combining siloed pools of compute on a blockchain to be validated and accessed trustlessly. This opens a door to scalable compute without the constraints of centralized power.
NI Compute brings, arguably, the most important and finite resource needed for the creation of machine intelligence. All network participants will have access to an ever-expanding pool of compute for all development needs.
What is a decentralized supercomputer without access to permissionless compute?
Miners contribute processing resources, notably GPU (Graphics Processing Unit) instances.
Performance-Based Mining: The system operates on a performance-based reward mechanism, where miners are incentivized through a dynamic reward structure correlated to the processing capability of their hardware. High-performance devices are eligible for increased compensation, reflecting their greater contribution to the network's computational throughput. Emphasizing the integration of GPU instances is critical due to their superior computational power, particularly in tasks regarding machine learning.
We greatly appreciate and encourage contributions from the community to help improve and advance the development of the Compute Subnet. We have an active bounty program in place to incentivize and reward valuable contributions.
If you are interested in contributing to the Compute Subnet, please review our Reward Program for Valuable Contributions document on GitHub. This document outlines the details of the bounty program, including the types of contributions eligible for rewards and the reward structure.
We do not support Containerized (docker)-based cloud platforms such as Runpod, VastAI and Lambda.
We strongly urge miners to provide their own hardware to foster and build a stronger network for all. Providing your own in-house hardware may come with its own benefits.
If you cannot supply your hardware in-house, here are some usable GPU providers:
Examples of GPUs to rent (listed in order of computing power):
NVIDIA H200: 4.00
NVIDIA H100 80GB HBM3: 3.30
NVIDIA H100 80GB PCIE: 2.80
NVIDIA A100-SXM4-80GB: 1.90
Verify that the Docker Engine installation is successful by running the hello-world image.
See Bittensor’s documentation for alternative installation instructions.
Verify using the btcli command
which will give you an output similar to below:
Create a Cold & Hotkey with the commands below:
Access the Compute-Subnet Directory
Required dependencies for validators and miners:
To ensure optimal performance and compatibility, it is strongly recommended to install the latest available CUDA version from NVIDIA.
If Nvidia toolkit and drivers are already installed on your machine, scroll down to verify then move on to the Wandb Setup.
You may need to reboot the machine at this point to finalize changes
The simplest way to check the installed CUDA version is by using the NVIDIA CUDA Compiler (nvcc).
The output of which should look something like
Inside of the Compute-Subnet directory; Rename the .env.example file to .env and replace the placeholder with your actual API key.
Install and run pm2 commands to keep your miner online at all times.
Confirm pm2 is installed and running correctly
Make sure to check that docker is properly installed and running correctly:
This is an example of it running correctly:
At this point, you will need some $TAO in your coldkey address for miner registration. Once your coldkey is funded, run the command below to register your hotkey:
Open your desired ssh port for allocations; default is 4444 (required for allocation):
--miner.whitelist.not.enough.stake: (Optional) Whitelist the validators without enough stake. Default: False.
--miner.whitelist.not.updated: (Optional) Whitelist validators not using the last version of the code. Default: False.
--miner.whitelist.updated.threshold: (Optional) Total quorum before starting the whitelist. Default: 60. (%)
After launching the compute miner, you can then check the logs using the two commands below:
Rent A Server From Subnet 27:
Compute Subnet Github:
Compute Subnet Discord Channel:
Real-Time Compute Subnet Metrics:
Reward Program for Valuable Contributions:
Validator CLI Guide For Reserving Compute Subnet Resources:
(referral code: BITTENSOR27)
(referral code: BITTENSOR27 - 2% cash back in platform expenditures)
GPU Base Scores: The following GPUs are assigned specific base scores, reflecting their relative performance. To understand scoring please see the Proof-of-GPU page :
To run a miner, you must Docker and run the service. If Docker is already installed on your machine, scroll down to step 2.1
Install Link:
Bittensor Documentation:
To log into the wandb project named opencompute from neuralinternet, miners and validators need a wandb API key. This is necessary for your miner to be properly scored. You can obtain a free API key by making an account here:
You can now track your mining and validation statistics on Wandb. For access, visit: . To view the networks overall statistics check out our real-time dashboard here:
For more information, refer to the NVIDIA Container Toolkit installation guide:
If you get the error ‘too many registrations this interval’ it means the max amount of registrations that cycle has been reached, and you need to wait a bit and try again. You can check the registration cost
To set up your miner, first replace COLDKEYNAME & HOTKEYNAME with the names of your keys. Then, update axon.portwith a 4-digit number in the range you opened for . For the parameters --axon.external and --axon.ip, use your miner machine's public IP address in place of the 'xxxxx's. You can find this IP by running hostname -I. Though not always necessary, these parameters can be crucial for resolving certain connectivity issues.
