Bittensor Subnet #36

HIP (Human Intelligence Primitive) Subnet

The HIP (Human Intelligence Primitive) Subnet is a Bittensor subnet designed to provide human intelligence services to other subnets. It will allow other subnets to send their data to the HIP Subnet for human evaluation, testing, and feedback. The HIP Subnet harnesses the collective intelligence of human miners who compete to provide high-quality evaluations and insights on the submitted data. Validators in the HIP Subnet assess the quality of the miners' responses and distribute rewards accordingly, creating an incentive mechanism that promotes diverse and valuable human feedback.

Features

Human Intelligence Primitives: The HIP Subnet aims to leverage human intelligence to perform tasks that require subjective judgment, contextual understanding, and creative problem-solving. Miners in the HIP Subnet are human participants who contribute their cognitive abilities to evaluate and provide feedback on data submitted by other subnets.*
Incentive Mechanism: The HIP Subnet implements an incentive mechanism that rewards miners for providing high-quality evaluations and feedback. Miners compete to offer the most valuable insights, and the subnet's validators distribute rewards based on the quality and human-likeness of the miners' responses. This incentive structure encourages miners to deliver their best work and continuously improve the network's overall performance.

Getting Started

To participate in the HIP Subnet as a miner or validator and get set-up quickly, Please follow the instructions in the respective guides bellow:

It is not mandatory to use either service provided in these guides. They are provided to help you get started.

Please note that Bittensor is currently supported on macOS and Linux, with limited support for Windows.

Reward Model

The current reward model works as follows:

When a miner submits a valid response (correct captcha or task answer), they receive the highest reward. If their response is valid but the task answer is incorrect, they receive a lower reward.

Miners who consistently provide correct answers will accumulate higher total rewards over time compared to miners who don't respond or provide incorrect answers.

The validator updates the scores of the miners based on the rewards they earn for each task. These scores are used to determine the overall performance and ranking of the miners.

As more miners start actively participating and providing correct answers, the relative rewards of the inactive or underperforming miners will decrease. This is because the active miners will be earning higher rewards, while the inactive miners will not be accumulating rewards at the same rate.

Consequently, the scores of the active and accurate miners will increase, while the scores of the inactive or inaccurate miners will relatively decrease or stagnate.

Mining

Mining in the HIP Subnet is designed to be straightforward. Follow these steps to set up and run your miner on an Ubuntu server. We have also included a guide on how to get set up on DigitalOcean below.

Setting up on DigitalOcean

Prerequisites

Python 3.8 or higher
A Bittensor wallet with sufficient TAO for registration
2X VCPU
8GB RAM
100GB SSD

Setting Up the Miner

Clone the HIP Subnet repository:

git clone https://github.com/HIP-LABS/HIP-Subnet.git

Enter the directory where the HIP Subnet was cloned:
```
cd HIP-Subnet
```

Create a virtual environment and install dependencies:

sudo apt-get update
sudo apt install python3.10-venv
python3 -m venv venv
source venv/bin/activate
python3 -m pip install -e .

Register your Bittensor keys with the subnet:

btcli subnet register --wallet.name <YOUR_WALLET_COLDKEY> --wallet.hotkey <YOUR_WALLET_HOTKEY> --netuid 36 --subtensor.network finney

Replace <YOUR_WALLET_COLDKEY> and <YOUR_WALLET_HOTKEY> with your corresponding keys.

Confirm your key is registered to the subnet:

btcli w inspect --wallet.name <YOUR_WALLET_COLDKEY> --wallet.hotkey <YOUR_WALLET_HOTKEY> --netuid 36 --subtensor.network finney

Running the Miner

To ensure that the miner and server run continuously, we will use pm2.

Install Node.js and pm2:

sudo apt-get install -y nodejs npm
sudo npm install pm2@latest -g

Ensure your virtual environment is activated:
```
source venv/bin/activate
```

Run the miner server with pm2:

pm2 start ./scripts/run_miner_frontend.sh --name miner_server

3.1 (Alternative to PM2)
Run the miner server with systemcl:
chmod +x /scripts/setup_uvicorn_service.sh
./scripts/setup_uvicorn_service.sh

Run the miner script with pm2:

pm2 start --interpreter python3 --name miner -- neurons/miner.py --wallet.name <YOUR_WALLET_COLDKEY> --wallet.hotkey <YOUR_WALLET_HOTKEY> --netuid 36 --subtensor.network finney --logging.debug --logging.trace

Save the pm2 process list and corresponding environments:
```
pm2 save
```
Set pm2 to start on boot:
```
pm2 startup
```

Accessing the Miner Frontend

The miner frontend will be accessible at http://localhost:3001 from your chosen web browser.

Managing `pm2` Processes

To check the status of your processes:
```
pm2 status
```
To restart a process:
```
pm2 restart <process_name>
```
To stop a process:
```
pm2 stop <process_name>
```

For further assistance, refer to the PM2 documentation to manage and keep your miner application online 24/7.

Validating

Setting up a HIP validator involves configuring a server with specific hardware requirements. Follow these steps to set up and run your validator on an Ubuntu server.

We have made a short guide on how to set up your validator using runpod here: Setting up on RunPod

Prerequisites

2x NVIDIA Cards with at least 20GB VRAM each. eg. 2 * RTX 3090.
8X VCPU
32GB RAM
200GB NVMe
Python 3.8 or higher
A Bittensor wallet with sufficient TAO for staking and registration

