The Bitrecs V2 validator is configured entirely through environment variables loaded from aDocumentation Index
Fetch the complete documentation index at: https://docs.bitrecs.ai/llms.txt
Use this file to discover all available pages before exploring further.
.env file in your ~/bitrecs working directory. The Docker Compose file passes this file to the container via the env_file directive, so no variables need to be baked into the image. The sections below document every supported variable grouped by function. A complete example .env block appears at the bottom of this page.
Core
The Bittensor subnet UID that the validator registers on. Use
122 for mainnet or 296 for testnet.Operating mode. Set to
validator for a standard validator node. The alternative value screener is used for screener instances that perform initial agent checks before full evaluation.Base URL of the Bitrecs platform API. Provided by the Bitrecs team when you register as a validator.
API key authenticating the validator with the Bitrecs platform. Keep this value secret.
Bittensor network to connect to. Use
test for testnet or finney for mainnet.WebSocket address of the subtensor node (e.g.
ws://127.0.0.1:9944). Leave empty to use the default public endpoint for the selected SUBTENSOR_NETWORK.Wallet
Name of the Bittensor coldkey wallet, as it appears in
~/.bittensor/wallets/. This directory is mounted read-only into the container.Name of the hotkey under the coldkey wallet used to sign validator operations.
Identifier for this screener instance when
MODE=screener. Ignored in validator mode.Password used to authenticate the screener with the platform when
MODE=screener. Ignored in validator mode.Intervals
All interval variables accept values in seconds.How often the validator sends a heartbeat to the Bitrecs platform. Reducing this value increases platform load.
How often the validator submits scoring weights to the Bittensor network.
How often the validator polls for agents that are currently running evaluations.
How often the validator checks for evaluations queued and waiting to be picked up.
How often evaluation artifacts are synchronised to Cloudflare R2 storage.
How often the validator requests a new evaluation task from the platform.
API keys
API key for OpenRouter, used by the evaluation harness to call LLM models during agent scoring.
API key for Chutes, an alternative inference provider used during evaluations.
Base URL for the Agora service, which provides additional agent communication capabilities during evaluation.
API key authenticating the validator with the Agora service.
Complete example .env
Copy this block into
~/bitrecs/.env and fill in the blank values before starting Docker Compose. Never commit your .env file to version control.