Mining on Bitrecs V2 means crafting a YAML artifact — a bundle of Jinja2 prompt templates, a model choice, and sampling parameters — then submitting it to the evaluation pipeline where it competes against other miners for onchain emissions. Unlike traditional mining, there is no hardware to provision: you iterate on prompts and model configuration, and the platform handles inference. This guide walks you from a fresh machine to a confirmed onchain submission.Documentation Index
Fetch the complete documentation index at: https://docs.bitrecs.ai/llms.txt
Use this file to discover all available pages before exploring further.
Each hotkey may only have one active submission at a time. Plan your artifact carefully before uploading — you cannot edit a submitted Gist.
Prerequisites
- A registered Bittensor wallet with a hotkey on the Bitrecs subnet (mainnet netuid 122, testnet netuid 296)
- A GitHub account with Gist access
- Python 3.11+ (managed by UV)
Steps
Install UV
UV is the Python package and project manager used by Bitrecs V2. Install it with the official installer:Restart your shell or source your profile after installation so the
uv command is available.Set up the environment
Sync all dependencies using UV, then create a Add these two variables to
.env file with your subtensor connection details:.env:Acquire a hotkey on the subnet
Register a fresh hotkey on the Bitrecs subnet using Replace
btcli. Each hotkey is tied to exactly one submission, so use a dedicated hotkey for each artifact you plan to submit.122 with 296 if you are on testnet.Create your artifact.yaml
Create a file named Replace
artifact.yaml (or any name you prefer locally). The artifact defines the prompts and model configuration the evaluation harness will run. Below is the canonical example from the repository:artifact.yaml
miner_hotkey with your own hotkey’s ss58 address. See the artifact reference for a description of every field.Upload to GitHub Gist as a single commit
Go to gist.github.com and create a new Gist:
- Paste the contents of your
artifact.yamlinto the editor. - Name the file
artifact.yaml. - Click Create secret gist (or public — both are accepted).
https://gist.github.com/YOUR_ACCOUNT/GIST_IDSubmit via the CLI
Run the upload command from the repository root. Replace the placeholder values with your GitHub account name, Gist ID, and wallet key names:The CLI will:On success, you will receive an artifact ID and a link to track your submission on the dashboard.
- Validate the Gist and artifact locally.
- Check your eligibility against the Bitrecs API.
- Commit the submission onchain.
- Wait ~12 seconds for the reveal period.
- POST the signed artifact to the submission endpoint.
The full process can take up to 1 minute depending on chain congestion. Do not interrupt the process.
Next steps
Artifact reference
Full documentation for every field in the artifact YAML format.
Submission process
Understand what happens under the hood during the onchain commitment flow.
Mining tips
Prompt engineering advice, provider tradeoffs, and common pitfalls to avoid.
Scoring overview
Learn how WTA scoring and Pareto dominance determine which miner earns emissions.