Option 1: Automated Setup

SSH into your server:
```
ssh username@your-server-ip
```

Export the mnemonic for your validator keys:

export MNEMONIC="[generate a mnemonic to use as validator]"

Run the setup script:

curl https://raw.githubusercontent.com/HIP-Labs/HIP-Subnet/main/scripts/setup_validator.sh | bash

Restart the server:
```
sudo reboot
```
SSH into the server again:
```
ssh username@your-server-ip
```

Spool up the subtensor after reboot:

cd ~/subtensor
sudo ./scripts/run/subtensor.sh -e docker --network finney --node-type lite

Change directory back into the HIP-Subnet and activate the environment:
```
cd ~/HIP-Subnet
source venv/bin/activate
```

Ensure your GPU is working:

python -c "import torch; print('CUDA available:', torch.cuda.is_available())"

Option 2: Manual Setup

SSH into your server:
```
ssh username@your-server-ip
```

Install NVIDIA drivers and CUDA toolkit:

sudo apt update
sudo apt install nvidia-driver-535 -y
sudo apt install nvidia-cuda-toolkit -y

Install Docker:

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list >/dev/null
sudo apt update
sudo apt install docker-ce -y
sudo systemctl start docker
sudo systemctl enable docker
sudo usermod -aG docker "$USER"

Install Node.js and PM2:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
source ~/.nvm/nvm.sh
nvm install --lts
npm install -g pm2

Clone and set up HIP Subnet:

cd ~
git clone https://github.com/HIP-Labs/HIP-Subnet
cd HIP-Subnet
git reset --hard
git checkout main
git pull

Install Python 3.10 and set up virtual environment:

sudo add-apt-repository ppa:deadsnakes/ppa -y
sudo apt update
sudo apt install -y python3.10 python3.10-venv python3.10-dev
sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.10 1

Create virtual environment and install dependencies:

cd ~/HIP-Subnet
python3.10 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
pip install -e .

Run the subtensor in Docker:

cd ~
git clone https://github.com/opentensor/subtensor.git
cd subtensor
git checkout main
sudo ./scripts/run/subtensor.sh -e docker --network finney --node-type lite

Staking and Running the Validator

Stake your validator:

btcli subnet stake --wallet.name <YOUR_WALLET_COLDKEY> --wallet.hotkey <YOUR_WALLET_HOTKEY> --amount <DESIRED_AMOUNT_OF_TAO> --netuid 36 --subtensor.network finney

Run the validator script with pm2:

pm2 start --interpreter python3 --name validator -- neurons/validator.py --wallet.name <YOUR_WALLET_COLDKEY> --wallet.hotkey <YOUR_WALLET_HOTKEY> --netuid 36 --subtensor.network finney --logging.debug --logging.trace

Save the pm2 process list and corresponding environments:
```
pm2 save
```
Set pm2 to start on boot:
```
pm2 startup
```

Managing `pm2` Processes

To check the status of your processes:
```
pm2 status
```
To restart a process:
```
pm2 restart <process_name>
```
To stop a process:
```
pm2 stop <process_name>
```

For further assistance, refer to the PM2 documentation to manage and keep your validator application online 24/7.

Contributing

We welcome contributions to the HIP Subnet! If you'd like to contribute, please follow these steps:

Fork the repository
Create a new branch for your feature or bug fix
Make your changes and commit them with descriptive messages
Push your changes to your forked repository
Submit a pull request to the main repository
Please ensure that your code adheres to the project's coding style and passes all tests before submitting a pull request.

#### License

# The MIT License (MIT)
# Copyright © 2024 HIP-LABS 

# Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
# documentation files (the “Software”), to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
# and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

# The above copyright notice and this permission notice shall be included in all copies or substantial portions of
# the Software.

# THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
# THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
# DEALINGS IN THE SOFTWARE.

Name		Name	Last commit message	Last commit date
Latest commit History 262 Commits
.circleci		.circleci
hip		hip
neurons		neurons
public		public
scripts		scripts
.gitignore		.gitignore
Dockerfile		Dockerfile
README.md		README.md
VERSION		VERSION
contributing.md		contributing.md
ecosystem.config.js		ecosystem.config.js
frontend.py		frontend.py
min_compute.yml		min_compute.yml
requirements.txt		requirements.txt
setup.py		setup.py

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Bittensor Subnet #36

HIP (Human Intelligence Primitive) Subnet

Features

Getting Started

Reward Model

Mining

Prerequisites

Setting Up the Miner

Running the Miner

Accessing the Miner Frontend

Managing `pm2` Processes

Validating

Prerequisites

Option 1: Automated Setup

Option 2: Manual Setup

Staking and Running the Validator

Managing `pm2` Processes

Contributing

About

Releases

Packages

Contributors 2

Languages

HIP-Labs/HIP-Subnet

Folders and files

Latest commit

History

Repository files navigation

Bittensor Subnet #36

HIP (Human Intelligence Primitive) Subnet

Features

Getting Started

Reward Model

Mining

Prerequisites

Setting Up the Miner

Running the Miner

Accessing the Miner Frontend

Managing pm2 Processes

Validating

Prerequisites

Option 1: Automated Setup

Option 2: Manual Setup

Staking and Running the Validator

Managing pm2 Processes

Contributing

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Contributors 2

Languages

Managing `pm2` Processes

Managing `pm2` Processes

Packages