Skip to content

validator_setup.md

Latest commit

 

History

History
79 lines (51 loc) · 1.94 KB

validator_setup.md

File metadata and controls

79 lines (51 loc) · 1.94 KB

Validator Setup Guide

Steps to set-up the validator.

⚠️ IMPORTANT: We strongly recommend auditing instead of validating for most users. Auditing is more cost-effective, easier to set up, and doesn't require expensive GPU infrastructure. See the Auditing Overview and Auditing Setup Guide for details.

If you dont intend to utilise the bandwidth independently of the gradients platform, child hotkeying would not be a bad idea at all.

Prerequisites

Setup Steps

  1. Clone the repo
git clone https://github.com/rayonlabs/G.O.D.git
cd G.O.D
  1. Install system dependencies (Ubuntu 24.04 LTS):
task bootstrap
  1. Get your key onto the VM:

You know how to do this, don't you ;)

  1. Create and set up the .vali.env file:

Within this you'll be asked for the gpu(s) you'd like to use for validation. If you select the default, then gpu at index [0] will be used to evaluate all models. However, you can select whichever you'd like "3,4,5" would mean that evaluation jobs are spread between your third, fourth and fifth gpu, for example.

task config

Make sure the VALIDATOR_PORT is not being used by anything else, and is exposed in your firewall settings.

  1. Install the dependencies:
task install

FOR DEV

pip install -e '.[dev]'
pre-commit install
  1. Run the Validator
task autoupdates

FOR DEV

task validator
  1. Make sure you have outgoing and incoming connections exposed

The validator communicates with 'api.gradients.io' for tournament infrastructure (fees, balances, task coordination). Ensure your firewall allows outbound HTTPS connections to this domain.

IF YOU ARE DEVVING AND ONLY IF YOU ARE A DEVELOPER, ADD THIS (key needs to be upgraded)

echo "NINETEEN_API_KEY=<your-nineteen-api-key>" >> .vali.env