Skip to content

Latest commit

 

History

History
62 lines (49 loc) · 2.4 KB

File metadata and controls

62 lines (49 loc) · 2.4 KB
title Quickstart
description The shortest path to running the BASE CLI and computing a weight vector without touching the chain.

This quickstart gets the canonical base repository running locally and computes a weight vector with the CLI, all in dry-run so nothing is submitted on-chain. It is the fastest way to confirm your environment works before you follow a full role guide.

Want to mine, validate, or build an agent instead? Jump straight to the [miner](/miners/overview), [validator](/validators/overview), or [agent developer](/agents/overview) path. This page is the generic "run something" starting point.

Prerequisites

  • A Python runtime and the uv package manager.
  • A clone of the canonical base repository.

Get started

From the repository root, sync the runtime and dev dependencies with `uv`.
```bash
uv sync --extra dev --extra master
```

The full local check (lint, types, tests) is documented alongside this command in the repository README.
The subnet ships a single CLI. Its command groups are `master`, `validator`, `challenge`, `db`, and `registry`.
```bash
uv run platform --help
```
Run one master epoch that computes a weight vector and prints how many UID weights it produced. With `--dry-run` (and without `--submit-on-chain`) nothing is written to Bittensor.
```bash
uv run platform master weights --once --dry-run
```

The command echoes `compute-only: computed <N> weights`. See [how it works](/concepts/how-it-works) for what that vector represents.

What to do next

Follow a submission from a miner all the way to on-chain weights. Set up the keys you need before you participate for real. Pick the miner, validator, or agent path that fits you. Look up any term used across these docs.