Connito AI
Validator Guide

Configuration

Connito validators are configured via a YAML file. This page walks through the key fields.

Example Configuration

chain:
  netuid: 102
  network: archive
  coldkey_name: my-wallet
  hotkey_name: my-hotkey
  port: 8000
model:
  model_path: deepseek-ai/DeepSeek-V2-Lite
  device: cuda
cycle:
  cycle_length: 448
  distribute_period: 20
  train_period: 300
  commit_period: 8
  submission_period: 20
  validate_period: 50
  merge_period: 50
ckpt:
  validator_checkpoint_path: /path/to/validator_checkpoint
  miner_submission_path: /path/to/miner_submission
dht:
  port: 6001

Field Reference

chain

FieldDefaultDescription
netuid102Subnet ID. Locked — do not change.
networkarchiveBittensor network (archive or finney). Locked.
coldkey_nameWallet coldkey name (must match btcli wallet list).
hotkey_nameWallet hotkey name.
port8000Bittensor serve port. Must be open inbound.

model

FieldDefaultDescription
model_pathdeepseek-ai/DeepSeek-V2-LiteHugging Face model ID. Locked.
devicecudaDevice for inference.

cycle

Cycle timing parameters. These are locked and must match the subnet-wide configuration.

FieldDefaultDescription
cycle_length448Total blocks per cycle.
distribute_period20Blocks for model distribution to miners.
train_period300Blocks for miner training.
commit_period8Blocks per commit sub-phase.
submission_period20Blocks for miner checkpoint submissions.
validate_period50Blocks for proof-of-loss evaluation.
merge_period50Blocks for inter-validator merging.

ckpt

FieldDefaultDescription
base_checkpoint_pathcheckpoints/validatorRoot directory for all checkpoint storage.
validator_checkpoint_pathvalidator_checkpointSubdirectory for validator state checkpoints.
miner_submission_pathminer_submissionSubdirectory for downloaded miner submissions.
checkpoint_topk2Number of recent checkpoints to keep.

dht

FieldDefaultDescription
port6000Hivemind DHT port. Open both TCP and UDP.

Locked Fields

Fields marked as locked are controlled by the subnet owner and must match the network-wide configuration. If your config file contains a different value, the validator will auto-reset it to the default on startup (with a warning in the logs).

Do not change locked fields unless instructed by the maintainers.

Docker Path Handling

When running with Docker, you do not need a separate config file. The validator automatically detects Docker and remaps host paths to container paths:

Host path (in your YAML)Container path (at runtime)
root_path/data
expert_groups//app/expert_groups
Checkpoint paths/data/checkpoints/...

This means you can use the same validator.yaml for both bare-metal and Docker runs.